agent-payment-x402

Execute x402 payments with ERC-4337 smart accounts and enforced spending policies.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Maelwalser/claude-config --skill agent-payment-x402-maelwalser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-payment-x402
Source: https://github.com/Maelwalser/claude-config/tree/main/skills/agent-payment-x402
Command: npx skills add https://github.com/Maelwalser/claude-config --skill agent-payment-x402-maelwalser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable AI agents to autonomously pay for APIs, services, or other agents while enforcing strict spending controls and avoiding custodial key management. This Skill prevents runaway costs, removes the need for human intervention on routine paid actions, and reduces operator risk by keeping keys non-custodial.

Core Features & Use Cases

  • x402 payment flow: Automatically negotiate price on HTTP 402 responses, sign transactions, and retry requests without human intervention.
  • Spending controls: Enforce per-task budgets, per-session budgets, allowlisted recipients, and rate limits to prevent overspend.
  • Non-custodial wallets: Use ERC-4337 smart accounts so agents hold their own keys while the orchestrator sets immutable spending policy.
  • Use Case: An orchestrator delegates a paid API call to an agent, sets a $0.50 per-task budget and $5/session limit, and requires pre-tool budget checks so the agent can only pay within approved bounds.

Quick Start

Configure the agentpay MCP tool with a pinned agentwallet-sdk and set an orchestrator SpendingPolicy before delegating any paid tasks.

Frequently Asked Questions about agent-payment-x402

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable autonomous payments for AI agents without risking runaway costs?

Enable autonomous payments for AI agents by enforcing an orchestrator-controlled SpendingPolicy with per-task and per-session budgets, allowing agents to pay for APIs while preventing overspend through pre-tool fail-closed checks.

How does the HTTP 402 payment flow work for AI agent API billing?

The HTTP 402 payment flow works by having AI agents automatically negotiate price on HTTP 402 responses, sign transactions, and retry requests without human intervention using MCP-compatible payment tools.

Can I use non-custodial wallets for inter-agent settlements?

Yes, you can use non-custodial wallets for inter-agent settlements by implementing ERC-4337 smart accounts, which allow agents to hold their own keys while the orchestrator sets immutable spending policies.

What is an orchestrator-enforced SpendingPolicy in agent payment systems?

An orchestrator-enforced SpendingPolicy is an immutable control mechanism that sets per-task budgets, per-session limits, allowlisted recipients, and rate limits to prevent overspend during autonomous agent transactions.

Do I need ERC-4337 smart accounts to execute autonomous agent payments?

Yes, you need ERC-4337 smart accounts because they provide the non-custodial key management framework required for agents to securely execute payments while the orchestrator maintains budget controls.

What are the limitations of using MCP-compatible payment tools for agent settlements?

Limitations of using MCP-compatible payment tools include the strict requirement for pinned agentwallet-sdk versions, explicit orchestrator-enforced SpendingPolicy configuration, and mandatory pre-tool fail-closed checks before delegating any paid tasks.