Candidate sourcing API and people-search infrastructure

Researched

Pearch AI✓ Claimed by vendor

API-first candidate sourcing engine that turns natural-language or job-description queries into ranked people profiles, with optional fresh data, contact enrichment and MCP access.

Visit Pearch AI Compare

The short answer

Best for: HR-tech and ATS teams embedding AI-native candidate discovery into their own product or agent
Not ideal for: Recruiters wanting a turnkey ATS, outreach platform or zero-integration sourcing seat
Price: Standard: USD 600 for 10,000 credits; usage varies by search and enrichment features
Closest alternative: Apollo.ioChoose Apollo when a broader prospecting data platform and end-user workflow matter more than a recruitment-specific semantic sourcing backend

At a glance

Recruitment fitStrong
Ease of useUnknown
ImplementationFair
Price transparencyStrong
Value for moneyUnknown
ScalabilityStrong

Why these assessments

Recruitment fitStrong: The product is explicitly built as candidate-sourcing infrastructure for ATSs, recruiting CRMs, HR-tech tools and AI recruiting agents.
Ease of useUnknown: The API, playground and client libraries look developer-friendly, but SourcrLab has not integrated Pearch and we found no substantial independent end-user review base.
ImplementationFair: REST endpoints, a Python client, MCP and n8n reduce integration friction, but Pearch is still infrastructure: a production buyer must connect it, design the UX and test the resulting workflow.
Price transparencyStrong: Pearch publishes standard credit packs, validity periods, per-candidate ranges and the credit cost of Fast, Pro, freshness, insights and contact enrichment; custom high-volume economics still require sales.
Value for moneyUnknown: Costs are modelable but value depends on candidate relevance and how many paid enrichment features each workflow enables; SourcrLab has not measured that output against a live vacancy.
ScalabilityStrong: The API is designed for embedded and bulk use, publishes volume packs and custom packages, and separates faster searches from deeper Pro searches so buyers can trade latency against quality.

Our reading of the evidence on this page. No score, no formula.

Where it sits

Sourcing infrastructure
Contact
Outreach

The SourcrLab bottom line

Pearch AI is easiest to understand as the sourcing engine underneath another product. A user or agent sends a plain-language query, a job description or structured criteria; Pearch searches its people index, ranks profiles and can return insights, fresher profile data and contact details. That architecture is genuinely differentiated from recruiter-facing tools such as LinkedIn Recruiter or Juicebox, but it also moves more responsibility to the buyer: somebody has to integrate the API, design the recruiter experience and control downstream outreach. Public credit packs and per-feature credit costs make the commercial model more transparent than most data APIs, while the biggest open question remains independent production evidence. Pearch's published benchmark is methodologically useful, but it was authored around the team's own proprietary system, so SourcrLab would validate search quality on representative vacancies before standardising a product around it.

Best fit

Products that need candidate discovery as infrastructure rather than another recruiter tab. Pearch exposes natural-language search, structured filters, ranking, optional insights and contact data through an API, with MCP, n8n and Python routes for faster integration.

Think twice if

If you want a finished ATS, outreach sequencer or self-contained recruiter workflow. Pearch is deliberately a backend layer, its economics are usage-based, contact enrichment can multiply credit consumption, and buyers processing candidate data still need to review the vendor's data-source, transfer and legitimate-interest position with their own privacy requirements.

SourcrLab assessment

Everything on this page comes from the vendor's own pages, checked on the dates below. SourcrLab has not used this product in real recruitment work, so you will not find a first-hand opinion here.

Why choose Pearch AI?

Candidate search is the product, not a side feature

Pearch accepts simple natural-language queries, detailed job-description-style searches and structured criteria, then ranks the returned profiles by relevance. The API also exposes controls for search depth, filters and scoring instead of forcing a single black-box workflow.

It can sit inside the product you already own

Pearch positions itself as white-label sourcing infrastructure for ATSs, recruitment CRMs and AI agents. The same search layer can query Pearch's index or, by arrangement, a buyer's own candidate data, keeping the user experience in the buyer's product.

Speed, quality and freshness are explicit knobs

Fast Search costs one credit per returned candidate and prioritises speed; Pro costs five and spends more time on match quality. Realtime-profile refresh, insights, contact filtering and enrichment can be enabled separately, so a product does not have to pay the maximum data cost for every query.

There are several integration surfaces

Beyond the REST API, Pearch publishes an MCP server, n8n integration and Python client. The MCP can expose people and company/lead search to compatible AI clients, which is useful for agent-led recruiting workflows without inventing a proprietary connector layer first.

Contact data is optional rather than baked into every result

Search results can be filtered for existing contact data and individual profiles can be enriched with verified work email or phone data. Because those actions have separate credit costs, buyers can source broadly first and enrich only the candidates they actually want to contact.

Main trade-offs

This is infrastructure, not a finished recruiter desk

The core product is an API/backend. A team still needs an ATS, CRM, AI agent or custom interface around the results, plus its own outreach and pipeline workflow. That makes Pearch more powerful for builders and less suitable for a recruiter who simply wants to buy a seat and start sourcing.

Credit cost can change materially with configuration

Fast search is one credit per candidate while Pro is five; insights, realtime refresh and contact requirements add credits, and email or phone enrichment each cost six more. A buyer should model the exact production recipe rather than dividing pack price by headline credits.

The strongest benchmark still needs a conflict-of-interest footnote

The public arXiv study found Pearch highest on candidate relevance in its four-tool comparison and used human recruiters for preference judgements. But the paper describes Pearch as the authors' proprietary system and sourced its 48 queries from anonymised Pearch traffic. SourcrLab treats that as useful, transparent vendor-linked research — not the same thing as an unaffiliated third-party benchmark.

Candidate-data governance deserves buyer-side review

Pearch says it indexes public and licensed professional data under legitimate interest, supports opt-out/deletion, offers a DPA and SCCs, and uses EU/US and US subprocessors. Those are concrete controls, but they do not remove the need for an EU buyer to validate lawful use, transparency duties and international-transfer requirements in its own deployment.

Pricing and buying reality

Usage-based credits; Standard is USD 600 for 10,000 credits

One-time introductory offer shown at USD 300 for 10,000 credits, valid for one month; the regular Standard pack is USD 600 for 10,000 credits, valid for three months.
Startup: USD 1,500 for 40,000 credits, valid for three months. Growth: USD 3,000 for 125,000 credits, valid for six months.
Fast Search uses 1 credit per returned candidate; Pro Search 5. Candidate insights add 1, realtime profiles 2, and filtering for profiles with contact data 1.
Email enrichment and phone enrichment each add 6 credits for the candidates you choose to enrich.
Auto-recharge is on by default; packages expire by tier. Custom and high-volume packages are available and long-term commitments are optional.

What we do not know

The exact economics and validity period of custom or multi-million-credit packages
Whether your production configuration qualifies for negotiated pricing or annual bonus credits

Checked on the vendor's pricing page, August 2026. Pearch AI pricing

How it fits your stack

Works with

ATS and recruiting CRM products through custom API integration
MCP-compatible AI clients such as Claude Desktop, Cursor and VS Code
n8n and a published Python client
A buyer's own candidate database by arrangement

Likely replaces

Building a semantic people-search engine and maintaining a large candidate index in-house

May overlap with

People-data/search APIs such as Apollo and People Data Labs
Candidate discovery provided by recruiter-facing sourcing products, but not their end-user workflow

Check before buying

Model the credits used by your actual search + insights + freshness + enrichment recipe
Validate privacy, DPA, lawful basis and international-transfer requirements for your candidate-data use case
Benchmark relevance on your own representative roles rather than relying only on the vendor-linked study
Confirm rate limits and custom-volume terms for your production traffic

Pearch AI vs alternatives

Products a buyer would genuinely put next to this one, with the reason you would pick each instead.

Apollo.io

Choose Apollo when you want a broader prospecting database, enrichment and a finished end-user workflow rather than a recruitment-specific sourcing backend.

Juicebox

Choose Juicebox when recruiters themselves need a conversational sourcing interface rather than an API you embed into another product.

Used Pearch AI?

Tell other recruiters what worked, what did not, and who it suits. Positive, mixed or critical — all useful.

Share your experience

Evidence

Natural-language candidate search, structured filtering and ranked profile output are live API capabilities — checked against a primary source: Pearch API reference
Public Standard, Startup and Growth credit packs and per-feature credit costs were visible when checked — checked against a primary source: Pearch AI pricing
The vendor reports an index of 810M+ people across 30M+ companies and optional email/phone data — vendor claim, not independently verified: Pearch AI product page
MCP, n8n and Python integration routes are publicly documented — checked against a primary source: Official Pearch MCP repository
An independent recruitment-tool directory also characterises Pearch as an API/backend rather than a recruiter-facing ATS — checked against a primary source: Effi Flo independent Pearch.ai directory profile
The 2025 arXiv benchmark ranked Pearch highest in its four-tool human-preference comparison, but the paper is vendor-linked rather than unaffiliated evidence — vendor claim, not independently verified: arXiv sourcing benchmark — public methodology, vendor-linked authorship
SourcrLab has not integrated or used Pearch in production — not enough evidence

Last reviewed: August 2026. How SourcrLab verifies information

Pearch AI has claimed this profile.

You are welcome to show the Claimed badge on your own site. Optional, free, and not a rating.

Use the Claimed badge