Payments for companies that run on agents.
Each agent gets an identity, a human owner, a funded account, approved counterparties, and spend limits the network enforces on every instruction.
Procurement payment · PO-4418 · inside its spend limit
Transaction monitoring
Fictional example · not a customer result
Agentic commerce is AI agents acting as economic actors: negotiating procurement, settling marketplaces, rebalancing treasury at 2am. A card is open-ended spend; an account caps it at the balance, with network-enforced spend limits inside. Infinite treats an agent like any network member. Agents pay. Compliance defends the record.
Agent accounts, opening now to a first group.
Bring your workflow to MCP, where agent-created transfers wait for human approval.
Give an agent a key, not your bank account.
The keyKYA establishes who the agent is. The key establishes what it may do.
- The keyThe agent’s credential. It can pay and nothing else.
- Spend limitsPer-transaction, per-day, and per-month bounds the network enforces in the same transaction that moves the money.
- CounterpartiesRecipients the network has already screened. Off-list destinations are refused before routing.
- Instant revokeRevoke the agent and every key dies instantly.
- Readable denialsDenials are machine-readable. The agent reads the limit, sees what’s used, and picks a smaller amount. No human in the loop.
- The recordRequest, screening state, route, settlement, and which agent sent it, assembled for an examiner.
Every demo shows the agent paying correctly. Infinite is built for the day it doesn’t.
The failure caseRun an agent long enough and it will attempt a payment it shouldn't.
A bug retries a payout. The spend limit refuses it in the same transaction, and the funded balance still caps it.
An injected instruction tries to redirect funds. The MCP-created transfer stays IN_REVIEW for a person to approve.
At 2am, an agent signed in over MCP creates a transfer, in early access. It starts in review, and nothing pays out until a named analyst approves it.
A limit that lives in the agent’s own code is a promise. A limit the network enforces in the same transaction that moves the money is arithmetic.
Decisions in milliseconds shouldn’t settle on Monday.
Machine speedOne API across ACH, wire, RTP, SWIFT, SEPA, Pix, and SPEI, plus stablecoins on Ethereum, Base, Polygon, Solana, and Tron. Transfer Routes picks the rail.
The same API. Readable by agents.
BuildThere is no separate agent product to integrate.
# An agent signed in over MCP calls create_transfer, # which posts the same transfer any caller creates. POST /v1/transfers { "onBehalfOf": "cus_7f3k2d", "amount": { "currency": "USD", "rawValue": "12500" }, "source": { "currency": "USD", "paymentRail": "BALANCE", "accountId": "vba_7f3k2d" }, "destination": { "currency": "USD", "paymentRail": "ACH", "accountId": "eba_9m2x81" }, "paymentReason": "PAYMENT_FOR_GOODS_AND_SERVICES", "confirm": true }
// 201 Created. A signed-in agent made it over MCP, so it // starts in review: nothing pays out until a named // analyst approves it. { "id": "tfr_2e7b90", "status": "IN_REVIEW", "sourceAmount": { "currency": "USD", "exponent": 2, "value": "12500" }, "destination": { "currency": "USD", "paymentRail": "ACH", "accountId": "eba_9m2x81" } }
Three ways to reach it.
Every capability an agent needs, under one discipline.
CapabilitiesLive today unless marked early access.
Accounts
Wallet accounts
Early accessA dedicated account per agent. The balance is the outer ceiling; spend limits are enforced inside it.
Money movement
Pay & request
Pay or collect by link, with the payer screened first.
Accept
An agent is paid into its own account, reconciled on arrival.
Transfer
Move funds on the rail chosen per payment: stablecoin, SWIFT, or US rails.
Credit & cards
Cards
Early accessCard issuing for businesses and their agents, under the same account-level controls.
Card issuingCredit
Early accessLines of credit for agents, drawn inside the limits and screening the account already enforces.
Lines of credit
Platform
Connect
Onboard customers through verification links, then move money for them.
Bill
Usage- and success-based billing, built into the funds flow.
Identity
A durable name and a human owner, bound to a KYB-verified business.
Observability
Every instruction in one exportable record.
Compliance
Agents assemble casework inside approved policy; judgment calls route to named analysts.
Agents on Infinite, answered
What is know your agent (KYA)?
Know your agent (KYA) extends a compliance program to AI agents that move money: each agent is bound to a KYB-verified business, funded with what it may spend, limited to vetted counterparties, screened on every instruction, and recorded.
Is KYA a regulatory requirement?
There is no named KYA rule, but sanctions screening, transaction monitoring, and auditability apply whoever initiates a payment, and “the model decided” is not an answer an examiner accepts.
Do AI agents need their own bank accounts?
Yes. Unlike a card’s open-ended spend, an account caps spend at its balance, vets counterparties first, and keeps the record. On Infinite, an agent’s account is held through chartered, FDIC-insured partner banks.
How does Infinite know which agent sent a payment?
By its account. Each agent gets a dedicated account, so every payment resolves to that agent, its business, and the accountable humans, in one reviewable record.
Can an AI agent open an Infinite account on its own?
No. A business clears KYB first, through a demo rather than a self-serve signup. After that, its agent can drive customer onboarding through MCP, and hosted verification handles the steps a person has to complete. Opening accounts for its agents is an API call.
What happens if an AI agent is compromised?
The blast radius is the agent, not the business. Revoke it and every key dies instantly. Until then it spends only what its spend limits allow, capped again by the funded balance, and only to vetted counterparties. Flagged payments stop for human review.
How do agents connect to Infinite?
Over MCP: the agent signs in with your Infinite account, and in early access it creates the transfer itself, which starts in review until a named analyst approves it. The REST API and the CLI drive the same accounts and transfers. Keys and tooling are shared during onboarding.
Which agent capabilities are live today, and which are in early access?
Live today: enforced spend limits, approved counterparties, instant revoke, per-agent attribution, sign-in and customer onboarding over MCP, Links, Transfer Routes, Embedded Compliance, and Compliance AI. An agent can be paid through a link today; an agent issuing its own links is coming. In early access: wallet accounts for agents, transfers a signed-in agent creates over MCP, card issuing, and lines of credit; request early access to join the first group.
Bring the agent. We'll bring the network.
Show us the workflow, and we'll map how its money moves.
Ask an AI about Agentic PaymentsChatGPTClaudePerplexityGemini