What is agent payment identity.
Agent payment identity is the credential an AI agent uses to pay or receive payment. It composes a wallet address, a public profile page, independently earned verification badges, and a per-agent spend policy. The identity is tied to one specific agent, not to a person or a company-wide account. It is what counterparties reference when they pay an agent and what the agent itself references when it pays.
Wallets are not identities. Agents need identities.
A raw crypto wallet gives you an address and a balance. That works fine when the payer is a human who already knows who they are paying. It fails when the payer is an AI agent, or when the counterparty is an AI agent: there is no shared reputation system, no way to verify the agent is legitimate before sending money, no record of what the agent has done before. Payments to anonymous addresses might be appropriate for tipping; they are not appropriate for paying a $50 invoice to an agent that should produce real work.
Agent payment identity solves this by wrapping the wallet with everything a counterparty actually needs to make a paying decision: a public profile that explains what the agent does, badges proving the operator is who they claim to be, transaction history showing the agent has fulfilled past obligations, and a policy layer showing what the agent is permitted to do with the money it receives or sends. The wallet underneath stays the same; the identity layer is what makes payments to agents safe at scale.
The per-agent granularity matters too. A workspace operator might run ten agents, each with its own customer base and risk profile. Identity at the workspace level would conflate them; identity at the agent level lets each one earn (or lose) reputation independently. This is why agent payment identity is a primitive specifically distinct from "the operator's account on the platform".
Five layers stacked.
Agent payment identity is not a single artifact; it is the composition of five layers, each owned by a different system component. The wallet is on-chain, the page is server-rendered, the badges are signed claims, the policies are platform-enforced, and the API key is your handshake with the SaaS layer.
- Layer 01
On-chain credential
A wallet address that can sign transactions and receive payments. Usually an EVM address controlled by an EOA or a smart contract wallet (e.g. Coinbase Smart Wallet, Safe). The address is what payment counterparties send to.
- Layer 02
Public profile page
A web page rendering the agent's name, purpose, owner, supported currencies, and recent transactions. Indexable by search engines and AI engines. The page is what counterparties read before paying.
- Layer 03
Verification badges
Independently earned signals (email verified, GitHub verified, domain verified) that connect the agent's wallet to a real-world identity. The stronger the badges, the more counterparties will trust large payments to that agent.
- Layer 04
Per-agent spend policy
Rules governing what the agent can spend (a per-period allowance and a per-transaction cap, set in the dashboard). Enforced at the payment infrastructure layer, not in the agent's code. Defines what the identity is permitted to do.
- Layer 05
API key + billing relationship
The SaaS-side credential the agent uses to authenticate to the payment platform's API, and the billing relationship between the agent's owner and the platform (per-agent subscription on Pro or Business).
What the identity does in practice.
Three concrete scenarios where the identity is doing work behind the scenes.
Agent receiving payment via the public page
A research agent's identity exists at wallet.blockchain0x.com/a/research-bot. Counterparties find the agent through search, X mentions, or a GitHub README. They click Pay, the page displays the wallet address + QR + verification badges, they send USDC. The agent's identity is the surface that converted browsing into payment.
Agent paying another agent programmatically
An orchestrating agent needs to delegate work to a specialist agent. It looks up the specialist's payment identity (the wallet address), creates a payment request against it, and pays at the hosted checkout URL it gets back. The specialist's identity is what the orchestrator referenced, not a generic account.
Auditor reviewing an agent's history
A compliance auditor wants to verify what an agent has done over the last quarter. The agent's identity includes its full transaction log (on-chain history at the wallet address + off-chain payment-request records in the platform's audit log). The auditor traces every payment without needing access to the owner's broader business systems.
Where this fits.
Agent payment identity is the connecting tissue between commerce, controls, and protocol.