Office hours: Build your self-driving GTM engine·Oct 29, 9:00am PT, onlineRegister→
Cargo
  • PrimitivesData ModelsYour companies, contacts and deals, merged from every sourceContextWhat your team knows, as files every agent readsTerritoriesWho sells where, defined onceMailboxesMailboxes in your reps' names, warmed up and kept under limitsToolsThe actions your agents, plays and reps callAgentsAI that researches, decides and writes, reading your contextPlaysWorkflows that run on a trigger or a schedule, with retriesAppsInternal apps for your reps, hosted on Cargo
    Add-onsChrome ExtensionSell faster, right in your browserButtonTrigger AI agents inside your CRMFormTurn any tool into an embeddable formSlackTag Cargo in Slack. It does the GTM workGitHubPlan on every pull request, deploy on merge
    MoreProjectsDefine your entire GTM in codeCLIUse Cargo from your terminalMCPUse Cargo from Claude and ChatGPTDeveloper resourcesCargo API docs, OpenAPI spec, auth docs, webhooks, MCP serverAPI ReferenceExplore the Cargo APIDocumentationLearn how to use CargoIntegrationsConnected to your entire GTM stack
  • VeriffHow Veriff replaced MuleSoft with Cargo under NetSuite, Stripe and SalesforceAugmentHow Augment Code routes developer sign-ups to reps in under an hourWeights & BiasesHow Weights & Biases ships a new purchase signal in 2 days on CargoSee all
  • Pricing
  • Cookbooks
  • Blog
Sign in
Cargo platform data

Cargo enrichment benchmarks

How often each enrichment job finds a result on Cargo, and what it costs, measured on 9,189,315 runs over 90 days to Oct 16, 2026.Cargo is go-to-market infrastructure that runs enrichment as code, across the data providers it connects. These are its own platform figures (Cargo platform data, 90 days to Oct 16, 2026), one row per job, never per provider.

Start building
9,189,315

Enrichment runs, across every Cargo workspace

6 jobs

Measured per job, never per provider

90 days

Jul 18, 2026 to Oct 16, 2026

Oct 16, 2026

Last regenerated, from the same query every month

Every job, one row

Found rate and credit cost, job by job

Measured at run level over the 90 days to Oct 16, 2026. A run counts once per job, however many providers it chained.

Cargo enrichment benchmarks by job: runs, workspaces, run-level found rate, list price per call, and the share of misses charged 0 credits.
JobRunsWorkspacesFound rateList price per callMisses charged 0 credits
Company enrichment2,454,22821091.6%0.01 to 3 credits99.8%
Email verification2,088,28360366.4%0.01 to 1 credits61.1%
Work email finding1,850,40494163.6%0.1 to 2 credits100.0%
LinkedIn profile enrichment1,824,33119093.6%0.25 credits100.0%
Mobile phone finding899,82910,57881.2%0.5 to 15 credits99.2%
LinkedIn URL from a name72,2404723.9%0.25 credits100.0%

Scroll the table sideways for workspaces, found rate, list price and free misses.

Job by job

What counts as found, and what each call lists at

One card per job: the result that makes a run found, the actions Cargo prices for it, and the skill that runs it.

Company enrichment

91.6%found

At least one step in the run returned a company record for the domain or name it was given.

Lists at 0.01 to 3 credits per call, across 10 priced actions
aiArk.enrichCompany0.01companyEnrich.enrichByDomain0.25linkedin.enrichCompany0.25linkedin.enrichCompanyFromDomain0.5prospeo.enrichCompany0.5apolloio.enrichOrganization1enrichCrm.enrichCompany1oceanio.enrichCompany1waterfall.enrichCompany1peopleDataLabs.enrichCompany3
Enrich company data

Email verification

66.4%found

The check marked the address valid. A check that marked it not valid counts as a miss.

Verification is billed per check, so a check that returns invalid is still charged, which is why this job's share of free misses is lower than the others.

Lists at 0.01 to 1 credits per call, across 11 priced actions
icypeas.verifyEmail0.01kitt.verifyEmail0.05bounceban.verifyEmail0.1enrichley.verify0.1enrowio.verifyEmail0.1waterfall.verifyEmail0.1zeroBounce.verifyEmail0.1neverBounce.verifyEmail0.2findyMail.verifyEmail0.25bouncer.verifyEmail0.3hunter.verifyEmail1
Verify an email list

Work email finding

63.6%found

At least one step in the run returned an email address for the person.

Lists at 0.1 to 2 credits per call, across 11 priced actions
icypeas.findEmail0.1findyMail.findEmail0.5hunter.findEmail0.5leadmagic.findEmail0.5prospeo.findEmail0.5datagma.findEmail1dropContact.findEmail1enrichCrm.findEmail1enrowio.findEmail1fullenrich.findEmail1forager.findWorkEmail2
Find work emails

LinkedIn profile enrichment

93.6%found

The step returned the profile behind the LinkedIn URL it was given.

Lists at 0.25 credits per call, across 1 priced action
linkedin.enrichProfile0.25
Enrich a LinkedIn profile

Mobile phone finding

81.2%found

At least one step in the run returned a phone number for the person.

Lists at 0.5 to 15 credits per call, across 10 priced actions
aiArk.findMobilePhone0.5prospeo.findPhone3findyMail.findPhone5forager.findPhone5fullenrich.findPhone6fullenrich.findPhoneAndEmail7waterfall.findPhone7datagma.findPhone8datagma.findPhoneAndEmail8cleon1.findPhone15
Waterfall enrichment

LinkedIn URL from a name

23.9%found

The step returned a LinkedIn profile URL for the name and company it was given.

Lists at 0.25 credits per call, across 1 priced action
linkedin.findProfileUrl0.25
Find a LinkedIn URL
Method

How these numbers are measured

One query over the connector steps Cargo ran, aggregated per run and per job. Nothing here is a provider's own claim.

Window
90 days, Jul 18, 2026 to Oct 16, 2026, in UTC.
Population
Every Cargo workspace. The figures are aggregates: no workspace or record is identifiable.
Unit
One run per job, however many providers it chained, and whatever else the run did.
Found
Any step of that job in the run returned a result.
Excluded
Runs where no step marked found or missed, such as a provider error. They count in runs and workspaces, and in neither rate.
Not counted
A provider action that can return a person or a company depending on how the step was configured, which the run does not record. It is left out of every job rather than guessed into one.
Prices
Read by hand from each action's credits definition in Cargo's code. Actions that run only on your own provider key have no Cargo price and are not listed.
Your own key
A run on your provider API key is charged 0 Cargo credits. It counts toward the found rate, and raises the share of misses charged nothing.
Refreshed
The same query runs monthly and rewrites the figures. It last ran on Oct 16, 2026.
Example run, work email findingOne run, three providers chained
prospeo.findEmailno result0 credits
hunter.findEmailno result0 credits
fullenrich.findEmailfound1 credit
Counted as1 run, found, 1 credit

A run counts once, however many providers it chained. Two of these calls came back with nothing and cost nothing, one returned an address: one found run, one credit.

Limits

What not to infer from them

Three readings these figures do not support, each one a question we get asked about them.

Not a provider ranking

Inside a waterfall a later provider only sees the records the earlier ones missed, so a provider's rate in a chain measures its position as much as its data. This page reports jobs, not providers.

Not your rate

Lists differ by customer (region, seniority, how clean the inputs are), and a found rate follows the list. Run a sample of your own records before you budget a full list.

Not the effect of a waterfall

Runs that chain more providers find more often, but they are also run on different lists by different teams, so the gap is correlational, not the measured gain from adding a provider.

Your list, not ours

Run it on your own records

A found rate follows the list it ran on, so the only figure that settles a budget is yours. Install the CLI, sign in without a browser, and run a sample.

CRM enrichment cookbookFind work emailsCredits and pricingEnrichment on Cargo
Start
Install Cargo by following https://api.getcargo.io/INSTALL.md
Paste into Claude Code, Cursor, Codex, Gemini CLI, Devin or Replicas.
$npm install -g @cargo-ai/cli cargo-ai login --email you@company.com
A new account starts with 100 free credits and no card.

Build the self-driving GTM engine

Your coding agents build it on Cargo.Or our team builds, operates and improves it with you.

Start building
Cargo
Backed byY CombinatorSOC 2 Type IICertified
LinkedinX

Product

Data ModelsContextTerritoriesMailboxesToolsAI AgentsPlaysAppsIntegrationsPricing

Add-ons

Chrome extensionButtonFormSlackGitHub

Build

DocsDeveloper resourcesCargo API docsCargo OpenAPI specCargo auth docsCargo webhooksCargo MCP serverProjectsClaude CodeCodexCursorAll coding agents

Resources

ReportsBlogCustomer storiesCookbooksEnrichmentRoutingSignalsScoringCRM hygieneAd audiencesGTM skillsGTM EngineeringGlossaryCompareCargo x ClayCargo x WorkatoCargo x n8nCargo x DeeplineCargo x DefaultCargo x LeanDataCargo x UnifyCargo x ValleyCargo x GojiberryCargo x PhantomBusterCargo x ZapierCargo x ApolloCargo x Chili PiperCargo x Common RoomCargo x MakeCargo x Tray.io

Company

ManifestoCommunityEventsJobsPartners DirectoryPartner Program

Legal

SecurityTerms of servicePrivacy PolicyRefundsDPASupport
© 2026 Cargo
 ////////    ///////    ////////     ////////    ///////
///         ///   ///   ///   ///   ///         ///   ///
///         ///   ///   ///   ///   ///         ///   ///
///         /////////   ////////    ///  ////   ///   ///
///         ///   ///   /// ///     ///   ///   ///   ///
///         ///   ///   ///  ///    ///   ///   ///   ///
 ////////   ///   ///   ///   ///    ///////     ///////

$ npm install -g @cargo-ai/cli