Enrichments vs Datagma

Email, mobile and firmographics from one key

One credit balance across a REST API, an MCP server your agents can call, an in-product chat agent and CSV upload — charged only when a field comes back.

ContactEmail
Liam Foster
Liam Foster
Queued
Maya Torres
Maya Torres
Queued
Ethan Brooks
Ethan Brooks
Queued
Zoe Martin
Zoe Martin
Queued
Andre Willis
Andre Willis
Queued
Chloe Bennett
Chloe Bennett
Queued
Noah Klein
Noah Klein
Queued
Priya Shah
Priya Shah
Queued
Kenji Tanaka
Kenji Tanaka
Queued
Ava Boone
Ava Boone
Queued

Enrichments vs Datagma

The differences that decide it, including the ones that go the other way.

Billing model
Enrichments

Credits, charged only when a field comes back. Free plan: 100 credits, then $69/mo.

Datagma

Published credit plans.

Empty results
Enrichments

A lookup that returns nothing is not charged, and every charge is in an auditable ledger.

Datagma

Charges on data returned.

Use from an AI agent
Enrichments

Native MCP endpoint. Connect it to Claude or ChatGPT and enrich in the chat.

Datagma

No first-party MCP endpoint.

Phone numbers
Enrichments

Mobile numbers from a LinkedIn profile URL, 10 credits per number found. Unverified — no deliverability equivalent exists for a phone, so none is implied.

Datagma

Offered, and a long-standing part of the product.

Access surfaces
Enrichments

REST API, MCP server, in-product chat agent, and CSV upload — one key for all four.

Datagma

Web app, API and extension.

Company firmographics
Enrichments

People and company enrichment from the same key and balance.

Datagma

Offered.

Start free

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.

Enrichments Agent
What can you return for a person?
Work email and its status, title, seniority, department, location, LinkedIn URL, and the company behind it.
Ask the agent…
Cached graph
checked first · a cached row makes no upstream call
queued
Person match
title, seniority, department, location
queued
Company match
domain and firmographics
queued
Work email
address discovered for the resolved person
queued
Deliverability check
every address carries its status
queued
Enriched
0/4 verified

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.

One key, four surfaces

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.

liam@northwind.io
Northwind · Founder
verified
maya@atlas.co
Atlas · Head of Sales
verified
ethan@cobalt.com
Cobalt · VP Marketing
verified
zoe@lumen.com
Lumen · Growth Lead
verified
andre@ridge.io
Ridge · RevOps
verified
chloe@vellum.ai
Vellum · Data Lead
verified
POST/v1/people/enrich
resolving
{
"fullName": "Liam Foster",
"email": "liam@northwind.io",
"emailStatus": "verified",
"title": "Founder & CEO",
"seniority": "founder",
"department": "executive",
"companyName": "Northwind",
"companyDomain": "northwind.io",
"location": "San Francisco, CA",
"country": "US",
"linkedinUrl": "/in/liamfoster",
"source": "search.people",
"confidence": 0.94,
"lastVerifiedAt": "2026-07-21T09:14:00Z"
}
Inbound routing

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

Built for engineers

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

Keeping data current

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.

Typesense
Convex
Xata
Storyblok
Documenso
Zeabur

Enrichments and Datagma — common questions

How do the phone numbers compare?
Datagma has offered phone for longer and you should expect broader coverage. Ours are mobile numbers resolved from a LinkedIn profile URL, charged only when one is found, and never marked verified — there is no deliverability check for a phone.
What is different here?
A native MCP server, so an AI agent can enrich directly in Claude or ChatGPT, and an auditable ledger showing exactly what each row cost.
How should I compare them?
Run the same list through both and compare hit rate and total spend. The free plan makes that test free on this side.

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.