Data enrichment APIs you can pay per call

What a B2B enrichment API does, and who calls it

A data enrichment API adds sourced context to a record you already hold. A company domain might gain a legal identity, industry, technology stack or social links. A professional profile might gain a current role or work email. The useful result is a matched field with evidence and a date, rather than an unexplained increase in the number of columns.

For an agent, enrichment often happens between discovery and a decision. A procurement assistant resolves a company before preparing a review, or a CRM helper checks whether a professional still works at the business already on file. Keep the original input, entity match and field-level provenance so the added context can be reviewed or replaced later.

This page covers B2B company and professional enrichment, related discovery, domain evidence and commercial signals. It includes 12 services as of October 26, 2026 and leaves out 13 candidates that pass the listing checks but lack a matching priced task route. Token or wallet enrichment, threat-intelligence indicators, factual-claim grounding and deterministic email-format checks are different tasks. A daily access pass is also a different purchase unit from a paid enrichment request and is not used to price this comparison.

What the 12 B2B enrichment services actually return

The classification follows documented endpoint products. It counts services per type, so a service offering more than one product can appear in more than one row. Each quote comes from the cheapest priced endpoint of that type, with its source route attached.

Each price is the cheapest endpoint of that service for that kind of data: the same number wherever this page quotes it.

Use this table to narrow the product before comparing hosts. A matching type identifies an advertised output, not verified accuracy or complete coverage of your input. The request schema, source period and returned missing-value states still need to fit the job. Read the service-specific notes below for limits that a broad product label cannot express.

Public website or DNS evidence is described by agentstools, Qonoro Intelligence API and DOHMAN Machine Services; People Data Labs is named by Deepline GTM API and MDataAccess. Preserve the declared source behind an added field, especially when a gateway combines several upstream products.

The 12 B2B enrichment APIs and their matching endpoint prices

One row per service, ordered by measured buyers. The price names the selected task route rather than an unrelated utility on the same host. Primary types determine the preferred quote; a service without a primary type uses its cheapest matching task endpoint.

$/CALL is the price of the endpoint named under it: the cheapest company identity and profile enrichment, professional person profiles and work-email discovery endpoint of the service or, for a service without one, its cheapest B2B enrichment endpoint. Never the cheapest tool of a gateway. Other kinds of data have their own price in the tables below. B2B ENRICHMENT ENDPOINTS counts the B2B enrichment endpoints out of all the endpoints the service lists. BUYERS 30D counts distinct wallets that paid the whole service on-chain in 30 days, not only its B2B enrichment endpoints. "Generalist" marks a gateway that sells more than three unrelated kinds of tools: it is never called the cheapest.

The buyer figure covers the host's measured payments, so it does not establish demand for this particular endpoint. A gateway can sell unrelated tools and a reseller can share an upstream source with another listing. Use these signals to investigate operational fit rather than inferring independent data collection or product quality from wallet counts.

How to choose a B2B enrichment API

Resolve before adding fields

Decide which identifier is authoritative for the record. A company domain can point to a brand or group, and a person can change employers. Preserve the original query and matching evidence before merging a response. Ambiguous candidates belong in a review state rather than being written into the first similar record.

Demand field-level provenance

Different fields can come from different sources and dates. A registry name, inferred employee count and website technology observation should retain their individual meanings. Store source URLs, as-of dates and explicit missing reasons where available. A confidence score should supplement those facts instead of hiding their origin.

Compare the paid unit

An enrichment request, a search result, a bounded batch and a delivered work-email match are different units. Read result limits and failure billing before multiplying a per-call quote by a target list size. A job submission may need a later completion check, and a no-match response needs its own accounting state.

Separate observations and recommendations

An open job or a filing is a dated observation. Buying intent, fit scores and suggested next actions are interpretations based on a provider method. Keep them in separate fields and expose the cited evidence when presenting a recommendation. Generating outbound copy is a later drafting step rather than additional company evidence.

Which endpoint fits which job

Start with the job, then compare the candidates whose classified endpoints match it. The price in a job table is tied to those types, which can differ from the service's selected price in the main table. Do not assume that one host's entry quote covers another product it sells.

Fill a known company record

Start with a domain, legal name or durable identifier and retain the original key. Separate registry identity from website claims and technology detection. Update a field only when the entity match and source fit the record; preserve an older manually reviewed value when the new response is ambiguous.

Candidates today, most buyers first: agentstools ($0.015/call, generalist, 127 buyers) · AgentBIT ($0.003/call, generalist, 71 buyers) · Deepline GTM API ($0.1/call, 43 buyers) · Apollo via Locus ($0.038/call, 36 buyers) · Linked Panda ($0.05/call, 34 buyers) · Qonoro Intelligence API ($0.01/call, generalist, 14 buyers) · DOHMAN Machine Services ($0.003/call, 4 buyers) · Zinin M2M Hub ($0.01/call, generalist, 3 buyers) · MDataAccess ($0.15/call, 1 buyer) · PayForAPI resale doors — people enrichment + web search ($0.15/call, generalist)

Resolve a professional person

Use the strongest available matching key and check the relationship to the intended company. A common name or a stale role can produce an apparently plausible profile. Keep source, observation date and alternatives so a later job change does not silently overwrite a different individual.

Candidates today, most buyers first: vaaya ($0.01/call, generalist, 57 buyers) · Deepline GTM API ($0.12/call, 43 buyers) · Apollo via Locus ($0.038/call, 36 buyers) · Linked Panda ($0.05/call, 34 buyers) · Qonoro Intelligence API ($0.05/call, generalist, 14 buyers) · MDataAccess ($0.35/call, 1 buyer) · PayForAPI resale doors — people enrichment + web search ($0.1/call, generalist)

Find a work email

Distinguish discovery from validation. A DNS check can show domain mail configuration without finding a person's address or confirming a mailbox. Inspect match and quality states, charging on no match, and asynchronous completion rules before treating an email lookup as a successful enriched record.

Candidates today, most buyers first: Linked Panda ($0.05/call, 34 buyers) · PayForAPI resale doors — people enrichment + web search ($0.05/call, generalist) · Deploid Enrich ($0.15/call)

Discover companies or decision-makers

Specify the target geography, company criteria and role. Check the paid unit: one profile, one company, a results page or a bounded batch can require different budgets. Deduplicate candidates using stable keys before enriching them again and retain the criteria that produced the list.

Candidates today, most buyers first: vaaya ($0.01/call, generalist, 57 buyers) · Apollo via Locus ($0.005/call, 36 buyers) · Linked Panda ($0.3/call, 34 buyers) · Qonoro Intelligence API ($0.05/call, generalist, 14 buyers) · MDataAccess ($0.15/call, 1 buyer) · PayForAPI resale doors — people enrichment + web search ($0.15/call, generalist)

Attach commercial signals and qualification

Keep observed jobs, filings and published announcements separate from inferred buying intent and fit scores. Store source dates and evidence URLs. A recommended sales action is a proposed interpretation, so expose the supporting facts instead of inserting that recommendation into a verified-facts field.

Candidates today, most buyers first: Linked Panda ($0.05/call, 34 buyers) · Qonoro Intelligence API ($0.05/call, generalist, 14 buyers) · Zinin M2M Hub ($0.01/call, generalist, 3 buyers)

Service details and limits to check

The notes below are read from the provider's description and endpoint list captured on October 21, 2026. They attribute advertised capabilities and source information; x402-list has not independently tested the accuracy of the delivered data or generated output. Price, uptime and buyer tokens come from the current page model.

MDataAccess

MDataAccess lists /company and /person for known-record enrichment, priced at $0.15 and $0.35. Discovery routes start at $0.15. The descriptions identify PDL search and explicitly say a paid company search returns one company and a paid people search returns one profile. That unit matters when projecting a list-building budget: an endpoint named search does not establish a page of results. Its decision-maker and lead routes are separate products. Preserve the original matching inputs and inspect whether the response resolves the intended individual or company before updating a CRM record that already contains manually verified information.

6 B2B enrichment endpoints of 7 · $0.15/call (GET /company) · Base · uptime 30d 100% · 235 ms · 1 buyer in 30 days

Apollo via Locus

Apollo via Locus lists organization enrichment at $0.038, person enrichment from $0.038 and discovery from $0.005. The route list distinguishes organization search, people search, individual people enrichment and bulk people enrichment. The endpoint descriptions are brief, so the path and service description establish the product family without establishing a field list, batch allowance or a guaranteed contact match. Inspect the request schema and response coverage before choosing the bulk route. A wrapper relationship also matters for failure handling: retain the upstream product identity rather than treating a reseller response as an independently collected company dataset.

5 B2B enrichment endpoints of 5 · $0.038/call (POST /apollo/org-enrichment) · Base · uptime 30d 99.9% · 300 ms · 36 buyers in 30 days

DOHMAN Machine Services

DOHMAN Machine Services describes /functions/v1/x402-domain-company-enrich as public HTTPS and DNS enrichment. The company-type and domain-evidence quote is $0.003. The endpoint description lists homepage metadata, JSON-LD organization evidence, social and contact-page links, technology hints, DNS and evidence hashes. This can fill source-backed website context around a company domain without establishing a personal contact database. The same service also lists hashing, release assurance and package intelligence; those unrelated cheaper tools do not set its enrichment price. Keep a website claim separate from a registry fact, and retain the source URL or hash so a later reviewer can inspect the basis of an added field.

1 B2B enrichment endpoint of 23 · $0.003/call (GET /functions/v1/x402-domain-company-enrich) · Base · uptime 30d 100% · 166 ms · 4 buyers in 30 days

agentstools

agentstools describes /enrich/domain as a business-domain profile from public registration, DNS, TLS and homepage sources. It costs $0.015. The description includes JSON-LD organization information, social links, role contacts and technology detection, with blocks left null when a source fails. It explicitly limits the product to business or domain data rather than personal data about individuals. A null technical block should therefore remain distinguishable from a negative finding or an absent business. Use the route when a domain is the starting key and you need public evidence, then resolve legal identity separately if the workflow requires a verified corporate counterparty.

1 B2B enrichment endpoint of 20 · $0.015/call (GET /enrich/domain) · Base · uptime 30d 100% · 156 ms · 127 buyers in 30 days

Deploid Enrich

Deploid Enrich describes one work-email lookup from a LinkedIn profile or a name and company. Its email-discovery quote is $0.15. The provider describes an asynchronous public pilot, free polling and charging only for a DELIVERABLE work-email result; no match and rejected quality are described as uncharged. It explicitly excludes personal emails and phone numbers and says the product is intended for occasional enrichment and fallback lookups rather than bulk prospecting. Model the result states directly instead of treating a submitted job as a successful contact match. Preserve the matched company and person evidence with the returned work email before adding it to an existing record.

1 B2B enrichment endpoint of 1 · $0.15/call (POST /v1/work-email) · Base · uptime 30d 100% · 889 ms · 0 buyers in 30 days

Qonoro Intelligence API

Qonoro lists separate company profiles, professional person profiles, search, domain intelligence, commercial signals and qualification. Company-type endpoints start at $0.01, person enrichment costs $0.05 and discovery starts at $0.05. Domain intelligence costs $0.03, commercial signals start at $0.05 and qualification costs $0.6. Its descriptions advertise source URLs and confidence for profile or discovery products, and recommendations in research and qualification outputs. Keep retrieved facts separate from an inferred intent, score or recommended next action. A cited source and a confidence number are useful review inputs; they do not establish that every field was independently verified by x402-list.

16 B2B enrichment endpoints of 21 · $0.01/call (POST /v1/domain-resolver/resolve) · Base · uptime 30d 100% · 257 ms · 14 buyers in 30 days

What the calls cost at different volumes

The median selected endpoint costs $0.0265 per call. At that same request shape, 100,000 calls would cost $2,650.00. This multiplication is a comparison aid, not a provider invoice or a promise that an arbitrary request will use the reference quote.

Each service at the price of its main B2B enrichment endpoint, the one named in the table above.

Budget for useful results as well as submissions. A retry, an additional research step or a separate product can add another charge; no-match and partial-failure handling depend on the particular endpoint. For a variable body, model or input size, inspect the returned payment requirement for that exact request. Keep the quoted route and paid unit in the job record rather than projecting from the cheapest unrelated tool on a gateway.

How an agent reaches the HTTP 402 payment step

An unpaid request lets the caller inspect a payment requirement. The example below pairs the documented route with a real HTTP 402 payload previously captured by x402-list's monitor. Its capture date belongs to that evidence; it is not a claim that a paid result was tested today. The documented route has a reference quote of $0.15; inspect the challenge for the exact request terms.

curl -i 'https://api.mdataaccess.com/company?name=Example'

HTTP/1.1 402 Payment Required

{
  "x402Version": 2,
  "resource": {
    "url": "https://api.mdataaccess.com/company"
  },
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "version": "2"
      },
      "payTo": "0x9aa51F7141dC677aB2dA923C62007dB3051Aa017",
      "amount": "150000",
      "scheme": "exact",
      "network": "eip155:8453",
      "maxTimeoutSeconds": 300
    }
  ]
}

402 of MDataAccess for GET /company, as stored by the monitor (terms unchanged since 2026-09-23, last check 2026-10-26 17:43 UTC), with every accepted payment exactly as stored and without error, extensions, resource.tags, resource.mimeType, resource.description and resource.serviceName, which are not payment terms: the full body is also on the service page, under Payment evidence. Amounts are in the asset's smallest unit: USDC has 6 decimals, so 150000 is $0.15.

Inspect the request schema before adapting the example. A documented POST endpoint needs the corresponding JSON inputs; a GET endpoint needs valid query values. Keep the payment requirement tied to the intended resource, network, asset and request. The captured challenge shows what payment access looks like. It does not prove that a paid call will return accurate output, complete a background job or satisfy the application's success criteria.

What this comparison measures

The listing requires an online, payment-ready service, a usable description, an advertised price and at least 90% measured uptime over 30 days. Task selection then reads its endpoint list and keeps the matching routes. Those listing checks establish a discovery threshold, not a certification of output accuracy.

Uptime is based on monitoring checks; average latency measures those checks. Buyer counts are distinct paying wallets observed for the service in the measurement window, with the limits described on the service page. A successful unpaid HTTP 402 response confirms a payment challenge rather than successful delivery after settlement.

Treat the provider's output contract and our monitoring as complementary evidence. Test a representative input, inspect source dates and missing states, and define a successful result before putting a recurring workflow on the endpoint. For comparison details, open the linked service page and the site's measurement methodology. Recheck the exact payment requirement when the input or advertised product changes.

Questions

How to pay

Each service answers an unpaid call with HTTP 402 and its price; your agent signs a USDC payment on the listed network and retries. No API key, no account, no subscription. See what x402 is.