Enrichments vs Clay
The Clay alternative for people who just want the API
Clay is a workflow canvas with enrichment inside it. If you already have the workflow — in code, in your CRM, in an agent — this is the enrichment underneath it, without the table in the middle.
| 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 Clay
The differences that decide it, including the ones that go the other way.
| Feature | Enrichments | Clay |
|---|---|---|
| Shape of the product | An API and a CSV upload. Enrichment as a call. | A spreadsheet-style canvas where enrichment is one step in a workflow. |
| Who operates it | Engineers and RevOps, from code or an agent. | GTM teams building visually, with no code required. |
| Provider choice | One waterfall, run for you, cheapest source first. | A large catalogue of providers you select and sequence yourself. |
| Billing model | Credits, charged only when a field comes back. Free plan: 100 credits, then $69/mo. | Credit-based, with credit cost varying by provider and step. |
| Failed lookups | A lookup that returns nothing is not charged, and every charge is in an auditable ledger. | Credit consumption depends on the provider a step calls. |
| Cost predictability | Preview the cost of a run before it executes. | Harder to predict across a multi-provider workflow. |
| Use from an AI agent | Native MCP endpoint. Connect it to Claude or ChatGPT and enrich in the chat. | Automation is built in the canvas rather than exposed as an MCP endpoint. |
| Time to first record | One API call, or one CSV upload. | Build the table and the workflow first. |
| Start free |
An API and a CSV upload. Enrichment as a call.
A spreadsheet-style canvas where enrichment is one step in a workflow.
Engineers and RevOps, from code or an agent.
GTM teams building visually, with no code required.
One waterfall, run for you, cheapest source first.
A large catalogue of providers you select and sequence yourself.
Credits, charged only when a field comes back. Free plan: 100 credits, then $69/mo.
Credit-based, with credit cost varying by provider and step.
A lookup that returns nothing is not charged, and every charge is in an auditable ledger.
Credit consumption depends on the provider a step calls.
Preview the cost of a run before it executes.
Harder to predict across a multi-provider workflow.
Native MCP endpoint. Connect it to Claude or ChatGPT and enrich in the chat.
Automation is built in the canvas rather than exposed as an MCP endpoint.
One API call, or one CSV upload.
Build the table and the workflow first.
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 Clay — common questions
- Is this a replacement for Clay?
- Only if what you wanted from Clay was the enrichment. Clay's value is the canvas and the provider catalogue; if your team builds workflows there, keep it. If you were using it as an expensive way to call one enrichment step, this is that step on its own.
- Can I call this from inside Clay?
- Yes, as an HTTP step against the REST API. Some teams run Clay for orchestration and point the enrichment step here.
- What does 'waterfall' mean here?
- Sources are tried in order and each one is asked only for the fields the ones above it did not return, so a paid source is reached only when everything cheaper came up empty. You are billed for the field, not for the attempts.
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.