When I look at how AI agents are developing, I keep coming back to a practical question: if an agent needs to buy something to complete a task, how does it pay?

We already use AI to find information, compare products, and help us make decisions. Agentic commerce takes this further by allowing an agent to participate in the transaction itself, with permission from its user.

This is where I find the connection with crypto interesting. Stablecoins could let an agent pay for a service or access information when it needs it. Stripe is already building integrations that connect these payments to the tools businesses use to manage their revenue.

What would an agent actually pay for?

Imagine asking an AI assistant to prepare a market research report. During its research, it finds a useful paid dataset and an analytics service that could improve the report.

Accessing them might normally require you to create accounts, choose subscriptions, and enter payment details. That can feel excessive when you only need one piece of information.

With machine payments, the agent could request the resource, receive its price, and pay within a budget you have authorized. It could then use the result to continue its work.

I can see the value in that. You give the assistant a task and a spending limit, while the service provider gets paid for what the assistant uses.

Why stablecoins have a role to play

Stablecoins provide a way to make these payments onchain while keeping prices tied to a familiar unit of account.

USDC, for example, is designed to track the US dollar. A service can price its output in USDC, and the user can set a budget that is straightforward to understand. The peg is still a mechanism rather than an absolute guarantee, but the intended stability is useful for pricing services.

Stripe currently documents a minimum of 0.01 USDC for stablecoin machine payments, compared with $0.50 for card payments through Shared Payment Tokens.

For a database lookup or a small API request, that difference could matter. It gives developers more flexibility to charge for individual uses.

Of course, a low payment minimum does not guarantee a profitable service. The provider still has to account for payment fees, computing costs, and the cost of producing the information.

What Stripe is implementing

On March 18, 2026, Stripe and Tempo introduced the Machine Payments Protocol, or MPP. It allows agents to pay for APIs and services programmatically.

Stripe also supports x402, a protocol that uses the HTTP response 402 — Payment Required to tell a client that payment is needed to access a resource.

In Stripe’s documented x402 flow, an agent requests a resource and receives the payment requirements. It submits a signed payment authorization, a facilitator verifies and settles the transaction onchain, and the service delivers the resource.

The transaction is then recorded in Stripe.

That connection is useful for businesses. Receiving a blockchain payment is only part of the job; the seller also needs to track the transaction and include it in its revenue reporting. Stripe brings the payment into an environment the business may already use.

Which networks and stablecoins are involved?

Stripe’s machine payments documentation currently lists these combinations:

Protocol Network Stablecoin

MPP Tempo USDC.e

MPP Solana USDC

x402 Base USDC

These are the combinations documented for Stripe’s integrations. They do not represent every network or asset supported by these protocols elsewhere.

Another detail caught my attention: Stripe says these machine payments settle in fiat into the merchant’s Stripe balance.

This means an agent can pay in stablecoins without requiring the seller to keep crypto on its balance sheet. For a business that wants to accept these payments but manage its revenue in traditional currency, that could make adoption easier.

Access is still subject to Stripe’s requirements. Its documentation asks businesses outside the United States to request access to stablecoin payments in more than 30 countries.

An opportunity for smaller digital services

What interests me most is what this could make possible for people building specialized tools.

A developer might create a service that produces a particular analysis, checks information, or provides access to a useful dataset. Another agent could purchase that service when it needs it.

For example, an assistant preparing a report could pay for a data query. An agent comparing suppliers could purchase a pricing analysis. A content workflow could pay for a specific processing task.

These are potential applications, but they show why payment per use matters. Someone who needs a service occasionally might be willing to pay for one result without committing to a monthly subscription.

For the person building the product, it creates another way to sell their work. The challenge remains the same: provide something reliable and useful enough that a customer wants to pay for it.

Crypto will be one of several payment options

Stripe is also developing agent payments using cards and bank accounts.

On April 29, 2026, it announced a Link wallet for agents. The user can authorize access, review a spending request, and approve it. The agent can then receive a single-use card or a Shared Payment Token to complete the purchase.

I expect different payment methods to coexist. An agent might use a card with one merchant and stablecoins with another, depending on what is supported and what the user has authorized.

The practical value of crypto will depend on where it makes the transaction easier, particularly for services that software can access and pay for directly.

What I’ll be watching

For me, the interesting question is whether these tools become useful enough for people to use regularly.

Can the agent stay within its budget? Does it understand what it is buying? Does the service deliver the expected result? Can the user see where the money went?

Those details will matter as much as the payment technology.

I also think it is worth keeping payment adoption separate from token prices. More stablecoin transactions do not automatically mean that related crypto assets will increase in value.

What I find promising is the possibility of crypto becoming part of a useful everyday process. A person delegates a task, an agent pays for an authorized resource, and a business receives payment for its work.

Stripe is helping put that infrastructure in place. I’m interested in seeing what people build with it—and which services customers find worth paying for.

Would you give an AI assistant a small budget to complete a task, or would you prefer to approve each purchase?

Sources

• Stripe — Machine payments: supported networks, payment minimums, settlement, and availability
• Stripe — How its x402 payment integration works
• Stripe — Implementing the Machine Payments Protocol
• Stripe — Introducing MPP, March 18, 2026
• Stripe — Giving agents the ability to pay with Link, April 29, 2026