---
title: "Blockchain for AI Agents: How Agentic Commerce Works on Sui"
description: "What AI agents need from a payment rail, and how Sui answers: Payment Intents, scoped authority, and 6M TPS in a live agent experiment."
author: "Sui Foundation"
datePublished: 2026-09-02
dateModified: 2026-09-03
category: "Infrastructure"
readTime: "8 min"
canonical: https://www.sui.io/blog/blockchain-for-ai-agents-agentic-commerce-sui
---

# Blockchain for AI Agents: How Agentic Commerce Works on Sui

## Main Takeaways

-   An AI agent that spends money needs three things today's payment rails do not provide: settlement that is atomic across multiple services, spending authority the protocol itself bounds, and cost low enough to run at machine volume.
-   Payment Intents let a single request, from an agent or an application, trigger multiple actions across multiple apps and settle them in one atomic transaction. Sui's programmable transaction blocks carry up to 1,024 operations that all succeed or all fail together.
-   On July 4, 2026, a public livestream experiment with AI agents peaked at 6,086,766 transactions per second, roughly 20 times the prior benchmark ceiling. The throughput came from programmable tunnels that settle to Sui mainnet, with gas sponsored and sign-in through zkLogin.

In 2024, automated traffic overtook human traffic on the web for the first time in a decade, reaching 51% of all requests according to Imperva's 2025 Bad Bot Report. Money is the next thing to make that shift. AI agents are starting to act as economic participants in their own right, booking, buying, settling, and routing payments on a user's behalf. The infrastructure they need does not look like the infrastructure people use. This guide explains what agentic commerce requires from a blockchain, and how Sui's design answers it.

## Why today's payment rails break for agents

An agent can make a decision in under a second. The payment systems it has to use cannot keep up, and the reason is structural.

Consider an agent given one ordinary financial task: move a user's idle cash into the best available stablecoin yield. To do that well it runs a sequence of related steps. It pulls current rates from a market-data provider, which charges per API call. It swaps the cash into the target stablecoin. It deposits the position into a lending venue. And it settles the data provider's invoice for the call it just made. On today's internet each of those is a separate login, a separate approval, and a separate payment, and the agent has to walk down the list one step at a time, waiting for each system to confirm before the next. Sequential execution at machine speed is slow and fragile. A failure halfway through leaves the position half-built and the money in limbo.

There is also a permissions problem. If you give an agent the ability to pay, you need hard limits on what it can spend, when, and to whom. Handing an agent an unrestricted payment method is not an option any serious builder would accept. The rails have to carry those limits natively.

Three requirements fall out of this. Payments for agents need to be atomic, so a multi-step workflow either completes fully or not at all. They need to be fast and cheap enough to run at machine volume. And they need scoped, programmable authority so an agent's spending power is bounded by rules the chain enforces.

## Payment Intents: many actions, one atomic transaction

Payment Intents are Sui's primitive for this problem. A Payment Intent lets a single request, whether it comes from an AI agent or an application, trigger multiple actions across multiple apps and settle them in one atomic transaction.

Let's return to the agent moving cash into yield. With Payment Intents, it can query the market-data provider, the swap venue, and the lending pool together, then settle the rate payment, the swap, and the deposit in one atomic transaction. The agent no longer works down a list. It finds the fastest route across the available services and executes the whole thing at once. If any part cannot complete, none of it commits, so there is no half-built position to unwind.

Bundling this many related actions into a single atomic transaction is something Web2 rails cannot do, and most blockchains handle it poorly. Sui's programmable transaction blocks let one transaction carry up to 1,024 operations that all succeed or all fail together, and the object model with parallel execution lets independent actions run without colliding.

**Reviewer note:** The original draft said this "has not been possible on other blockchains." Per the comment, the safer and more accurate framing is that Sui can bundle more related actions into a single atomic transaction than other chains. Please confirm the exact competitor comparison before publishing.

A Payment Intent settles on-chain, which leaves a verifiable record of what was paid, to whom, and under what authority. For agentic commerce that auditability is not a nice-to-have. When software is spending money autonomously, being able to reconcile exactly what happened is what makes the system safe to operate.

**Reviewer note:** The original draft claimed a verifiable receipt at "every step," which may conflate Payment Intents with Payment Kit. The exact receipt behavior should be confirmed with engineering before publishing.

## Scoped authority that composes across apps

Giving an agent permission to pay is only acceptable if the permission has edges. Sui lets builders grant agents scoped authority with clear limits on what they can spend, when they can spend it, and who they can pay.

These permissions are composable, which means the rules work across applications rather than being redefined inside each one. An agent authorized to spend up to a set amount at a set cadence carries that authorization with it as it moves between apps to complete a task. The chain enforces the boundary. A builder does not have to trust each individual application to respect a spending limit, because the limit lives at the protocol layer.

This is the difference between an agent that can theoretically transact and an agent a business would actually deploy. Bounded, auditable, composable authority is the precondition for letting software spend real money.

## The throughput agents actually need

Agentic workflows concentrate activity in a way human activity does not. A single agent, or a single account orchestrating many agents, can generate a burst of transactions that would overwhelm a chain built around per-account limits.

Sui put this to a public test. On July 4, 2026, anyone could join a livestream experiment in which AI agents played blackjack and Quantum Poker against each other, drew on a shared canvas, chatted, and paid one another. The network peaked at 6,086,766 transactions per second, roughly 20 times the prior benchmark ceiling set in controlled testing.

The throughput came from programmable tunnels: offchain payment and state channels that settle to Sui mainnet when they close. Every closed channel is mutually cosigned and independently verifiable onchain. Gas was sponsored throughout, so no participant needed to hold SUI, and everyone signed in with a Gmail address through zkLogin. For agent-to-agent activity running at machine speed and machine volume, that architecture is what keeps the base chain from becoming the bottleneck.

The headline chain numbers support the same conclusion. Sui finalizes typical transactions in about 390 milliseconds and keeps average transaction cost under $0.02. In benchmark testing it has reached a theoretical peak of around 297,000 commands per second (CPS), the figure that counts the individual operations bundled inside transactions; that is a ceiling measured in testing rather than observed mainnet throughput. Sui's consensus layer, Mysticeti, takes a fast path for simple non-dependent transactions like token transfers, which is part of why simple payments settle so quickly. For an agent making thousands of small payments, sub-second finality and sub-cent cost are what decide whether the model is economically viable at all.

## Gasless transfers, with confidential amounts in development

Two more properties matter specifically for machine-driven payments.

First, moving stablecoins on Sui is gasless. There is no gas and no pre-purchased token to hold, whether the transfer is a fraction of a cent or a large institutional sum. Sui supports gasless stablecoin transfers across multiple stablecoins at the protocol level, and it is live on mainnet. An agent making thousands of micropayments cannot be required to hold and manage a separate gas token for each one, and gasless transfers remove that friction.

Second, Sui is adding confidential transfers. They hide the amount from the public while the sender and the recipient stay visible. The feature is in beta on devnet. For commerce agents conduct on behalf of people, shielding the amount is useful, and the visible parties are what keep the system auditable.

## What a builder should take from this

If you are building agents that need to transact, the questions to ask a chain are concrete. Can a single workflow settle atomically across multiple services? Can you bound an agent's spending authority in a way the protocol enforces and that travels across apps? Will the throughput and cost hold up when one account drives thousands of payments? Can the agent move stablecoins without managing gas?

Sui answers yes to most of these today. Payment Intents provide the atomic multi-app settlement, scoped composable permissions provide the authority model, programmable tunnels provide the headroom, and gasless stablecoin transfers remove the operational friction. Parts of the agentic-commerce stack are still being built. The settlement primitives underneath it are running today, and Sui is working toward becoming the default rail for AI-initiated payments.

## FAQ

**What makes a blockchain suitable for agentic commerce?**

Agentic commerce needs atomic multi-step settlement, scoped and programmable spending authority, high per-account throughput, low cost, and gasless transfers. A chain that lacks any of these forces agents into slow, sequential, or unsafe payment flows.

**What are Payment Intents on Sui?**

Payment Intents are a transaction type that lets one request, from an AI agent or an application, trigger multiple actions across multiple apps and settle them atomically in a single transaction. The whole workflow either completes or does not commit.

**How does Sui handle agent spending limits?**

Builders grant agents scoped authority with explicit limits on amount, timing, and recipients. These permissions are composable, so the rules are enforced at the protocol layer and hold across every application the agent uses.

**Can agents pay without holding a gas token?**

Yes. Moving stablecoins on Sui is gasless across multiple stablecoins at any size, which removes the need for an agent to acquire and manage gas for each payment. This is live on mainnet.

## Further reading

-   Sui documentation on Payment Intents and transaction architecture at [docs.sui.io](http://docs.sui.io)
-   Sui object model and parallel execution at [docs.sui.io](http://docs.sui.io)
-   Updates on gasless stablecoin transfers and confidential transfers at [blog.sui.io](http://blog.sui.io)
-   "Sui Processes Over 6 Million Transactions Per Second in AI Agent Livestream Experiment" at [blog.sui.io](https://blog.sui.io/sui-processes-over-6-million-transactions-per-second-in-ai-agent-livestream-experiment/)