agentleFS
nirholasnirholas/XActions/skills/x402-payments/SKILL.md

x402-payments

Skill648 starsChanged 9 months agoApache-2.0View on GitHub

Enable and integrate x402 crypto payment protocol for XActions API access. Supports multi-chain, multi-token payments for pay-per-use API calls. Use when users want to pay for XActions operations with crypto or integrate x402 into their own agent/app.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use /.well-known/x402 for discovery in agent applications

    line 91

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

x402 Payments

XActions supports the x402 payment protocol — an HTTP-native micropayment standard for pay-per-use API access with cryptocurrency.

Entry Points

GoalRouteMethod
Discover payment capabilitiesGET /.well-known/x402Public
Get OpenAPI spec with payment infoGET /api/x402/openapiPublic
Make a paid API callAny protected routeREST API (with x402 headers)

Configuration

Config lives in api/config/x402-config.js. Key settings:

{
  networks: ['base', 'ethereum', 'polygon', 'arbitrum'],  // Supported chains
  tokens: {
    base: ['USDC', 'ETH'],
    ethereum: ['USDC', 'USDT', 'ETH'],
    polygon: ['USDC', 'MATIC'],
    arbitrum: ['USDC', 'ETH'],
  },
  pricing: {
    'POST /api/operations/unfollow': { amount: '0.01', token: 'USDC' },
    'POST /api/operations/follow':   { amount: '0.005', token: 'USDC' },
    // ... per-route pricing
  }
}

Discovery (/.well-known/x402)

Returns a JSON manifest describing all payable routes, supported networks, and token addresses:

GET https://api.xactions.io/.well-known/x402

Response includes:

  • List of payable API endpoints with prices
  • Supported blockchain networks
  • Token contract addresses per network
  • Payment verification endpoint

Making a Paid Request

x402-compatible clients handle payment automatically. For manual integration:

# 1. Get payment requirements (HTTP 402 response)
POST /api/operations/unfollow → 402 Payment Required
  X-Payment-Required: { amount, token, network, recipient }

# 2. Submit on-chain payment + proof
POST /api/operations/unfollow
  X-Payment: <signed-payment-proof>

Middleware

api/middleware/x402.js handles:

  • Detecting x402-protected routes
  • Returning 402 Payment Required with payment details
  • Verifying payment proofs before processing requests
  • Multi-chain verification across Base, Ethereum, Polygon, Arbitrum

Supported Clients

Any x402-compatible client works automatically:

  • x402-axios — Axios adapter with auto-payment
  • x402-fetch — Fetch adapter with auto-payment
  • Claude agents with x402 MCP tools
  • Custom implementations following the x402 spec

Notes

  • x402 payments are per-request — no subscription needed
  • Payment proofs are cryptographically verified on-chain before operations run
  • Use /.well-known/x402 for discovery in agent applications
  • Stripe billing (billing-management skill) remains an alternative for subscription access

Related Skills

  • billing-management — Stripe subscription-based payment alternative
  • xactions-mcp-server — MCP server that uses x402 for AI agent access
  • a2a-multi-agent — Agent-to-agent workflows that use x402 for payment

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.