---
path: /learn/agentic-commerce/
title: "Agentic commerce: how AI agents buy and pay"
description: Learn what agentic commerce is, how AI agents find, buy, and pay for products and services, and which payment controls businesses need before agents transact.
image: /images/opengraph/og-learn.png
publishDate: 2026-10-24
keywords: agentic commerce, what is agentic commerce, agentic payments, AI agent payments, agentic checkout, AI payments
label: Payments
timeToRead: 6
faq:
  - question: What is agentic commerce?
    answer: Agentic commerce is buying and selling in which an AI agent completes part or all of a purchase for a person or business. The agent works within goals and spending limits set by whoever deployed it, and the seller requests and verifies payment before delivering.
  - question: What is the difference between agentic commerce and agentic payments?
    answer: "Agentic commerce covers the whole purchase, from discovery to delivery. Agentic payments are the payment step: how an agent is authorized to pay, how the seller requests and verifies payment, and how both sides record the transaction."
  - question: How do AI agents pay for products and services?
    answer: Agents pay with credentials their owner has authorized, such as a card set up for agent use or a stablecoin account with limited permissions. For APIs and digital services, protocols such as the Machine Payments Protocol (MPP) let a service request payment over HTTP and verify it before returning the resource.
  - question: Can businesses limit what an AI agent spends?
    answer: Yes. Give each agent its own credential with a spending limit, an expiry, and, where supported, a list of allowed sellers. On Tempo, access keys enforce a configured spending limit and expiry for each agent, and you can revoke one key without affecting other agents.
  - question: Why are stablecoins used for agentic payments?
    answer: Agents often make small, frequent purchases at any hour. Stablecoin transfers on Tempo have sub-cent network fees and settle near-instantly onchain, 24/7, which suits per-request pricing. Funding, conversion, and payout steps outside the blockchain keep their own fees and timing.
heroTitle: "Agentic commerce: how AI agents buy and pay"
seoTitle: What is agentic commerce? How AI agents buy and pay
socialTitle: Agentic commerce explained
locale: en
canonical: https://tempo.xyz/learn/agentic-commerce/
---

# Agentic commerce: how AI agents buy and pay

_Agentic commerce is commerce in which an AI agent acts for a person or business: it finds a product or service, decides within the limits it was given, and completes the payment. For sellers, the question is how to let agents pay while keeping control of pricing, access, and records. [Explore agentic payments on Tempo](/solutions/agentic-payments/)._

Most online checkout flows assume a person is present. They read a product page, enter card details, and pass an authentication step. An agent changes those assumptions. It can compare options and buy on a schedule, but it is not built to fill in a card form or answer a one-time code.

This guide explains how agentic commerce works, where payments fit, and which controls buyers and sellers need.

## What is agentic commerce?

Agentic commerce describes purchases that software agents start and complete on someone's behalf. The person or business that deploys the agent sets the goal and the limits. The agent carries out the steps.

Two patterns are emerging:

- **Agents buying for people.** A shopping or travel assistant compares options, then completes checkout with a payment method the user has authorized.
- **Agents buying services for software.** A coding or research agent pays for an API call, a dataset, a compute job, or a tool it needs to finish a task. These purchases are often small and frequent.

**Agentic payments** are the payment layer of agentic commerce. They cover how the agent is authorized to pay, how the seller requests and verifies payment, and how both sides record the transaction.

## How does an agentic purchase work?

Consider an illustrative agent that needs data from a paid API:

1. **Discovery.** The agent finds a service that can complete its task and reads the price.
2. **Payment request.** The service states what the request costs. With the [Machine Payments Protocol (MPP)](https://mpp.dev/), a service can answer with [HTTP 402 Payment Required](/learn/402-payment-required/) and its payment terms.
3. **Authorization.** The agent checks the request against its spending rules and pays from an account it is permitted to use.
4. **Verification and delivery.** The service verifies payment, then returns the data with a receipt.
5. **Records.** Both sides store the payment reference so the purchase can be matched to the task, customer, or invoice.

Consumer purchases follow the same steps. The payment can run through card checkout with credentials issued for agent use, or through a stablecoin payment.

## Why do agents need different payment rails?

**Smaller prices.** Agents can buy one request at a time. Fixed per-transaction card fees make very small charges uneconomical for many sellers, so per-request pricing needs a low-cost way to pay. See [microtransactions](/learn/microtransactions/).

**Delegated authority.** Authentication built for people, such as one-time codes, does not fit software. Agents need credentials with limits set in advance.

**Machine-readable terms.** The price, accepted asset, and recipient need to be in a format software can read and verify.

**Always-on activity.** Agents run outside business hours. Onchain stablecoin transfers can settle 24/7, while bank-based steps follow their own schedules.

## Agentic commerce vs. traditional ecommerce

||Traditional checkout|Agentic commerce|
|-|-|-|
|Who completes checkout|A person|An agent, within delegated limits|
|Typical price unit|Order or subscription|Order, subscription, or single request|
|Authentication|Passwords, card checks, one-time codes|Pre-authorized credentials with limits|
|How payment is requested|A checkout page|A machine-readable request, such as HTTP 402|
|When value moves|Often batched on bank schedules|Onchain stablecoin legs can settle 24/7|

## What controls do buyers and sellers need?

**For businesses that deploy agents:**

- Give each agent its own credential, so you can revoke one without affecting the rest.
- Set a spending limit and an expiry for every credential.
- Restrict which sellers or services an agent can pay where your tools support it.
- Log each purchase with the task or customer that triggered it.

**For businesses that sell to agents:**

- Decide which products agents can buy and at what price.
- Verify payment before delivering the resource, and return a receipt.
- Apply rate limits and abuse controls, as you would for any API.
- State in your terms how errors and refunds are handled. A stablecoin transfer does not come with card-network chargeback rules.

## Where Tempo fits

Tempo is the blockchain built for payments, incubated by Stripe and Paradigm. Tempo and Stripe co-authored MPP, an open protocol that lets services request and verify payment over HTTP.

On Tempo, [access keys](/developers/docs/accounts/access-keys) let you set a spending limit and expiry for each agent. [Pay-as-you-go sessions](/developers/docs/guide/machine-payments/pay-as-you-go) let small charges accumulate without a separate onchain payment for every request, and [fee sponsorship](/developers/docs/accounts/fees/fee-sponsorship) lets a platform cover network fees for its agents. Stablecoin transfers settle near-instantly with sub-cent network fees.

Sellers still set their prices, access rules, and refund terms. To build agent payments into your product, see [agentic payments on Tempo](/solutions/agentic-payments/) or read [AI payment processing with MPP](/learn/ai-payment-processing/).

## FAQ

### What is agentic commerce?

Agentic commerce is buying and selling in which an AI agent completes part or all of a purchase for a person or business. The agent works within goals and spending limits set by whoever deployed it, and the seller requests and verifies payment before delivering.

### What is the difference between agentic commerce and agentic payments?

Agentic commerce covers the whole purchase, from discovery to delivery. Agentic payments are the payment step: how an agent is authorized to pay, how the seller requests and verifies payment, and how both sides record the transaction.

### How do AI agents pay for products and services?

Agents pay with credentials their owner has authorized, such as a card set up for agent use or a stablecoin account with limited permissions. For APIs and digital services, protocols such as the Machine Payments Protocol (MPP) let a service request payment over HTTP and verify it before returning the resource.

### Can businesses limit what an AI agent spends?

Yes. Give each agent its own credential with a spending limit, an expiry, and, where supported, a list of allowed sellers. On Tempo, access keys enforce a configured spending limit and expiry for each agent, and you can revoke one key without affecting other agents.

### Why are stablecoins used for agentic payments?

Agents often make small, frequent purchases at any hour. Stablecoin transfers on Tempo have sub-cent network fees and settle near-instantly onchain, 24/7, which suits per-request pricing. Funding, conversion, and payout steps outside the blockchain keep their own fees and timing.

---

## Site links

- [Tempo home](/)
- [Privacy policy](/privacy-policy/)
- [LinkedIn](https://www.linkedin.com/company/tempo)
- [X](https://x.com/tempo)
- [YouTube](https://www.youtube.com/@tempo)

### Products

- [Earn](/earn/)
- [Routes](/routes/)
- [Zones](/zones/)

### Solutions

- [Agentic payments](/solutions/agentic-payments/)
- [Cross-border payments](/solutions/cross-border-payments/)
- [Institutional settlement](/solutions/institutional-settlement/)
- [Stablecoin accounts](/solutions/stablecoin-accounts/)
- [Tokenized deposits](/solutions/tokenized-deposits/)

### Developers

- [Documentation](/developers)
- [Tempo Explorer](https://explore.tempo.xyz/)
- [Tempo API](/developers/docs/api/)
- [Performance](/developers/performance)
- [Status](https://status.tempo.xyz/)
- [GitHub](https://github.com/tempoxyz)

### Resources

- [Blog](/blog/)
- [Customers](/customer-stories/)
- [Learn](/learn/)
- [OUSD](/ousd/)
- [Partners](/partners/)
- [Reports](/reports/)
- [Stablecoin Advisory](/stablecoin-advisory/)

### Company

- [About](/about/)
- [Careers](/careers/)
- [Brand kit](/brand/)
- [FAQ](/faq/)
