AI agents are becoming more capable, reliable and able to work with one another. Increasingly, they also need to pay for things. An agent might buy data from one provider, use an AI model from another and pay for computing power from a third. In other words, AI agents are becoming economic actors.
But how does an agent actually pay?
Paid digital services today typically require an account, API key, prepaid credits or billing relationship with each provider. That works when an agent uses one or two services. It becomes harder when the agent needs to choose different services as a task unfolds, paying only for what it uses along the way.
Then there’s trust. Who gave the agent permission to spend? How much can it spend? What can it spend that money on? And who is it paying?
Those questions need to be answered instantly, at machine speed. That's why we built Agent Pay for Machines. It builds on x402, an open protocol that lets digital services request payment online, and connects it with the trust, security and reach of the Mastercard network.
Today at Cloudflare Connect, Mastercard is showing how Agent Pay for Machines allows AI agents to securely purchase digital services on behalf of businesses while staying within approved budgets and permissions.
Following end-to-end pilots with Cloudflare, Ant International, AIsa, Base, BVNK, Coinbase and Hype, we’re also opening Agent Pay for Machines Early Access, giving developers access to the APIs, tools and documentation needed to begin building and testing agent-to-agent commerce experiences.
Payments aren't the hard part. Authority is. The challenge is making sure the right agent can complete the right transaction with the right permissions.