ClaudeSuperPower
SubmitLog in

accept-agent-payments

Skill

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, microp

0API Tools

Install

git clone https://github.com/circlefin/skills.git ~/.claude/skills/accept-agent-payments

What is accept-agent-payments?

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.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Run shell commands

Declares Bash

Create and modify files

Declares Write or Edit

~93 tokens of context used while enabled, before you invoke anything

All declared tools (6)
BashEditGlobGrepReadWrite

Documentation

README · ~7 min read

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"

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.