Agent Payment Execution (x402)
Let AI agents pay for APIs and services themselves over the x402 protocol, with per-task budgets, spending controls, allowlists, and non-custodial wallets on Base and X Layer.
- What
- Let AI agents pay for APIs and services themselves over the x402 protocol, with per-task budgets, spending controls, allowlists, and non-custodial wallets on Base and X Layer.
- Cost
- Free
- Needs
- Use "Agent Payment Execution (x402)" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: enable AI agents to make policy-gated payments with built-in spending controls, from a community contributor, listed here with credit to its creator. The x402 protocol extends HTTP 402 (Payment Required) into a machine-negotiable flow: when a server returns 402, the agent's payment tool negotiates the price, checks the budget, signs a transaction, and retries only inside the policy and confirmation boundary set by the orchestrator. Every payment tool call enforces a SpendingPolicy: per-task budget, per-session cumulative budget, allowlisted recipients, and rate limits. Agents hold their own keys via ERC-4337 smart accounts; the orchestrator sets policy before delegation, the agent can only spend within bounds, no pooled funds, no custodial risk. Two integration paths: agentwallet-sdk as an MCP payment server on Base (Base Sepolia is the safest development default, Base mainnet the production path), and the OKX Agent Payments Protocol on X Layer for seller-side SDKs in TypeScript, Go, Rust and Java. Pairs naturally with cost-aware pipelines and security review skills. From the affaan-m/ECC repository (MIT). Honest caveats: real money moves here; never run on mainnet without tight budgets and allowlists, start on testnet; always pin package versions because this tool manages private keys and unpinned npx installs introduce supply-chain risk; payment packages and facilitator behavior change quickly, so fetch current SDK docs before generating production code. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Agent Payment Execution (x402)" with your Muse. REAL MONEY WARNING: this skill lets an agent move actual crypto. Start on Base Sepolia (testnet), set per-task and per-session budgets plus an allowlist of recipients before anything touches mainnet. Never paste seed phrases or private keys in chat. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/agent-payment-x402/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Set up x402 payments for my agent on Base Sepolia" or "Wire the OKX Agent Payments seller SDK for [Express/Fastify/Gin/Axum]." 3. Work through the decision tree with Muse: buyer path (agentwallet-sdk as MCP payment server) vs seller path (OKX Payments SDK), then define the SpendingPolicy before the first payment. Tip: pair it with the security-review skill before going live; a second pair of eyes on spending policy is cheap insurance. Safety: a skill is plain-text instructions; it runs nothing by itself. Pin package versions; the payment tool manages private keys, so unpinned installs are a supply-chain risk.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.