accept-agent-paymentslisted

Use when a developer wants to monetize an API, endpoint, service, model, dataset, tool, or agent-facing resource with Circle USDC pay-per-call payments, Gateway Nanopayments, x402, HTTP 402, or Agent Marketplace listing. Triggers on: charge agents, sell to agents, paid API, monetize endpoint, micropayments, nanopayments seller, x402 seller, accept USDC, service listing.
Ekinoxis-evm/claude-skills · ★ 0 · AI & Automation · score 63

Install: claude install-skill Ekinoxis-evm/claude-skills

# Accept Agent Payments ## Overview Turn an existing HTTP endpoint into a paid agent-consumable service. Default to Circle Gateway Nanopayments: x402 handles the `402 Payment Required` negotiation, Gateway handles gasless USDC authorizations and batched settlement. This is a seller-side skill. Buyer wallet setup is only a test harness; do not let it swallow the work. ## Red Flags Stop and re-plan if your answer says any of these: - "Use standard x402 exact on Base by default" - "Default to Base mainnet" - "Gateway batching can come later" - "Use `x402[fastapi]` because the app is FastAPI" - "Register the service with `circle services publish`" Those are generic x402 seller instincts, not this Circle seller path. The default is Circle Gateway Nanopayments, current docs, supported-network discovery, and marketplace submission prep. ## Default Path Use Circle Gateway Nanopayments unless the user explicitly needs vanilla x402 compatibility or a non-Gateway facilitator. Generic x402.org examples, FastAPI middleware, Bazaar metadata, and Base-mainnet vanilla `exact` are not Circle's default seller path for agent nanopayments. | Situation | Path | |---|---| | Sub-cent, cent-level, high-frequency, or agentic API calls | Gateway Nanopayments | | Existing Express or Node API | Add `@circle-fin/x402-batching` middleware | | FastAPI, Rails, Go, or other non-Node API | Prefer a thin Express payment proxy for Circle Gateway unless current Circle docs provide a native library | |