For AI agents: a documentation index is available at https://docs.parallel.ai/llms.txt. The full text of all docs is at https://docs.parallel.ai/llms-full.txt. You may also fetch any page as Markdown by appending
.md to its URL or sending Accept: text/markdown.Beta Notice: Entity Search is part of Parallel FindAll, which is currently in public beta. Endpoints and request/response formats are subject to change; we will provide 30 days notice before any breaking changes. Entity Search is new and evolving quickly — if it isn’t working for your use case, tell us at support@parallel.ai.
What is Entity Search?
Entity Search finds people and companies on the web. It is a fast, synchronous API: you describe the people or companies you’re looking for in plain language and receive a structured set of matching results in seconds. Here, an entity is a real-world company or person. Entity Search is the real-time counterpart to FindAll, designed for the latency-sensitive parts of agentic systems.Entity Search is optimized for recall and speed: results return in seconds, and depending on the specificity of your objective, may not satisfy every requirement. The FindAll API is optimized for precision: it runs asynchronously and verifies every result against your match conditions.
When to Use It
Entity Search is built for real-time, human-in-the-loop, and latency-sensitive agentic workflows that require a starting set of people or companies to evaluate, enrich, or pass into deeper research:- Interactive interfaces: Power a go-to-market or hiring interface, a chat experience, or an automation with a human in the loop, where results need to come back in seconds.
- Starting sets for deeper work: Generate an initial set of people or companies to filter, enrich with additional fields, or hand off to FindAll or the Task API for comprehensive list building and research.
- Cost-sensitive lookups: Run people-and-company search at a fraction of the cost of a full FindAll run when you don’t need exhaustive coverage or per-field citations.
Input and Output
You send a small set of inputs and receive a structured set of matching results. Input:
Output: an
entity_set_id identifying the request, plus a ranked list of entities. Each entity includes its name, url, and description.
Entity Search does not support pagination — a request returns a single set of results, up to
match_limit. To retrieve as many results as possible, set match_limit to its maximum of 1,000.Sample Request
Sample Response
Getting Good Results
Entity Search prioritizes recall: a response favors including every relevant entity over excluding every irrelevant one. As a result:- Consider requesting more results than you need. Results are ranked approximately rather than verified against your objective, so a low
match_limitmay omit relevant entities that a larger request would include. If your workflow filters or reviews results downstream, request 100 or more and select from the response. - Avoid highly restrictive objectives. The API returns up to
match_limitresults even when few entities satisfy the objective, so for narrow, heavily qualified objectives, relevance declines toward the end of the list. Prefer an objective that captures your core criterion and apply further conditions downstream, or use FindAll, which evaluates each match condition explicitly.
How It Differs from FindAll
Entity Search and FindAll both turn natural-language criteria into entities, but they make different trade-offs.Scope and Compliance
Results draw on the public web and cover companies and people in a professional context — not consumer profiling, and not for use in employment, credit, or housing decisions.Next Steps
- FindAll Quickstart: Comprehensive, asynchronous entity discovery with verified, enriched, and cited results
- Search API: Retrieve pages and excerpts across the whole web
- Pricing: Detailed rate schedule
- Rate Limits: Default quotas and how to request higher limits