什么是 配置 x402 微支付？

配置 x402 技能为自主的智能体间商业启用了 HTTP 原生支付协议。通过利用 HTTP 402 Payment Required 状态码，该技能允许智能体在每笔 API 调用中以低于一美分的 USDC 结算交易。凭借 Base 网络上亚秒级的结算时间，它为 Openclaw Skills 提供了一个稳健的框架，无需 API 密钥、手动账户或订阅即可运行。

该工具支持双向支付流，这意味着可以配置智能体为外部服务付费、为其自身工具接收付款，或两者兼而有之。通过集成此技能，开发者可以将他们的 AI 智能体转变为创收的服务提供商，或是不断增长的智能体经济中的高级消费者。

下载入口:https://github.com/openclaw/skills/tree/main/skills/wpank/configure-x402

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

配置 x402 微支付 应用场景

• 通过微支付门槛将特定的 MCP 工具或 API 端点变现。
• 使智能体能够自主支付高价值数据，例如实时代币报价或资金池分析。
• 为复杂的链上操作（如兑换或流动性提供）设置按执行付费的工作流。
• 通过标准化清单自动化智能体间的服务发现和计费。

1. 分析用户请求，确定所需的模式（支付、接收或两者兼有）以及目标 USDC 钱包地址。
2. 验证 Base 网络上的钱包地址，确保其可以发送或接收 USDC 代币。
3. 在 .uniswap/x402-config.json 生成本地配置文件，其中包含定价层级、支出限制和辅助器详情。
4. 在 .well-known/x402-manifest.json 创建公开的发现文件，向生态系统中的其他智能体宣传受限工具。
5. 通过检查辅助器可用性并确保钱包具有自动结算所需的代币授权来验证设置。

配置 x402 微支付 配置指南

要初始化支付协议，请确保您的智能体在 Base 网络上有一个存有 USDC 余额的活跃钱包。您可以通过提供钱包详情和首选定价模型来配置该技能。

# 同时支付和接收 USDC 的智能体示例配置
configure-x402 --walletAddress  --mode both --maxSpendPerHour 1.00

配置 x402 微支付 数据架构与分类体系

该技能管理两个主要的元数据文件，以促进运行时支付和发现：

内部定价按工具类别结构化，从基础数据报价的 0.001 美元到交易执行的 0.05 美元不等。

name: configure-x402
description: Configure x402 micropayments for agent-to-agent commerce via Uniswap. Set up your agent to pay per MCP request in USDC on Base (~200ms settlement) or accept x402 payments as a service provider. Use when the user wants to enable pay-per-use API access or monetize their agent's services.
model: sonnet

Configure x402

Overview

Configures the x402 HTTP-native payment protocol for agent-to-agent micropayments settled on Base. x402 uses the HTTP 402 "Payment Required" status code to enable pay-per-request billing — agents pay fractions of a cent per API call in USDC, with ~200ms settlement, no API keys, no accounts, and no subscriptions.

This skill supports two modes:

• Pay mode: Configure your agent to pay for MCP tool calls and external API access via x402
• Accept mode: Configure your agent as an x402 service provider that accepts micropayments for its services
• Both: Enable bidirectional x402 payments

x402 has processed 100M+ agent-to-agent transactions across 80+ ecosystem projects (Feb 2026). It eliminates API key onboarding friction and creates revenue streams from every agent interaction.

When to Use

Activate when the user says:

• "Set up x402 payments for my agent"
• "Enable pay-per-swap via x402"
• "Configure my agent to accept x402 payments"
• "Set up micropayments on Base"
• "Enable x402 for my MCP server"
• "Monetize my agent's API"
• "Configure pay-per-request billing"
• "Set up agent-to-agent payments"

Parameters

Recommended Pricing (Accept Mode)

Workflow

1. Parse configuration from the user's request. Determine the payment mode, wallet address, chain, pricing, and tool scope. Validate the wallet address format.

2. Validate wallet: Verify the wallet address exists on the target chain and has a USDC balance (for pay mode) or can receive USDC (for accept mode). Check that the chain supports x402 settlement.

3. Write x402 configuration: Generate the x402 configuration file at .uniswap/x402-config.json with:

   • Payment mode (pay/accept/both)
   • Wallet address and chain
   • Facilitator endpoint
   • Per-tool pricing (accept mode)
   • Spending limits (pay mode)
   • Supported tools list

   For accept mode, also generate the .well-known/x402-manifest.json that advertises the agent's x402-enabled endpoints to other agents.

4. Verify setup: Confirm the configuration is valid by checking:

   • Wallet connectivity on the settlement chain
   • Facilitator availability
   • USDC token approval for the facilitator contract (if pay mode)
   • Configuration file is properly formatted

Output Format

x402 Configuration Complete

  Mode:         Both (pay + accept)
  Chain:        Base (8453)
  Wallet:       0x1234...abcd
  Facilitator:  Auto-selected (Coinbase x402)

  Pay Mode:
    Max Spend:  $1.00/hour
    USDC Balance: $50.00 (sufficient)

  Accept Mode:
    Pricing:
      Price quotes:       $0.001/call
      Pool analytics:     $0.003/call
      Route optimization: $0.005/call
      Simulation:         $0.010/call
      Execution:          $0.050/call
    Tools Gated:  All (17 tools)

  Config Files:
    .uniswap/x402-config.json
    .well-known/x402-manifest.json

  Status: Ready for x402 payments

Important Notes

• x402 settles on Base by default (~200ms). Ethereum mainnet settlement is possible but slower and more expensive.
• USDC is the only supported payment token for x402. The wallet must hold USDC on the settlement chain.
• The maxSpendPerHour safety limit prevents runaway costs in pay mode. Adjust based on expected usage.
• x402 uses the HTTP 402 "Payment Required" status code. When a client hits an x402-gated endpoint without payment, it receives a 402 response with payment instructions.
• Facilitators handle the payment settlement. The "auto" option selects the best available facilitator on the target chain.
• For accept mode, the .well-known/x402-manifest.json file makes your agent discoverable on Coinbase Bazaar (12,365+ services).
• x402 payments are per-request. There are no subscriptions, API keys, or accounts. Each request includes a micropayment.
• All x402 transactions are logged for treasury management and can be tracked via the manage-treasury skill.
• This skill does not execute any on-chain transactions. It only generates configuration files. The actual x402 payment flow happens at runtime when the MCP server processes requests.

Error Handling