The payment firewall for AI agents
The security layer between an agent deciding to spend and the money moving.
Task ↔ purchase
Does the purpose match the submitted task context?
Amount + budget
Is it within transaction, daily, and velocity limits?
Counterparty
Is the vendor or address blocked or otherwise risky?
Wallet controls check limits and addresses. They do not check whether the purchase matches the job.
A valid wallet action can still be the wrong action for the job. Same amount, same category, same counterparty — and still the wrong purchase. Safe4 inserts an enforceable checkpoint.
Safe4's own decision is sold over x402. An agent calls, receives a price list, pays in USDC, and gets an authorization back.

01 x402
Payment protocol
Safe4 is callable as an MCP tool. Connecting and reading the price are free; the authorization call settles per use.

02 Model Context Protocol
Agent tool
On ALLOW, Circle Agent Wallet executes. On DENY the executor is never invoked and no funds move.
03 Circle Agent Wallet
Execution
USDC settles on Base through open x402 facilitators, then is verified against the chain rather than trusted.

04 Base
Settlement network
USDC settles on Arc with receipt verification, so the decision and the movement of money stay tied together.

05 Arc
Settlement network
Payments settle from a Gateway balance, so a buyer funds once and spends across many calls.
06 Circle Gateway
Settlement rail
What is Safe4?
How does Safe4 work?
What does Safe4 evaluate?
How is Safe4 different from wallet controls?
What technologies does Safe4 use?
Is Safe4 a replacement for Circle Agent Wallet?
Get the SDK
Start integrating Safe4 into your agent. Check the quickstart guide for setup instructions.
Read the Docs
Full SDK reference, policy engine documentation, and integration patterns.
View on GitHub
Source code, examples, and contribution guidelines. Open issues and PRs welcome.
The rails for autonomous commerce are landing now. The control layer above them is still open.


