$9
500 lookups / month · 20 req/min
- Single enrichment API
- Workspace access
- History and usage
Best for first-time evaluation and small CRM cleanup jobs.
Start with a small credit pool, validate search relevance and enrichment quality, then move into batch and recurring workflows once the economics make sense.
500 lookups / month · 20 req/min
Best for first-time evaluation and small CRM cleanup jobs.
3,000 lookups / month · 60 req/min
Best for active outbound teams running weekly prospecting and enrichment workflows.
15,000 lookups / month · 200 req/min
Best for RevOps owners with recurring jobs, shared usage, and larger batch volume.
Leads Pro starts at $9 per month for 500 monthly lookups. The pricing model is usage-based, so teams can validate people search, company search, and lead enrichment before committing to a larger sales data spend.
API keys, workspace search, usage logging, request history, and structured enrichment responses are standard. The difference between plans is mainly volume, rate limits, and how much recurring work your team needs to support.
Most teams should start with the smallest plan that can answer one real workflow question: can this improve prospecting, cleanup, or routing enough to justify ongoing usage?
This gives search visitors a clearer path from cost questions into implementation fit, instead of making the pricing page a dead end.
Usage-based credit pricing is often a better fit than seat-based plans for lean outbound teams testing lead enrichment APIs.
CRM data enrichment works best when teams validate stale records, repair company context, and improve routing inputs before automation touches the data.
A sales prospecting API should help teams search for buyers, inspect company context, and enrich weak records without forcing them into disconnected tools.
Most pricing visitors still need one more step before they convert: docs for implementation questions, compare pages for vendor framing, or guides for workflow economics.
Use the API reference if the open question is endpoint shape, auth, or workflow coverage.
Use comparison pages if the buyer is still deciding between a focused workflow and a heavier platform.
Use editorial pages if the real question is ROI, workflow fit, or how to size the first test.