Cargo is built for agents

Name: Cargo
SKU: cargo
Availability: InStock

At each tool's entry tier, Clay charges $0.125 per work email (3 Data Credits), $0.167 per person enrichment (4) and $0.042 per company enrichment (1), at $125 for 3,000 Data Credits; Cargo charges $0.111 (1.01 credits), $0.056 (0.51) and $0.111 (1.01), at $165 for 1,500 credits. Cargo costs less per work email, email verification and person enrichment; Clay costs less per company enrichment and mobile phone, and a Cargo email lookup that finds nothing is charged 0 credits.Clay puts a person in front of a table. Cargo puts the engine in a repository an agent can read, run and fix.

Start building

Trusted by GTM teams at

Augment Code
Weights & Biases
Dust
WorkOS
Braintrust
Descript

~/cost-per-record/

Clay vs Cargo, per enriched record

Clay at $0.0417 per Data Credit ($125 for 3,000, its entry Launch pack). Cargo at $0.11 per credit ($165 for 1,500, its entry monthly tier).Cargo platform data, 90 days to Oct 16 2026: roughly 1.57M find-email runs across 800+ workspaces, 64% of which returned an email, roughly 1M emails found. The roughly 570K lookups that found nothing were charged 0 credits. A found email costs 0.1 credits with Icypeas; 0.5 with Findymail, Prospeo and Hunter; and 1 with FullEnrich, Dropcontact, Enrow and Datagma, depending on the provider that answers.

Cost per enriched record on Clay and Cargo at each entry tier
Enrichment	Clay Data Credits	Clay $ at entry tier	Cargo credits	Cargo $ at entry tier
Work email	3	$0.125	1.01	$0.111
Email verification	1	$0.042	0.11	$0.012
Person enrichment	4	$0.167	0.51	$0.056
Company enrichment	1	$0.042	1.01	$0.111
Mobile phone	13.7	$0.571	6.01	$0.661

Clay Data Credit costs are typical marketplace costs and vary by provider and waterfall depth. Clay also charges one Action per step, $0.004 at its entry Action pack, not included above. Cargo credits include the orchestration step. Larger Clay Data Credit packs do not cost less per credit; Cargo's rate falls to $0.06 per credit on its largest self-serve monthly tier. Sources: clay.com/pricing and Clay Actions & Data Credits, and the Cargo pricing page. Last verified August 2026.

The operator used to drive. Now the agent does.

Every GTM tool in market was designed around a person at a screen, because that was the only thing operating it. That assumption is what Clay is excellent at and what it cannot outgrow.

A screen is a ceiling

A table runs only what one person thought to put in it.

Company

Score

Acme

found

Initech

found

Umbrella

pending

Someone has to be here for anything to happen

A repository is not

An agent changes the whole engine and proposes each change as a diff.

$ cargo-ai project plan~ play routing.ts+ agent expansion.ts2 changes, 0 destructive

An agent opened this. A human approves it.

What changes when an agent is the operator

An agent needs state it can query, a CLI for every primitive, changes it can propose as a diff, and work that starts without anyone pressing run.

Clay and Cargo compared
	Clay	Cargo
Designed around	A person operating a spreadsheet	An agent operating a typed system
The artifact	A table, and the columns configured on it	A repository: models, tools, plays and agents
How you change it	In the UI, with an API and CLI alongside it	A pull request, planned as a diff, then deployed
How you undo it	In-app workflow versions	Roll back to any release
What starts the work	Someone presses run	The business changes
When it breaks	Open the row and look	Retries, approval gates, queryable traces

You ask, the agent builds, you approve

A change to the engine arrives as a diff somebody reads before it is live. Clay keeps workflow versions; it has no step where a proposed change waits for review.

You ask
Reactivate closed-lost accounts when their champion leaves
The agent plans it
cargo-ai project plan
+ play reactivate-on-exitcreate
+ tool detect-job-changecreate
~ model Accountsupdate
2 to create, 1 to update
You approve
pull request #248 reactivate-on-exit
merged by you, deployedrelease 41

~/choosing/

When to choose which

Clay is genuinely better at the job it was built for. The decision is whether a person or an agent is going to operate this in a year.

Choose Clay when…

A person is the operator, and that is the plan
The job is building audiences to go after
You want to test which data providers cover your market
Nobody on the team will adopt a CLI or read a diff
You work campaign by campaign: launch, learn, move on

Choose Cargo when…

Agents should run the process and humans should approve it
The engine has to live in git, with review and rollback
Work has to start when the business changes, not when someone logs in
Customer truth is spread across CRM, warehouse, product and billing
The process has to keep operating after the person who built it leaves

Use Cargo + Clay when…

Keep Clay for what it does well; move the GTM logic and agents to Cargo.

~/pricing/

Price your own workload

There is no single answer: Cargo bills one shared credit pool across enrichment and orchestration, Clay meters Actions and Data Credits separately, and which wins depends on your mix. Published pricing on both sides.

Your current Clay plan

Clay plan

Actions / month

Data credits / month

Your estimated cost

Clay

$495/moGrowth, 40K Actions + 6K DC

equivalent

Cargo

$495/mo5.5K credits/mo, steps not metered

What 5.5K credits/mo gets you on Cargo

Clay Growth: 40K Actions/mo in this tier · Cargo: steps aren't metered separately

5,445

Work emails

5,445

Companies

10,784

People

915

Phones

Start building

Estimates use published self-serve pricing and the inputs above. Actual costs vary by provider mix, AI usage and contract terms. Last verified August 2026.

See methodology and sources

Methodology: Cargo figures use published credit costs per enrichment type (shown next to each input), plus 0.01 credits per orchestration step and metered AI usage, priced against the same monthly credit tiers as our pricing page. Clay prices Actions and Data Credits as two separate tiered meters; we sum the smallest Action tier and the smallest Data Credit tier that fit the workload, on the cheapest eligible plan (Launch), so the Clay figure is never inflated. Clay Data Credit costs per enrichment (email ~3 DC, phone ~13.7 DC, person ~4 DC) are typical marketplace costs and vary by provider; every enrichment or step on Clay also consumes 1 Action, including with your own API keys. Above Clay's largest self-serve tiers (200K Actions, 50K Data Credits per month) Clay is custom-priced Enterprise, so we show no estimate. Monthly billing shown; Clay annual billing is 10% lower. Pricing sources: clay.com/pricing and Clay Actions & Data Credits. Last verified August 2026.

Move one workflow at a time

Clay exports to JSON. Cargo's coding agents read the export and rebuild each table, function and Claygent as a model, a tool or a play.

What each Clay piece becomes in Cargo
In Clay	Becomes in Cargo
Clay Table	Cargo Model or Segment
Clay Function	Cargo Tool or Play
Claygent	Cargo Agent
Workspace and business context	Cargo Context and knowledge resources
Provider connections	Cargo connectors, or your existing provider keys
Scheduled workflow	Cargo Play trigger
Table output and CRM push	Cargo CRM sync, with rules and approvals

What does not move. Run history and per-row traces stay in Clay. Community template recipes have no import path, and manual copy-paste has to become a real step. Budget the rebuild, not the export.

Or keep Clay. Cargo integrates with Clay directly, so Clay can stay an enrichment provider inside a Cargo workflow. Migrate a workflow only when there is a reason to.

“Currently downloading my Clay tables worth saving, pulling them across into Markdown to then give to Cargo. Then everything is getting rebuilt the Cargo way. Impressive”
Muttley MccGwire, nPlan, one week after his first Cargo demo

Ready to map your first workflow?

30 minutes with a GTM engineer, and you leave with a concrete plan. Teams migrating from Clay also get two months of bonus credits matched to their plan.

Or start with the quickstart

Cargo vs Clay, in short

Sources, last verified August 2026

Cargo projects Cargo docs Clay API, CLI & Agent Plugin Clay Functions Claygent Builder Clay table management Clay pricing Clay Actions & Data Credits

Who operates it. Clay is a UI-first application designed around a person working in a browser: the artifact is a table, and the logic lives in column configuration. Cargo is designed to be driven by agents: the artifact is a repository of models, tools, plays and agents in TypeScript, reachable from a CLI and over MCP, planned as a diff and deployed. With Clay you end up owning a set of tables. With Cargo you own an engine you can review, test and roll back.

Four concrete things. The engine is connected commercial state an agent can query and write to, not rows it has to scroll. Every primitive is reachable from a terminal, from code and over MCP through Claude or Cursor, so an agent can drive the product without a mouse. The whole thing lives in git, so an agent proposes changes as pull requests with a plan diff and a human approves them. And plays fire on business change rather than on someone pressing run, with retries, approval gates and queryable traces behind them.

It can be. Waterfall enrichment, email and phone discovery, AI research, scoring and CRM sync can all run natively in Cargo. But replacement is no longer required: Cargo also integrates directly with Clay, so Clay can remain one enrichment provider inside a broader Cargo workflow.

Yes. Waterfall enrichment across multiple providers is a first-class primitive in Cargo rather than a column configuration, which means the same waterfall is reusable across every play, versioned with the rest of the engine, and callable by an agent.

Yes. Cargo can now use Clay as an enrichment provider inside end-to-end GTM workflows, alongside your CRM, warehouse, scoring, routing, sequencing and agents.

It is the layer underneath. Cargo holds your commercial state (accounts, deals, territories, subscriptions and your own objects) connected across CRM, warehouse, product and billing, runs the plays that act on that state, and gives agents a typed surface to operate both. Enrichment is one thing it does, not what it is. It is also not a front end for agents you already run: it is the substrate those agents call.

It depends on the workload, which is why this page ships a calculator instead of a headline. Cargo uses one shared credit pool across enrichment and orchestration; Clay meters Actions and Data Credits as two separate tiered plans, so a workload that just crosses a tier boundary pays for the whole tier. Cargo tends to win on action-heavy workflows and when you bring your own provider keys, and the two can land within a few dollars of each other on a workload that fits Clay's tiers cleanly. Price your own mix rather than trusting either claim.

Clay bills two meters that add up to the plan price: Actions, used by the steps a table runs, and Data Credits, spent on marketplace enrichment. Launch starts at $185 a month: Actions run from 15,000 for $60 up to 200,000 for $540 a month, and Data Credits from 3,000 for $125 up to 50,000 for $2,125 a month. Growth starts at $495 a month: Actions run from 40,000 for $205 up to 200,000 for $850 a month, and Data Credits from 6,000 for $290 up to 50,000 for $2,125 a month. A workload that crosses a tier boundary pays for the whole next tier, annual billing takes 10% off, and beyond 200,000 Actions or 50,000 Data Credits a month Clay moves to custom Enterprise pricing. These are the tiers the calculator on this page uses, from clay.com/pricing; check there for changes.

It depends on the provider and how deep the waterfall goes, so treat these as typical rather than fixed. A work email costs around 3 Data Credits (about $0.13) at the entry Data Credit tier, an email verification 1 Data Credit (about $0.04), a person enrichment 4 Data Credits (about $0.17), a company enrichment 1 Data Credit (about $0.04) and a phone number 13.7 Data Credits (about $0.57), plus the Actions each step uses. Larger Data Credit packs do not cost less per credit, so buying more does not lower this rate. Cargo draws enrichment and orchestration from one credit pool, and you can bring your own provider keys; the calculator on this page prices the same mix on both.

When a person is the operator and that is the plan. Clay is the fastest path to an enriched list without involving engineering, its visual usability is genuinely better for table-first work, its provider marketplace is broader, and its community template library has no equivalent. If nobody on the team will adopt a CLI or read a diff, Clay gets you further. This page is not trying to talk you out of it.

People-hours, not credits, which is the honest answer most comparison pages avoid. Clay tables export to JSON and Cargo's coding agents rebuild them as models, tools and plays, so the export is cheap and the rebuild is the real work. Your Clay run history and per-row traces stay in Clay, and community template recipes have no import path. Start with one high-value workflow, run both in parallel, and cut over only at parity. You can also skip migrating entirely: Cargo integrates with Clay directly, so Clay can stay on as an enrichment provider inside a Cargo workflow.

“Essential. Innovative. Indispensable. Cargo let you build your unique growth engine, a much-needed solution in the market today.”

Guillaume Cabane · Co-Founder @Hypergrowth

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

//////// /////// //////// //////// /////// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// ///////// //////// /// //// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// /// //////// /// /// /// /// /////// ///////

Enrichment

Clay Data Credits

Clay $ at entry tier

Cargo credits

Cargo $ at entry tier

Work email

$0.125

1.01

$0.111

Email verification

$0.042

0.11

$0.012

Person enrichment

$0.167

0.51

$0.056

Company enrichment

$0.042

1.01

$0.111

Mobile phone

13.7

$0.571

6.01

$0.661

Clay and Cargo compared
	Clay	Cargo
Designed around	A person operating a spreadsheet	An agent operating a typed system
The artifact	A table, and the columns configured on it	A repository: models, tools, plays and agents
How you change it	In the UI, with an API and CLI alongside it	A pull request, planned as a diff, then deployed
How you undo it	In-app workflow versions	Roll back to any release
What starts the work	Someone presses run	The business changes
When it breaks	Open the row and look	Retries, approval gates, queryable traces

Clay

Cargo

Designed around

A person operating a spreadsheet

An agent operating a typed system

The artifact

A table, and the columns configured on it

A repository: models, tools, plays and agents

How you change it

In the UI, with an API and CLI alongside it

A pull request, planned as a diff, then deployed

How you undo it

In-app workflow versions

Roll back to any release

What starts the work

Someone presses run

The business changes

When it breaks

Open the row and look

Retries, approval gates, queryable traces

In Clay

Becomes in Cargo

Clay Table

Cargo Model or Segment

Clay Function

Cargo Tool or Play

Claygent

Cargo Agent

Workspace and business context

Cargo Context and knowledge resources

Provider connections

Cargo connectors, or your existing provider keys

Scheduled workflow

Cargo Play trigger

Table output and CRM push

Cargo CRM sync, with rules and approvals