Enrichments vs Lusha
The Lusha alternative for bulk, not for browsing
Lusha is built around looking someone up in the browser. This is built around enriching ten thousand rows on a schedule — same kind of data, a different unit of work.
| 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 Lusha
The differences that decide it, including the ones that go the other way.
| Feature | Enrichments | Lusha |
|---|---|---|
| Unit of work | Bulk and programmatic — a list, a job, an API call. | One contact at a time, mostly in a browser extension. |
| Billing model | Credits, charged only when a field comes back. Free plan: 100 credits, then $69/mo. | Per-seat plans with monthly credit allowances. |
| Failed lookups | A lookup that returns nothing is not charged, and every charge is in an auditable ledger. | Credits are generally spent on the lookup. |
| Seats | No seat licences. One API key per organisation, shared by the whole team. | Per user, with credits attached to the seat. |
| Access surfaces | REST API, MCP server, in-product chat agent, and CSV upload — one key for all four. | Extension, web app, integrations and an API on higher tiers. |
| Use from an AI agent | Native MCP endpoint. Connect it to Claude or ChatGPT and enrich in the chat. | No first-party MCP endpoint. |
| Browser extension | None. This is an API and a CSV tool. | Mature extension, and the main reason people buy it. |
| 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. | Yes — a core part of the product. |
| Start free |
Bulk and programmatic — a list, a job, an API call.
One contact at a time, mostly in a browser extension.
Credits, charged only when a field comes back. Free plan: 100 credits, then $69/mo.
Per-seat plans with monthly credit allowances.
A lookup that returns nothing is not charged, and every charge is in an auditable ledger.
Credits are generally spent on the lookup.
No seat licences. One API key per organisation, shared by the whole team.
Per user, with credits attached to the seat.
REST API, MCP server, in-product chat agent, and CSV upload — one key for all four.
Extension, web app, integrations and an API on higher tiers.
Native MCP endpoint. Connect it to Claude or ChatGPT and enrich in the chat.
No first-party MCP endpoint.
None. This is an API and a CSV tool.
Mature extension, and the main reason people buy it.
Mobile numbers from a LinkedIn profile URL, 10 credits per number found. Unverified — no deliverability equivalent exists for a phone, so none is implied.
Yes — a core part of the product.
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 Lusha — common questions
- Does Enrichments have a Chrome extension?
- No. The product is a REST API, an MCP server, an in-product chat agent and CSV upload. If a browser extension is central to how your team works, Lusha is the better choice.
- Can I enrich a list I exported from Lusha?
- Yes. Upload the CSV, map your columns, preview the cost, and download the result. Only rows that return data are charged.
- What about phone numbers?
- Mobile numbers are available and billed per number found — misses are free. Unlike a work email they carry no deliverability verdict, because nothing can check a phone the way a mailbox can be checked. Whether a number is lawful to call is your call to make, not ours to imply.
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.