Agent product teams
Set transaction, daily and monthly limits, and send unusual spending to a human approval queue.
AGENT FINANCIAL OPERATING LAYER · STAGING
Control how AI agents spend money.
Set spending rules, approve high-risk actions, verify transactions, route payments and keep a complete financial record of every AI agent action.
WHO IT IS FOR
Built for teams that let AI agents act.
Platform operators
See what every agent requested, what your rules decided and what was actually paid — in one dashboard.
MCP and API developers
Connect agents with a few lines of code, around the x402 payment endpoints you already use.
HOW A PAYMENT WORKS
Every payment follows the same safe path.
An agent wants to pay
The agent declares what it wants to buy, for how much and why — before any money moves.
Trust is checked
The agent's payment history is reviewed, so a brand-new or risky agent doesn't get a free pass.
Your rules decide
Your spending limits decide whether the agent can pay on its own or must ask you to approve first.
The payment is verified
The amount, asset, network and recipient are checked while the payment is still only a plan.
The route is ready
A payment route to the service you enabled is prepared. The layer never signs or sends money itself.
Everything is recorded
The final payment is matched against the actual result and kept in an append-only financial record.
INTEGRATE WITH WHAT YOU ALREADY USE
Works with your agents, MCP tools and x402 payments.
API or MCP integration
Connect an agent with generated credentials and a copy-paste snippet. The financial layer sits beside your existing paid endpoints without changing them.
Financial API reference →x402 payments
Routes describe the x402 protocol, USDC asset, network and recipient. A route is a preparation step — it cannot send funds on its own.
See safe demo →Operator security
Admin actions use Basic Auth in the current staging MVP. Every record is append-only, so nothing can be quietly rewritten.
Security approach →WHAT TO KNOW BEFORE YOU CONNECT
This is a staging product surface. The layer does not hold funds, custody keys or guarantee a transaction outcome — it records and enforces the decisions around payments. Production onboarding still needs tenant isolation, customer-issued credentials, production rate limits and webhooks.