For agents that earn
Let AI Agents Get Paid - Payouts for Agents That Earn
Some agents earn. An agent that sells a service, runs a paid API, or settles with another agent can receive payouts into its wallet, with the same policy and audit.
In short
Letting AI agents get paid means routing the money an agent earns into a wallet it controls, under policy. Agentspay handles payouts as well as spending: an agent that sells a service, charges for an API, or settles agent-to-agent receives funds into its wallet, and every payout is recorded in the same audit trail as its spending.
The problem
Why this is hard without a control plane
-
Most agent-payment tools only handle spending, not earning.
-
Agent-to-agent settlement needs identity and an audit trail on both sides.
-
You want earnings and spending under one policy and one record.
The control surfaces
What you get with Agentspay
Each surface is enforced in the platform, not in fragile agent code.
AI agent wallet
Agent wallet
An AI agent wallet is a funded, budgeted account that belongs to a single agent. You top it up to a set amount, attach spend limits and rules, and the agent draws from it. Because the wallet is capped and policy-gated, the agent cannot exceed its budget or spend outside the rules you wrote.
Learn moreAudit trail
Audit trail
An audit trail for AI agent spending is an immutable, append-only record of every payment an agent made. Each row links the spend to the intent that triggered it, the agent that requested it, the human who owns the agent, the policy verdict, and the approver. It gives you cost attribution, reconciliation, and a record you can defend.
Learn moreSpend controls
Spend controls
AI agent spend controls are rules that limit what an agent can buy: per-transaction, daily, and total caps, merchant and category allowlists, and velocity limits. Agentspay evaluates them at the API boundary, so a hallucinating or compromised agent is declined before it can overspend, not flagged after.
Learn moreHuman approvals
Human approvals
Human in the loop agent payments means an agent's transaction pauses for human sign-off when it crosses a threshold you set. The agent waits, the request is sent to Slack, email, or a webhook, and nothing settles until a person approves or denies. The decision and approver are recorded in the audit trail.
Learn moreFurther reading: agentic commerce for merchants, ChatGPT Instant Checkout for merchants, and UCP Checkout on Google. Or see what it costs on the pricing page.
See policy decide
Watch a transaction run the gauntlet
Pick a scenario and watch policy auto-approve the routine spend or hold the big one for a human, then write the audit row.
Pick an agent
Payment intent
intent: ▌
Policy evaluation
Human approval required
This spend is over your approval threshold. Approve it to issue a scoped card, or deny it.
Scoped virtual card issued
Wallet budget
spent of
Audit trail
Keep exploring
More solutions
For agent builders
Agent builders
You are building the agent. We are the safe way for it to pay. Drop in a wallet, a policy, and a scoped virtual card without building a money-control stack yourself.
ExploreFor AI platforms
AI platforms
Give every agent on your platform a safe way to pay, without becoming a payments company. Embed wallets, policy, cards, and audit, and keep your own rail and issuer.
ExploreFor businesses
Businesses
Put agents to work on procurement, subscriptions, and ad spend without losing control of the budget. Caps, approvals, and audit your finance team will actually approve.
ExploreShip agents that spend safely
Create a wallet, write a policy, and issue a scoped virtual card in an afternoon. Sandbox-first and rail-neutral.
Never moves money without policy