pay-via-agent-wallet

Search, inspect, and pay for x402 marketplace APIs with USDC micropayments.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Surojit012/CMO --skill pay-via-agent-wallet-surojit012
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pay-via-agent-wallet
Source: https://github.com/Surojit012/CMO/tree/main/.agents/skills/pay-via-agent-wallet
Command: npx skills add https://github.com/Surojit012/CMO --skill pay-via-agent-wallet-surojit012

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents often hit walls when a task requires live data, paid APIs, or services behind paywalls, rate limits, or API-key signup flows. This Skill lets an agent discover paid HTTP endpoints in the Circle services marketplace and pay per call in USDC via the x402 protocol, with no API keys, accounts, or prefunded billing. ## Core Features & Use Cases - Marketplace Discovery: Search the Circle services marketplace by keyword (circle services search) to find paid endpoints for crypto prices, prediction-market odds, web search, weather, sports stats, academic research, and communication APIs. - Inspect Before Paying: Confirm price, accepted chains, payment scheme (Gateway vs vanilla x402), and request schema with circle services inspect or a raw 402 probe before any funds move. - USDC Payment Execution: Settle per-call payments with circle services pay, including cost estimates, per-call spending caps, chain selection across BASE, MATIC, ETH, ARB, OP, AVAX, and UNI, and structured error recovery for 422 schema mismatches and chain rejections. - Use Case: A user asks for current prediction-market odds. The agent searches the marketplace, inspects a Predexon-backed endpoint, confirms the $0.005 price, pays in USDC on Polygon, and returns the odds JSON. ## Quick Start Ask the agent to look up the current price of Bitcoin using a paid marketplace service and it will search, inspect, and pay for the API call in USDC automatically.

Frequently Asked Questions about pay-via-agent-wallet

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

FAQPage Schema
How do I call a paid API with USDC using the Circle CLI?

Run circle services search with a keyword to find endpoints, circle services inspect to confirm price and schema, then circle services pay with the service URL, wallet address, chain, and JSON data payload. The CLI signs the payment authorization and returns the endpoint response.

What is the x402 protocol for API payments?

x402 is a payment protocol where HTTP endpoints return a 402 response listing accepted chains and schemes, and clients settle a small USDC fee per call. It removes the need for API keys, accounts, or prefunded billing.

Which blockchains does Circle services pay support?

Supported chain values include BASE, MATIC (Polygon), ETH, ARB, OP, AVAX, and UNI. The seller's accepts array dictates payable chains, and the CLI error hint tells you which chain to retry with if one is rejected.

Why does circle services pay return HTTP 422?

A 422 means the request payload schema is wrong, not a transient error. If the CLI says payment was not charged, fix the --data fields and retry; if it says payment was submitted, check the payment log in ~/.circle-cli/payments/ and wallet balances before retrying.

What is the difference between Gateway and vanilla x402 payments?

Gateway (GatewayWalletBatched) uses a deposited balance and settles calls in under 500ms, while vanilla x402 pays directly per call in about 2 seconds. When a seller accepts both, the CLI picks Gateway first, so a Gateway deposit may be needed.

What should I do when the agent wallet has no USDC balance?

Hand off to the fund-agent-wallet skill, which covers fiat on-ramp purchases, direct address transfers with a QR code, and Gateway deposits. An eco deposit on BASE settles on Polygon in roughly 30-50 seconds for a $0.03 flat fee.