INSTANT SETTLEMENT
Let agents clear API access, compute, and data requests at the moment work happens.
agents can pay
as they work
x402 lets autonomous systems meet paid resources at the request layer. This agentic environment keeps the budget, policy, settlement, and receipt trail in one loop.
Request preview
PRIVATE ALPHA FOR AGENT BUILDERS
objectiveship paid retrieval flow
x402 required
Fetch priced market data from provider
approved
Run verification in isolated worker
queued
Attach receipts to final output
payment trace
GET /resource -> 402policy: under_limitwallet: scoped_sessionsettle: 0.008 USDCreceipt: verifiedreceipt bundle8 paid calls3 providers
SPEND DELEGATION
Assign budgets to specialist agents without handing them your whole treasury.
LIVE OVERSIGHT
Watch every x402 payment attempt, approval, retry, and receipt from one control surface.
POLICY REVIEWS
Test agent flows against limits before money moves, then preserve an audit trail.
a complete loop
for paid agents
DEFINE THE INTENT
Prompt once. Bound the wallet.
Describe the outcome, the payment rails allowed, and the maximum spend per task.
The agent receives a narrow x402 budget and a clear approval policy before it starts.
intent
objective: paid retrievalmax_spend: $42scope: research onlyboundedwallet session
what's coming
The project is moving toward a practical stack for agents that need to pay for tools without turning every integration into a billing project.
Hosted x402 policy simulatorProvider discovery for paid APIsWallet-scoped agent sandboxesReceipt export for finance teams
using x402 with agent teams
4agent loops run with isolated spend windows
12mslocal policy check before an x402 request leaves
100%receipts tied back to the task that created them
0shared secrets between delegated workers
faq
What is this project?
An agent control layer for x402-native work: budgets, payment policies, execution traces, and receipts for autonomous tasks.
Does it hold private keys?
The landing concept assumes delegated spend controls. Production custody can be wired to your own wallet, vault, or policy engine.
Why x402 for agents?
HTTP-native payments let agents acquire paid resources at request time instead of waiting for account setup or manual invoicing.
Can teams approve spend?
Yes. The intended workflow separates default limits, live approvals, and post-run review so finance and engineering can both see what happened.
Is this only for APIs?
No. The same pattern works for compute, data, model access, credentials, environments, and any service that can price a request.
What should connect first?
Start with low-risk paid resources: search, enrichment, test infrastructure, or internal tools that already have clear per-request value.