FullEnrich vs Datagma (2026): Data, Pricing and API Compared

Datagma is the cheaper way to fill emails and a few hundred mobiles from a name and a company. FullEnrich is the better pick when volume or mobile hit rate matters, because it asks 25+ sources for each contact. Neither publishes a price at 1M records.

Verdict

• Pick FullEnrich if you run batch pipelines of thousands of contacts and want one credit meter for emails, mobiles and search, with MCP and a documented rate limit (FullEnrich pricing, September 2026).
• Pick Datagma if you enrich a few thousand contacts a month, need direct mobiles from a name plus a company, and want the lower entry price (Datagma pricing, September 2026).
• Pick neither if you build whole audiences by API at volume, with filters to apply before you spend. LeadOcean is one option, covered below.

Side by side

Data and coverage

The two tools are built differently, so the numbers do not line up. FullEnrich holds a searchable index and waterfalls to other vendors for contact data. Datagma looks things up live and keeps no database of its own.

FullEnrich lists 800M people and 50M companies for search. Search results carry no emails or phones. Its 1.6B figure is a customer quote about coverage, not a database size (FullEnrich MCP page, September 2026).

Datagma gives no dataset size. It says it does not use a database and delivers data in real time (Datagma docs, September 2026). That is a design choice, but it means you cannot size an audience before you pay.

Email quality is a claim on both sides. FullEnrich runs a triple verification and returns four statuses: deliverable, high probability, catch-all and invalid (FullEnrich docs, September 2026). Datagma verifies every email it returns. An unverifiable catch-all comes back as "most probable" and is not billed (Datagma docs, September 2026).

Phones are where they split. FullEnrich's waterfall asks 25+ sources, so a miss at one is a chance at the next. Datagma sells direct mobiles from a name plus a company, with no profile URL, and flags numbers on WhatsApp (Datagma, September 2026). Run 200 rows of your own list through both before you commit.

API and developer experience

Both have a REST API on every plan. Datagma answers in one GET call. FullEnrich starts a job and tells you when it finishes. Placeholders below stand in for real people.

Datagma, find a mobile from a full name and a company domain.

curl "https://gateway.datagma.net/api/ingress/v2/full?apiId=$DATAGMA_API_KEY&data=acme.com&fullName=Jane%20Doe&phoneFull=true"

The call is synchronous. Your key goes in the apiId query parameter, so it appears in every request URL. Datagma charges for a match only, and a person response costs two credits (Datagma API, September 2026).

FullEnrich, start a bulk enrichment for one contact. It takes up to 100.

curl --request POST \
  --url "https://app.fullenrich.com/api/v2/contact/enrich/bulk" \
  --header "Authorization: Bearer $FULLENRICH_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "name": "Jane Doe",
    "webhook_url": "https://example.com/webhook",
    "data": [{
      "first_name": "Jane",
      "last_name": "Doe",
      "domain": "acme.com",
      "enrich_fields": ["contact.work_emails", "contact.phones"]
    }]
  }'

The job is asynchronous. You get the result on your webhook, or you poll with the enrichment id (FullEnrich docs, September 2026). That suits batch work. It is awkward for a lookup inside a user-facing request.

Limits differ in shape. FullEnrich allows 60 calls a minute across Enrich, Reverse Email and Search, with 100 contacts per bulk call. That is 6,000 contacts a minute, and calls over it get an HTTP 429 (FullEnrich docs, September 2026). Datagma's docs list no request limit, so ask before you plan a heavy batch.

On MCP, FullEnrich runs its own server on every plan. Search is a free preview of the first 10 results plus the total (FullEnrich help, September 2026). Datagma has no first-party server in its docs. The Zapier-run one lists five actions: detect a job change, find an email, find employees, enrich, and find a mobile (Zapier, September 2026).

Pricing

Both charge only for a hit. FullEnrich credits roll over 3 months on monthly plans and 12 on annual ones (FullEnrich pricing, September 2026). Datagma credits roll over up to 12 months on paid plans (Datagma pricing, September 2026).

The first example is 10,000 work emails a month, one credit each, at list price.

At 10,000 emails Datagma costs about half: $249 against $499, or $0.0249 an email against $0.050. FullEnrich's price per credit is $0.050 at that tier (FullEnrich pricing, September 2026). Datagma's Expert plan has room for 22,500, so cost per email falls as you use more of it.

Mobiles change the picture. Datagma Expert lists 750 phones a month for $249, where 750 mobiles plus 750 emails takes FullEnrich's 10,000-credit tier. Datagma's header reads "3 phones or 100 emails" for the free plan, and every plan keeps the same 30 emails per phone, so phones may share one allowance with emails. Ask Datagma before you plan on both. Past 750 mobiles, Datagma stops publishing a price, while FullEnrich keeps going to 100,000 credits.

At 1M, neither publishes a price. FullEnrich's top monthly tier is 100,000 credits for $3,500, which covers 10% of a million lookups. Above that the page says contact sales. The yearly toggle stops at 1,200,000 credits a year for $37,800 (FullEnrich pricing, September 2026). FullEnrich does not say whether yearly credits arrive upfront or month by month, so that tier is not a confirmed path to 1M lookups in one month.

Datagma's largest self-serve plan covers 22,500 emails a month, 2.25% of a million. Enterprise is a custom quote (Datagma pricing, September 2026). A million lookups in one month needs a quote from either vendor.

Check the yearly discount before you rely on it. Datagma's page says 20% off, but the Expert plan shows $209 a month billed yearly against $249 monthly, about 16% (Datagma pricing, September 2026). FullEnrich's yearly price is about 10% below monthly.

Plan against hit rate, not list rate. Both charge only for found data, so real cost per contact sits below the list rate. Neither publishes a hit rate you can plan on, apart from FullEnrich's own 80% claim on work emails.

Side services add up too. FullEnrich search costs 0.25 credits per person or company returned, so browsing 10,000 people is 2,500 credits before you enrich anyone (FullEnrich docs, September 2026). Datagma's Find People call returns up to 10 people for 10 credits on a hit, and 1 credit on a miss (Datagma API docs, September 2026).

Seats are a cost on one side only. FullEnrich has unlimited users on every plan. Datagma includes 1, 3 or 5 seats and charges $5 a user a month for more (Datagma pricing, September 2026).

Where FullEnrich wins

• Mobile hit rate on paper. A waterfall over 25+ sources finds numbers one lookup misses.
• Volume. Public tiers run to 100,000 credits a month, against 22,500 emails on Datagma's largest plan.
• Search and MCP from the vendor itself, on every plan, with a documented rate limit.
• Unlimited users on every plan.
• A published 800M-person search index you can query before you enrich.

Where Datagma wins

• Price at low volume. $249 lists 22,500 emails a month on Expert, where FullEnrich charges $499 for 10,000 credits.
• A free plan that renews every month, where FullEnrich's trial is 50 credits once.
• Name plus company in, mobile out, with a WhatsApp check.
• A Job Change Detect endpoint and a Chrome extension on every plan (Datagma API docs, September 2026).
• Catch-all addresses it cannot verify are not billed.

If you need volume through an API

LeadOcean is the data layer only: 693M people and 63M companies over REST and MCP. Pro is $499 a month flat with no credits and no per-record price, and Free gives you 1,000 records, one-off, with no card. The limit is 100 requests per second per key, and POST /v1/exports returns up to 50,000 rows per request. LeadOcean has no waterfall, Chrome extension or job change alerts, so it replaces neither tool for hand-finding mobiles. See pricing.

FAQ