Agent payments with limits that hold.
Give an agent permission to buy what it needs—not access to your wallet. ACKRATE binds every payment to a wallet-approved budget, merchant, and expiry, then enforces those terms on Stellar Mainnet before Circle USDC moves.
Complete a payment to place its Stellar Explorer receipt here automatically.
The fourth request exceeded the $0.03 mandate and was rejected before broadcast.
One request, independently verifiable
From HTTP 402 to paid delivery
- 01
Set the mandate
Approve the merchant, budget, and expiry in Freighter. Your signing key stays in your wallet.
- 02
The agent requests a resource
The consumer calls the protected Express endpoint and receives a standard HTTP 402 challenge.
- 03
The contract enforces the payment
MandateRegistry checks scope and remaining authority before settling $0.01 in Circle USDC.
- 04
The API returns the result
The fulfillment service verifies settlement, returns HTTP 200, and records the transaction as evidence.
The agent never gets your wallet.
Freighter handles every user signature. The SDK prepares the request; MandateRegistry decides whether the payment is authorized. Application code cannot raise the ceiling, change the merchant, or extend the deadline.
Control surface
Designed for accountable autonomy.
Funds remain under the user’s Freighter account.
The agent can spend only within the signed mandate.
Payment cannot be redirected to another recipient.
Each completed purchase links to its Mainnet transaction.
SDK
Typed packages prepare mandates, agent requests, and verified fulfillment.
CLI
The research-agent command runs the same Mainnet payment path from a terminal.
Reference agents
Consumer and fulfillment examples show both sides of the 402 exchange.
See the policy hold under real payment pressure.
Authorize three one-cent purchases. The fourth request exceeds the mandate and is rejected by the contract before settlement.