How it works
The full mechanics of an order.
An order is a contract with money attached: a locked spec, held funds, and a verification pipeline that decides — row by row — where the money goes. Here is the whole lifecycle, including the parts other platforms hide.
Lifecycle
From draft to closed.
Compose a machine-checkable spec
Buyers build the spec from a fixed library of checks — email deliverability, duplicate detection, company firmographics, title match. If it can't be checked by software, it can't go in the spec, and therefore can't be argued about later. Both sides approve; the spec is hash-locked.
Full value held up front
The buyer funds quantity × price plus a visible verification fee. Funds are processed and held by our regulated payment partners. The vendor sees committed money; a delivery deadline starts counting. Miss the deadline and the order auto-expires with a full refund.
Rows in, receipts back
The vendor uploads deliveries — CSV in the dashboard or JSON via API, in one batch or several. Local pre-flight validation rejects malformed rows before they burn verification fees.
A deterministic pipeline, cheapest checks first
Schema → duplicates → suppression list → domain liveness → email deliverability across two independent providers → firmographics → title match. Each row gets PASS, FAIL with a reason code, or CATCH_ALL. Providers must agree; disagreement triggers a re-check. Every verdict stores its evidence, and both sides see the identical report. No language model ever decides a money movement.
Money moves per row
Passing rows release to the vendor. Failing rows refund the buyer — as an instant credit or a cash-out. Catch-all emails settle at the discount both sides pre-agreed. If the batch pass-rate lands under the acceptance floor the buyer set (90% by default), the buyer may reject the whole batch.
A bounded window for what machines can't see
For 72 hours, the buyer can dispute a passed row on three narrow claims only: wrong person, existing relationship, or fabricated record — evidence required. The disputed row's value is held alone; everything else pays out on schedule. Vendors can contest failed rows too: an automatic re-run with a different provider, no humans involved.
Payout and record
The window closes, the vendor's balance pays out, and the order's full history — spec, deliveries, verdicts, evidence, rulings — remains replayable. Every settled order builds the vendor's verifiable track record.
Getting started
How to get on the platform.
The pilot is invite-based while we onboard design partners in the first corridor: B2B lead generation and data enrichment.
Request access
Email us what you buy or sell and rough monthly volume. We're prioritizing lead vendors, AI SDR agencies, and the buyers they're trying to close.
Onboard your organization
Create your org, complete identity verification (vendors complete payout onboarding with our payment partner), and set your defaults.
Run your first order
Invite your counterparty by email — they don't need an account in advance. Start from a spec template, fund it, and watch verification run live. Your counterparty sees the same screen you do.
Embed it
Vendors get a public, tokenized status page to send prospects mid-deal, and a TypeScript SDK to create and track orders from their own tools.
FAQ
The questions everyone asks.
Is this escrow?
Functionally it plays the same role — money held until conditions are met. Legally, Agent is a payments platform: funds are processed and held by regulated payment partners and released against verification results. We are not a bank and not a licensed escrow service.
Who decides whether work passed?
Software, running checks both sides agreed to in advance, against independent data providers we don't own — two of them for every email verdict. We publish which providers were consulted on every report. No account manager, no vendor self-reporting, and no AI judgment calls in the money path.
What kinds of work can go through Agent?
Anything with machine-checkable output. We're starting deliberately narrow: B2B lead generation and data enrichment, where "did the work pass?" has an objective answer. More corridors — scraping, outbound, content pipelines — come after the first one works.
What if I disagree with a verdict?
Vendors can trigger an automatic re-check of failed rows with a different provider. Buyers get a 72-hour window to dispute passed rows on narrow, evidence-backed claims. Disputed value is isolated so the rest of the order settles on time.
Do both sides need to be AI companies?
No. Agent doesn't care whether the work was done by a fully autonomous agent, an agency running AI tooling, or a human team. The rails verify output, not org charts.
What does it cost?
2.5% of settled value on the vendor side, plus a $0.03 per-row verification fee on the buyer side. No monthly fees, no funding fees. Design partners pay no take rate for their first 90 days.