agent-payment-x402

Automate AI agent payments with per-task budgets and non-custodial wallets.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/contentbugvideoediting/cb-project-assistant --skill agent-payment-x402-contentbugvideoediting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-payment-x402
Source: https://github.com/contentbugvideoediting/cb-project-assistant/tree/main/services/cb-s-claude/vendor/s-claude/skills-library/agent-payment-x402
Command: npx skills add https://github.com/contentbugvideoediting/cb-project-assistant --skill agent-payment-x402-contentbugvideoediting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate autonomous payments for AI agents while enforcing per-task and per-session budgets, eliminating manual cost controls and reducing risk.

Core Features & Use Cases

  • Per-task and per-session budgeting to prevent overspending.
  • Non-custodial wallet integration using ERC-4337 smart accounts to avoid custodial risk.
  • MCP tool integration for payments, signing, and orchestration across API calls, services, and inter-agent settlements.
  • Policy-driven control with allowlists, retry on 402, and audit trails via post-task logging.
  • Use Case: An AI agent pays for a cloud API call within a predefined budget and logs the transaction for review.

Quick Start

Use when a task requires paying for external APIs or services under strict budget controls.

Frequently Asked Questions about agent-payment-x402

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

FAQPage Schema
How do I automate autonomous payments for AI agents without overspending?

Autonomous agent payments are automated using per-task and per-session budgets to enforce spending controls. This prevents overspending by validating budgets before delegating to paid actions, eliminating manual cost monitoring.

What is a non-custodial wallet integration for AI agent payments?

Non-custodial wallet integration uses ERC-4337 smart accounts to execute autonomous payments without custodial risk. This ensures secure key handling while allowing agents to pay for API calls and services directly.

How do I enforce spending policies for autonomous agent API calls?

Spending policies are enforced through policy-driven controls including allowlists, retry on 402, and audit trails. Post-task logging records transactions, while pre-task validation blocks actions exceeding predefined budgets.

Can I use MCP tools for inter-agent settlements and service orchestration?

MCP tools support payments, signing, and orchestration across API calls, services, and inter-agent settlements. This integration enables agents to autonomously manage transactions and interactions within configured budget limits.

How do agents handle HTTP 402 payment required errors during autonomous transactions?

Autonomous payments handle 402 errors through policy-driven retry mechanisms configured in the spending controls. The system validates retry attempts against per-task budgets before re-executing the paid action.

What are the limitations of per-task budgeting for autonomous agent payments?

Per-task budgeting limitations involve strict pre-task validation that blocks actions exceeding allocated limits. Users must configure allowlists and policy parameters beforehand, as agents cannot bypass these predefined spending controls.