A budget for each agent
Set per-request, daily, and total limits. Keep a research agent’s spending separate from a production workflow.
Machine payments
Give your agents
a wallet.
Let your agents pay for the APIs they need with x402 and MPP. Fund a wallet, set an allowance, and turn paid endpoints into tools they can use.
npx openspender connectConnect your AI tools from the terminal.
Available balance
$250.00USDC
Self-custodial · Your keys
Research agent
ActiveSpending allowance
Daily spending$1.24 / $5.00
Per request $0.05Allowed hosts 3 services
Recent payments
Web searchTavily · x402$0.010 Paid
Web researchExa · MPP$0.007 PaidGive your agent access to paid tools
- TavilyWeb search
- ExaResearch
OpenAIModels
ClaudeModels
falImages
PinataStorage
How it works
From a request to a result.
OpenSpender handles the payment step between your agent and a supported API.
- 01
Fund your wallet.
Add money once. Give each agent an allowance with the limits you choose.
- 02
Connect your agent.
Use MCP or the API. Your agent gets scoped spending access to your wallet.
- 03
Call. Pay. Keep going.
OpenSpender checks the price, pays within your allowance, and returns the result.
Agent workspace
Your research agent
Search the web
01 / Request
POST
/tavily/search{ "query": "machine payments for agents" }1
Read the payment requirement
Reading price…2
Check the agent’s allowance
Waiting for price3
Pay and return the result
Waiting for allowance check02 / Payment receipt
Tavily / Web search
Quoted price
$0.010USD
- Allowance
- Research agent
- Per-request limit
- $0.05
- Payment route
- x402 · Base
Daily spending limit
$5.00per day
Per request$0.05
Total allowance$50.00
Allowed hosts
x402.tavily.comapi.exa.aiapi.pinata.cloudYour agent can spend within these limits.
You can revoke its allowance at any time.
An allowance for every agent
Let it do the work.
You set the limits.
Give agents room to finish the task, with a budget that stays in your hands.
Control where it spends
Use an allowed-host list to choose the services an allowance can pay. Revoke access from your wallet.
Check before paying
The provider’s payment request is checked against your allowance before a payment is signed.
Built for paid API calls
One place for agent spending.
Your wallet$250.00 USDC
Self-custodial
Your wallet stays yours.
Keep funds in a self-custodial wallet. Give agents scoped spending access without sharing your wallet’s private key.
Your agent OpenSpender
MCPAPI
npx openspender connectConnect the tools you use.
Connect through MCP, or send API requests with an allowance token. Start from your existing agent workflow.
Payment receipt
Web search$0.010
Settlement Recorded
See what every call cost.
Review the service, amount paid, and settlement transaction in one activity feed.
Payment protocols
Open standards. A familiar workflow.
The endpoint asks for payment. OpenSpender handles the payment exchange within your allowance.
x402
HTTP-native payments
Call an endpoint, receive a payment requirement, then pay and retry the request. OpenSpender’s x402 routes settle on Base.
x402 routing is liveExplore x402MPP
Machine Payments Protocol
MPP lets services describe how a request can be paid. OpenSpender’s catalog includes MPP routes; payment availability depends on the route and signing support.
Check current route availabilityExplore MPPCheck the router docs for supported providers, payment methods, and current MPP availability. Read the docs
Start building
Your next API call.
Paid by your agent.
Open your wallet, or copy the setup prompt into your coding agent.
Read the quickstartAgent setup
npx openspender connectConnected tool
Your coding agent
Daily limit$5.00
Per request$0.05
First search. Paid.
Tavily · x402
Within your allowance
200 OK