Agents in Finance · Manchester · 25 March 2026
No Human
in the Loop
Welcome to agent-to-agent commerce — where AI pays for what it needs, in real time, without asking permission.
Andy Gray
Co-Founder · BlockRocket
KnownOrigin co-founder (acq. eBay '22)
Director in Web3, eBay · Blockchain Manchester
Director in Web3, eBay · Blockchain Manchester
James Morgan
Co-Founder · BlockRocket
KnownOrigin co-founder (acq. eBay '22)
Blockchain since 2017 · Blockchain Manchester
Blockchain since 2017 · Blockchain Manchester
Truth Terminal
Lightbulb moment for
social agents with wallets
🧠
First social agent with a wallet
Widely seen as the first breakout social AI agent to operate with an associated crypto wallet, making autonomous agents with financial rails feel real.
📣
AI personality meets market speculation
Built an audience through posts on X, then became closely linked to crypto speculation and token-driven attention.
✨
A glimpse of what comes next
A lightbulb moment for builders and investors: AI agents could be more than chatbots; they can be online actors with identity, reach, and money.
The problem
Your agent needs agency.
Credit card says no.
💀 Legacy rails (built for humans)
⏳
ACH bank transfer takes 1–3 days to settle
💳
Credit cards charge $0.30 + 2.9% per transaction — micropayments are uneconomical
🔐
Every API needs a human to sign up, verify identity, attach a card
🔄
Chargebacks reversible for up to 120 days — a fraud nightmare
🌍
1.4 billion people unbanked — locked out of the system entirely
✅ x402 (built for agents)
⚡
Settlement in ~200ms on Base (Ethereum L2)
💰
Fees below $0.0001 — micropayments finally make economic sense
🤖
No account, no API key, no subscription — agent just pays and gets access
🔒
On-chain finality — no chargebacks, ever
🌐
Permissionless — works globally, with any wallet, any chain
The backstory
402: The status code the
internet forgot to use
💀 1995 — RFC 1945
📄
HTTP 402 Payment Required was defined in the original HTTP/1.0 spec
🚫
Marked "reserved for future use" — no implementation, no standard, no adoption
🌐
The web was built on the assumption that someone else would figure out payments later
⏳
30 years of workarounds: subscriptions, API keys, billing portals — all bolted on after the fact
✅ 2025 — x402
🤖
x402 finally implements what HTTP always promised — a native payment primitive baked into the protocol
⚡
Server returns
402 Payment Required with a machine-readable payment request
🔗
Agent pays on-chain and retries — all within a single HTTP exchange
🏛️
Not a hack. Not a workaround. The spec finally shipping — 30 years late.
The internet was always designed for payments. We just never built them in.
The protocol
One HTTP round-trip.
Agent pays. Data delivered.
🤖
1
Agent asks
Standard HTTP GET
to any API endpoint
to any API endpoint
→
💬
2
Server replies: 402
"Pay 0.02 USDC
to this address"
to this address"
→
✍️
3
Agent signs & retries
EIP-712 signed payment
attached to HTTP header
attached to HTTP header
→
✅
4
200 OK — data arrives
Payment verified on-chain
in ~200ms. Done.
in ~200ms. Done.
~200ms
Settlement finality on Base
<$0.0001
Transaction fee
$0
Protocol fee
0
API keys / subscriptions needed
Finance use cases — today
This is already happening
📊
Trading AI buys market data, per request
CoinGecko now gates on-chain data feeds via x402. A trading agent pays
$0.02 per request for live price data.
No Bloomberg contract. No minimum commitment. Costs exactly
$0 when the market is closed.
CoinGecko · live today
🛒
Agent browses, picks & pays — zero human touch
A shopping agent searches multiple retailers, compares price and reviews,
selects the best option and completes checkout via x402 —
no saved card, no form, no confirmation click.
First live pilots already running across e-commerce platforms.
E-commerce · live pilots
💳
Stripe backs x402 as the agentic payments rail
In February 2026, Stripe integrated x402 to handle USDC payments for AI agents on Base.
Co-founder John Collison predicted
"a torrent of agentic commerce"
in the months ahead. This isn't a startup experiment.
Stripe · Feb 2026
🤝
Google's agents pay each other
Google Cloud's Agent2Agent (A2A) protocol integrated x402 via its Agentic Payments
Protocol (AP2). Agents across platforms can now
monetise their own services and pay other agents
— automatically, without human-in-the-loop.
Google Cloud · A2A + x402
x402 use cases — finance and beyond
The agentic finance stack is being assembled
🛡️
Compliance orchestration
A compliance agent pays for sanctions screening, company registry pulls,
identity checks, and adverse media only when needed.
KYC / AML becomes modular, auditable, and usage-based.
Financial services · now/near-term
🏦
Real-time underwriting
Lending agents buy bureau data, bank transaction enrichment, fraud signals,
and income verification per applicant.
Fixed origination cost turns into variable cost per decision.
Lending · near-term
📈
Research and market intelligence
Analyst and trading agents pay per filing, transcript, dataset,
chart, or news query.
Data spend maps directly to decisions made, not seat licences bought.
Asset management · live pattern
☁️
Cloudflare turns APIs, tools and content into paid agent endpoints
With Workers and the Agents SDK, Cloudflare uses x402 to gate HTTP routes, MCP tools,
and even crawler access. An agent hits a protected endpoint, receives a 402,
pays automatically, and retries.
This is the clearest infrastructure example of machine-native paywalls in the wild.
Cloudflare · APIs, MCP, pay-per-crawl
🚚
Logistics and supply chain
Ops agents buy shipment status, customs data, route optimisation,
weather risk, and spot capacity quotes in real time.
Agents can assemble the best operational view on demand.
Logistics · strong fit
🛒
Commerce and software agents
Shopping, travel, and workflow agents pay for search, product feeds,
booking holds, compute, and premium APIs without accounts or cards.
The checkout flow becomes an API call.
Cross-industry · emerging now
The common pattern: agents discover, pay for, and consume digital services in real time — no API keys, no procurement delay, no human checkout.
The wider landscape
x402 isn't the only
game in town
🏦
Tempo — Machine Payment Protocol (MPP)
Fiat-first answer to x402. Agents transact over existing banking rails — no crypto required. Standards-based request/response agents speak natively.
Enterprise and compliance-first path into agentic payments.
Fiat rails · emerging
💳
Visa — Trusted Agent Protocol
Card-network approach. Visa issues tokenised credentials tied to a human account. The agent spends on the cardholder's behalf within
pre-set limits — works with every existing merchant terminal.
Card rails · announced
⚡
Stripe — Agent Toolkit
Not a new protocol — Stripe made their existing APIs agent-legible via an MCP server and intent-based flows.
Works today, no new crypto infrastructure, plugs into the stack you already have.
Classic rails · live
🖥️
Computer Use — the brute-force path
Anthropic & OpenAI Operator: agents that literally navigate checkout flows like a human would.
Zero merchant integration — works everywhere today. Slow and brittle, but immediate.
Any rails · live now
The real question: whose rails do agents run on? Crypto speed vs. fiat compliance vs. card trust vs. brute-force compatibility — the race is on.
Agents in Finance · Manchester · 25 March 2026
Let's break things
— then monetise the wreckage.
Protocol
x402.org
GitHub
coinbase/x402
Andy & James
blockrocket.tech
npm
@x402/express-middleware