The financial OS for the AI agent economy
One integration. Every payment protocol. Full control.
Built on x402 · ACP · AP2
Built for the Visa and Mastercard agent programs
One integration with Saifuro connects you to every major agent payment standard. x402 is stewarded by a Linux Foundation project with 40 members, including Cloudflare and AWS.
Trust machines with money
AI agents already move real money. But there are eight competing payment protocols, no spending rules, and no audit trail. Finance teams are flying blind.
Saifuro is the missing layer: spending rules, escrow, compliance and reconciliation that work on every rail.
What Saifuro does
Treasury, policy, escrow, billing and audit for agent money, above every rail.
Agents and keys
Every agent runs under a mandate that says who it may pay, for what, and up to how much. The keys that move funds stay in your own wallet or custodian. Saifuro holds no keys and no money, in any configuration.
mandate mnd_7f…a3 · per_transaction $50 · your keysPolicy engine
Declarative limits, allowlists and approval thresholds, evaluated in the hot path of every payment. Each verdict lands in an append-only audit log.
daily $500 · per_tx $50 · 30 tx/h · hold >$200Protocol adapters
x402, ACP, AP2 and the card frameworks. Routing picks the best rail per transaction while your integration stays put.
x402 · acp · ap2 · visa · mastercardEscrow and disputes
Programmable contracts hold funds until delivery. Releases, refunds and disputes follow a state machine with conditions you define.
funded → delivered → releasedMetering and billing
Per-call usage events, streaming aggregation, your pricing applied. Settle instantly over x402 or invoice monthly.
48,112 requests · $96.22 billedDecision log and audit
Every decision lands in an append-only log: which agent asked, under which mandate, which rule decided, and the signed verdict returned. The whole window exports as NDJSON whenever finance or an auditor asks.
append-only · signed verdicts · ndjson exportHow it works
Connect the SDK
One integration gives your agents wallets, budgets and access to every supported payment protocol.
The SDK ships at onboarding.
Set the rules
Spending limits, vendor allowlists, approval thresholds. Saifuro enforces them on every transaction, whatever the rail.
Agents transact, you see everything
Payments route over the best rail for the job. Each event lands in one dashboard and reconciles into your ERP.
Agents move money. You set the rules.
Code first
One SDK, a policy file and a drop-in fetch. The 402 flow, rail selection and receipts happen under the hood.
Webhooks: decision.review_pending · mandate.revoked · escrow.released · escrow.disputed
In practice
Data purchases under policy
Your research agent buys datasets on its own, capped at $500 a day and limited to vendors you approved. Every purchase is checked against the policy before it settles.
Metered API revenue
Agents call your API around the clock. Saifuro meters each request, applies your pricing and settles to your account. Refunds and disputes are handled inside the same service.
Escrow for agent-to-agent deals
Escrow holds the funds until the work is delivered. If the deal falls through, the money returns to the buyer automatically.
One report for the CFO
Every agent and every rail in a single ledger. Spend breaks down by agent, vendor and protocol, reconciles into your ERP, and anomalies get flagged before month close.
Audit in one export
Who paid whom, under which policy, approved by which rule. Identity, decision and settlement for each transaction, in a single export.
Watch a payment clear
Policy check, escrow and settlement in a single flow.
Every verdict is written to an append-only audit log.
Frequently asked questions
Ten answers on protocols, controls, custody and getting started.
How do AI agents pay for APIs? +
Through machine payment protocols. Under x402, the API answers a request with HTTP 402 and a price. The agent pays, usually in USDC, and the call completes without a checkout page or a card form. Saifuro wraps every major protocol in one integration and adds spending policies, receipts and reconciliation.
What is x402? +
x402 is an open protocol for machine payments over HTTP. Coinbase launched it in May 2025, and it now sits with a Linux Foundation project whose 40 members include Cloudflare and AWS. The protocol uses the HTTP 402 status code to request and settle payment. Saifuro supports it natively.
Which payment protocols does Saifuro support? +
x402 (Coinbase), ACP (Stripe and OpenAI), AP2 (Google), MPP (Stripe and Tempo), plus the card-based agent frameworks from Visa and Mastercard. One SDK covers all of them and routes each transaction by cost and speed. We add new protocols on our side, so your integration stays put.
What spending controls can I set? +
Per-agent budgets, daily and monthly limits, vendor allowlists and blocklists, category and geo rules, plus approval thresholds. A transaction above its threshold waits for a human or a multi-signature sign-off. Policies hold across every rail, and you can cut an agent's spending off at any moment.
Is Saifuro custodial? +
No. Funds stay in your own accounts and wallets. Saifuro enforces policy at the transaction layer and never takes possession of your money. When a deal calls for escrow, it runs on programmable contracts with release conditions you define, and the audit trail records every step.
How do refunds between agents work? +
Through escrow. Funds sit in escrow until the agreed condition is met, whether that is delivery, an SLA or a deadline. A failed deal returns the money to the buyer automatically. A contested one goes through a programmable dispute flow with the transaction trail attached. Most rails treat a refund as just another transfer. Saifuro treats it as a first-class operation.
How is Saifuro different from Stripe or Coinbase? +
Stripe and Coinbase each run their own rail, ACP and x402, and their tooling serves that rail first. Saifuro doesn't operate one. It sits above all of them as a neutral layer, so your policies, escrow, billing and reporting work the same whichever protocol wins.
What is agentic commerce? +
Commerce where AI agents transact on behalf of a person or a company: buying data, paying for API calls, ordering goods. It's already in production. Agent checkout runs at Walmart, Nike and other large retailers, and Bain projects 300 to 500 billion dollars of US agentic commerce by 2030. Saifuro is the financial infrastructure underneath.
How do I get started? +
Book a demo. Integration is one SDK and typically takes a day: connect, define policies, and your agents can pay over any supported protocol. On the call we map your use case, whether that is API monetization, agent treasury or both, and scope a pilot.
Is Saifuro open source? +
No. Saifuro is a closed product built on open standards. The payment protocols it speaks, x402, ACP and AP2, are open and publicly documented. The treasury, policy, escrow and ledger layers on top are proprietary. The SDK ships at onboarding.
Agents move money.
You set the rules.
Tell us about your use case and we will set up a call: a walkthrough on your scenario, then scoping for a pilot.
Prefer email? contact@saifuro.com