Governed x402 Payments
for AI Agents
x402 lets any agent pay any API over HTTP. SwarmCitadel decides whether it should, and proves it afterward.
The open payment standard for agents
x402 is an open standard, governed by the x402 Foundation under the Linux Foundation, that turns the unused HTTP 402 status code into a payment request. A server adds one line of middleware. An agent that calls the endpoint without payment receives a 402 response with the price, pays in stablecoins, and retries. No account, no API key, no invoice.
It is blockchain-agnostic and charges no protocol fee. x402.org reported 75M+ transactions and $24M+ volume in the 30 days to October 2026.
Effortless payments make invisible spend
When fifty agents each hit paid endpoints hundreds of times a day, the finance team has fifty wallets, no aggregate view, and no control until a balance reaches zero. A prompt injection in one agent can drain its wallet by paying a hostile endpoint.
x402 was designed to answer how an agent pays. It deliberately says nothing about whether it should.
Policy before signature
SwarmCitadel evaluates every x402 payment challenge before signing.
Agent receives challenge
Agent requests a resource and receives an x402 payment challenge.
Forward to treasury
Agent forwards the challenge to its SwarmCitadel treasury instead of paying directly.
Policy evaluation
Policy engine evaluates the challenge: per-call ceiling, daily budget, counterparty allowlist, spend category, and the Reasoning Quality Gate on why the agent wants this purchase. Most restrictive rule wins.
Sign and return
Approved payments are signed from a governed vault and returned to the agent to retry the request.
Escalate if denied
Denied payments escalate to a human with the agent's reasoning attached.
Audit trail
Every decision is written to the tamper-evident audit trail, tied to the on-chain payment.
Unified visibility
Finance sees one treasury, one ledger, and spend by agent, vendor and purpose in real time.
Capabilities
Spend policy
Per-call, daily and monthly ceilings per agent, per team, per vendor.
Counterparty control
Allowlists and denylists for x402 endpoints, with velocity caps.
Reasoning Quality Gate
Evaluates the agent's stated justification before funds move.
Audit trail
Challenge, policy result, reasoning score and outcome, linked to the transaction hash.
Who it is for
Fleets of research and data-enrichment agents buying API access
Procurement agents paying for services
Any regulated operator that needs to show an auditor why an autonomous system spent money