One Budget, Multiple Paid Tools: Inside Mastercard Agent Pay for Machines

The Mastercard Agent Pay for Machines pilot lets an AI agent buy digital services within spending limits approved for its work. For a job that needs research from one provider and images from another, you approve the plan and budget, then let the agent make the permitted purchases as the work unfolds.

You asked for a campaign. Somewhere between the brief and the finished assets, the agent needs another tool, that tool needs an account, and somebody has to sort out the payment. Before long, you’re managing the agent’s errands.

Mastercard's October 20 demonstration brings that everyday friction into focus: one agent, a sample campaign and paid services from two independent merchants. You can hand over more of the job when its spending stays connected to the plan you approved.

Research first, then eight campaign images

In Mastercard's Cloudflare Connect pilot demonstration, marketing agency Hype gives an agent a sample protein-bar campaign and a defined budget. The agent discovers registered providers and proposes social media research from AIsa followed by campaign images through Cloudflare AI Gateway.

Hype approves the funding for that plan. The agent buys the research and eight images, making nine payments across the two merchants under the same approved budget.

Watch the campaign-payment demonstration:

Research feeds the creative work, the agent pays for the next service in the plan, and you get to review the campaign. Fewer errands, more of the job you actually wanted to hand over.

Approve the job before the paid calls begin

Mastercard's product walkthrough starts with a business assigning work. The agent identifies qualified providers and recommends a plan and budget. The business then approves spending limits, funding preferences and execution rules through a verifiable authorization.

Give the agent a brief it can act on. If your agent needs to research an audience and produce a set of campaign images, name those outputs and the total you approve. Decide how it should handle a change in the work before that change arrives halfway through the job.

For a first pilot, give the approval these practical boundaries:

• Work: the research and creative outputs you want delivered.
• Spending: the total allowance for the job, including paid calls across providers.
• Providers: the services your application permits the agent to buy from.
• Changes: the point at which a different deliverable or additional spend needs a new approval.

Translate that approval brief into the controls your pilot supports. For a deeper look at purchase constraints, continue to the agent payment mandate guide.

A voucher lets the work continue before later settlement

When a paid service requests payment, the agent supplies a digitally signed payment voucher within its approved limit. The provider verifies the voucher and delivers the service. Mastercard describes those interactions as off-chain, with providers able to combine vouchers and redeem them later.

Account for accepted vouchers as the next tool call arrives. They can represent payment obligations that will settle later, so your task record needs to carry those obligations forward.

The underlying x402 payment exchange gives services a way to request payment over HTTP. Its documented batch-settlement scheme also separates per-request vouchers from later redemption. Mastercard’s service follows its own integration and participation requirements.

For your pilot, keep the allowance, existing payment obligations and returned work visible together. A successful research purchase should leave the image-generation step with an accurate account of what remains.

Review the whole job when the agent finishes

At the end of a campaign run, you want to open the research and images and know what they cost. Ask for a task record that connects each provider's work to its payment evidence and the approval that covered it.

That record makes ordinary follow-up easier. A designer can find the purchased images, a finance colleague can trace the charges, and you can decide whether the next campaign deserves the same budget. The next person should be able to pick up the work without reconstructing the agent’s afternoon.

The payment receipts and delivery guide explains how to connect approval, payment status and the result received. Connect those records under the job your team approved, so someone can follow the whole run.

Give the service behind the job a continuing name

Your campaign agent may change models or replace a research tool as its work improves. A Headless Domain gives customers a recognizable name to return to, with public records leading to the service you operate.

Compatible agents use HeadlessDomains.com and SkyInclude's API and command-line infrastructure to inspect those records and discover linked manifests and endpoints. The payment network manages its credentials and transaction controls; your application establishes any verified connection between those credentials and the public agent name.

For developers exploring Mastercard's system, the early-access program offers a route into the pilot. Agent Pay for Machines is still in pilot and is not commercially available.

Choose one job that crosses more than one paid tool. Give it a clear budget and a result someone can review. Then give the agent doing that work a name people can keep using as the service grows.

Give your agent the HeadlessDomains.com setup instructions and choose a name for its work.

Connect your name to the service with What to Do After Registering a Headless Domain: 7 Next Steps.