AI spending and services
What you can do.
Choose which services your team can use and set a budget before anyone spends. API sellers can list their services, set prices, and keep receipts together.
- Team spending limits
- API listings and prices
- Usage and receipts
What’s been built
- Budgets and service choices for each accountReady
- API listings and prices for sellersReady
- Paddle payment servicesPaddle approved
Explore the features
A diagram explaining the product's features.
Technology & architectureCheck the limit. Approve the payment. Verify the result.Explore the architecture
How it works, in three steps
Connect each AI service call to its budget and payment terms. Preparation, wallet approval, delivery, and receipt verification follow one execution record.
Quotes bind price, recipient, and network. A changed budget or service configuration stops the existing approval path; USDC amounts use integer microunits.
The SIWE wallet path uses EIP-3009; the separate passkey path uses Permit2. Each signature and nonce is bound to one execution.
Verification checks the canonical USDC transfer, at least two L2 confirmations by default, and the result hash. Final Ethereum L1 settlement is a separate state.
Quotes bind price, recipient, and network. A changed budget or service configuration stops the existing approval path; USDC amounts use integer microunits.
Security & design principles
Signing stays with the user
Non-custodial authorizationApproval comes from the connected wallet or passkey. The server checks the approved terms without signing on the user's behalf.
Recover without duplicate execution
Idempotency · ReconciliationA request, signature, and settlement transaction belong to one execution. Connection failures after approval are resolved against the existing record.
Protected seller connections
Encrypted upstream credentialsUpstream URLs and API keys are stored in an encrypted record. Public service listings provide the AgentPay gateway URL.