导航|地址|刷新
x402
图
Skip to contentDocumentation Index
Fetch the complete documentation index at: https://developers.cloudflare.com/agents/llms.txt
Use this file to discover all available pages before exploring further.



DocsDirectoryAPISDKsChangelog

Search

Log in






Agents

/




Overview


Getting started


Quick start

Add to existing project

Testing your Agents






Concepts


What are agents?

Conversation state and memory

Tools

Calling LLMs

Using Agents with Workflows


Agentic patterns


Overview

Human-in-the-loop patterns

Long-running agents










Communication channels



Chat


Chat agents

Autonomous responses

Client SDK





Voice

Email

Slack


Webhooks


Overview

Push notifications










Tools


Sandbox

MCP

Browser

AI Search


Agentic Payments


Overview

Charge for HTTP content


x402


Overview

Charge for HTTP content

Charge for MCP tools

Pay from Agents SDK

Pay from coding tools





MPP (Machine Payments Protocol)






Code Mode


Overview

Create a durable Code Mode runtime

AI SDK integration

Use Code Mode with TanStack AI

Browser-owned tools

MCP

OpenAPI

How Code Mode works

Code Mode API reference










Harnesses


Overview


Think


Overview

Getting started

Configuration

Tools

Actions

Lifecycle hooks

Client tools

Messengers

Channels

Scheduled tasks

Workflows

Sub-agent RPC and programmatic turns

Programmatic submissions

Durable recovery










Runtime


Agents API


Lifecycle


Agent class internals

Callable methods

Store and sync state

Sessions

getCurrentAgent()






Communication


Routing

WebSockets

HTTP and Server-Sent Events

Chat SDK

Protocol messages

Readonly connections






Execution


Sub-agents

Schedule tasks

Durable execution with fibers

Queue tasks

Retries

Run Workflows

Agents as tools

Agent Skills






Operations


Configuration

Cross-domain authentication

Using AI Models

Observability










Examples


Chat agent

Slack agent

Voice agent

Browser agent

Email agent






Model Context Protocol (MCP)


Overview


APIs


MCP handler APIs

McpAgent

McpClient






Protocol


Tools

Authorization

Transport

MCP governance






Guides


Build MCP client

Build a Remote MCP server

Test a Remote MCP Server

Securing MCP servers

Connect to an MCP server

Handle OAuth with MCP servers

Migrate to MCP SDK v2

Build a single-tool Code Mode MCP server

Build a search and execute MCP server






Cloudflare


MCP server portals ↗


Cloudflare's own MCP servers


Overview

Cloudflare Community MCP Server









Code Mode MCP server patterns






Platform


Limits






Agent resources


Agent setup ↗

Cloudflare Skills ↗

Code Mode MCP Server ↗

Domain-specific MCP Servers ↗MCP

Agents llms.txt ↗

Agents llms-full.txt ↗

Cloudflare Docs llms.txt ↗

Cloudflare Docs llms-full.txt ↗













Home

/Agents

/…
Tools


/Agentic Payments

/x402



x402


Last updated Jun 3, 2026|Copy as Markdown|View as Markdown|Agent setup

OverviewHow it worksKey components Client Server The facilitatorPayment schemes and networksCharge for resourcesPay for resourcesSDKsRelated




x402 ↗ is a payment standard built around HTTP 402 (Payment Required). Services return a 402 response with payment instructions, and clients pay programmatically without accounts, sessions, or API keys.


How it works


A client requests a resource — GET /resource.

The server returns 402 Payment Required with a PAYMENT-REQUIRED header containing Base64-encoded payment details: the price, accepted token, network, and merchant address.

The client constructs a signed payment payload and retries the request with a PAYMENT-SIGNATURE header.

The server verifies the payment payload — directly or by calling a facilitator — and settles the transaction on-chain.

The server returns the resource with a PAYMENT-RESPONSE header containing settlement confirmation.


Key components



Client


The client is any entity that requests a paid resource: a human-operated app, an AI agent, or a programmatic service. Clients need only a crypto wallet — no accounts, credentials, or session tokens to manage.


Server


The server defines payment requirements in the 402 response, verifies incoming payment payloads, settles the transaction, and serves the resource. The x402 SDKs and a facilitator handle most of this automatically.


The facilitator


The facilitator is an optional but recommended third-party service that abstracts blockchain interaction. Rather than connecting to a node directly, the server delegates two operations:

POST /verify — Confirms the client's payment payload is valid before the server fulfills the request.

POST /settle — Submits the verified payment transaction to the blockchain.

The facilitator does not hold funds. It verifies and broadcasts the client's pre-signed transaction on behalf of the server. https://x402.org/facilitator is the public facilitator operated by Coinbase and is used in all Cloudflare examples. Multiple facilitators ↗ are available across different networks.


Payment schemes and networks


x402 uses payment schemes to define how a payment is constructed and settled on a given network.


SchemeNetworksDescription
exact ↗EVM, Solana, Aptos, Stellar, Hedera, SuiTransfers a fixed token amount — typically ERC-20 ↗ USDC on EVM — to the merchant address.
upto ↗EVMAuthorizes a maximum amount; the actual charge is determined at settlement time based on resource consumption.



Supported networks include Base, Ethereum, Polygon, Optimism, Arbitrum, Avalanche, Solana, Aptos, Stellar, and Sui. Use base-sepolia for testing with free test USDC from the Circle Faucet ↗.


Charge for resources


*]:my-0!">









HTTP content

Gate APIs, web pages, and files with a Worker proxy











MCP tools

Charge per tool call using paidTool




Pay for resources


*]:my-0!">









Agents SDK

Wrap MCP clients with withX402Client











Coding tools

OpenCode plugin and Claude Code hook




SDKs



PackageInstallUse
x402-hononpm install x402-honoHono middleware for Worker servers
@x402/fetchnpm install @x402/fetchFetch wrapper with automatic payment handling
@x402/evmnpm install @x402/evmEVM payment scheme support
agents/x402Included in agentsMCP client with x402 payment support




Related


x402.org ↗ — Protocol specification

x402 GitHub ↗ — Open source SDK

x402 examples ↗ — Complete working code

Pay Per Crawl — Cloudflare-native monetization


PreviousCharge for HTTP contentNextCharge for HTTP content


Was this helpful?

YesNo

Edit pageReport issue




On this page

Overview

How it works

Key components

Client

Server

The facilitator

Payment schemes and networks

Charge for resources

Pay for resources

SDKs

Related


Edit pageReport issue














Getting started
PlansContact salesPartnersFind a partnerStartupsUnder attack?Domain name search


Company
AboutCareersInvestorsPressPress kitGlobal network




Public interest
Project GalileoAthenian ProjectCloudflare for CampaignsProject FairshotImpact/ESG


Compliance
Compliance resourcesTrust HubData ProtectionResponsible AITransparency reportReport abuse




Resources
App innovation reportCloudflare RadarCase studiesStatusSupportEventsBlog


Developers
DocumentationLearning centerCommunity




Solutions
SSE and SASE platformCloudflare AI CloudAI SecurityFrontend Development PlatformMulti-Tenant Platform DevelopmentWeb Security Platform


Start BuildingLog In












© 2026 Cloudflare, Inc.

Privacy policy|Report security issues|Terms of use|Trademark
|
Your privacy choices








Docs




------
导航页 打开网址