Enrichments vs FullEnrich
Waterfall enrichment, with an API your agents can call
The same idea — try the cheap sources first, pay for the one that lands — delivered as a REST API, an MCP server your AI agents can call directly, a chat agent, and CSV upload.
| Contact | |
|---|---|
 Liam Foster Queued | |
 Maya Torres Queued | |
 Ethan Brooks Queued | |
 Zoe Martin Queued | |
 Andre Willis Queued | |
 Chloe Bennett Queued | |
 Noah Klein Queued | |
 Priya Shah Queued | |
 Kenji Tanaka Queued | |
Ava Boone Queued |
Enrichments vs FullEnrich
The differences that decide it, including the ones that go the other way.
| Feature | Enrichments | FullEnrich |
|---|---|---|
| Approach | Waterfall: cheapest source first, stop when the field is filled. | Waterfall across a set of contact-data providers. |
| Billing model | Credits, charged only when a field comes back. Free plan: 100 credits, then $69/mo. | Credit packs, charged on successful enrichment. |
| Use from an AI agent | Native MCP endpoint. Connect it to Claude or ChatGPT and enrich in the chat. | No first-party MCP endpoint. |
| Access surfaces | REST API, MCP server, in-product chat agent, and CSV upload — one key for all four. | Web app, API and integrations. |
| Company firmographics | People and company enrichment from the same key. | Focused on contact data. |
| Provider depth | A smaller set of sources today, run cheapest-first. | A broader roster of paid providers in the waterfall. |
| Phone numbers | Mobile numbers from a LinkedIn profile URL, 10 credits per number found. Unverified — no deliverability equivalent exists for a phone, so none is implied. | Offered. |
| Start free |
Waterfall: cheapest source first, stop when the field is filled.
Waterfall across a set of contact-data providers.
Credits, charged only when a field comes back. Free plan: 100 credits, then $69/mo.
Credit packs, charged on successful enrichment.
Native MCP endpoint. Connect it to Claude or ChatGPT and enrich in the chat.
No first-party MCP endpoint.
REST API, MCP server, in-product chat agent, and CSV upload — one key for all four.
Web app, API and integrations.
People and company enrichment from the same key.
Focused on contact data.
A smaller set of sources today, run cheapest-first.
A broader roster of paid providers in the waterfall.
Mobile numbers from a LinkedIn profile URL, 10 credits per number found. Unverified — no deliverability equivalent exists for a phone, so none is implied.
Offered.
Only pay for the match that lands
Just ask. The agent plans the run, resolves each row, and checks every address before it reaches you — and a row that comes back empty is never charged.
Built for the whole GTM stack
Enrich a form fill in real time, backfill a million-row list overnight, and keep your CRM current — all from the same key.
A row that comes back empty costs nothing.
Credits are charged per delivered field, and every charge is written to a ledger you can read line by line.
People, companies and firmographics resolve behind a single endpoint — and the same key and the same credit balance work from the REST API, the MCP server, the in-product chat agent, and CSV upload. Ask in any of them and the answer comes back in the same shape.
Work email, title, seniority, department, location, LinkedIn URL, company domain and firmographics. No phone numbers.
Enrich a single record inline on a form fill, or hand a list to an async job and poll it. Same key, same ledger, same field catalogue.
POST /v1/people/enrich
One REST endpoint per operation, an OpenAPI document you can generate a client from, idempotency keys on every write, and typed errors.
GET /v1/openapi
Every record carries the time it was last verified, so you can re-run only what has gone stale — and a re-run that returns nothing new is not charged.
result.lastVerifiedAt
Lands wherever your team already works
A run finishes as a file, a signed webhook or a JSON response your stack already speaks — no connector to install on the other end.
Enrichments and FullEnrich — common questions
- How is this different from FullEnrich?
- The closest difference is where it runs. Enrichments exposes a native MCP server, so an AI agent in Claude or ChatGPT can enrich directly, and the same key also covers a REST API, an in-product agent and CSV upload. Both products use a waterfall and both charge on success.
- Do you cover companies as well as people?
- Yes. Company records return domain and firmographics alongside the people fields, from the same API key and the same credit balance.
- How should I compare them?
- Run the same 200-row list through both and compare hit rate, deliverability and total credits spent. That is the only comparison that settles it, and it is why the free plan exists.
Start enriching in a single call
Free to try, no card required. Ship your first enriched record before your coffee gets cold.
The free plan includes 100 credits, and only rows that return data are charged.