From xactions
Integrates x402 crypto payment protocol for pay-per-use XActions API access. Supports multi-chain (Base, Ethereum, Polygon, Arbitrum) and multi-token (USDC, ETH, USDT, MATIC) payments. Use for crypto billing or x402 integration in apps.
npx claudepluginhub nirholas/xactionsThis skill uses the workspace's default tool permissions.
XActions supports the [x402 payment protocol](https://x402.org) — an HTTP-native micropayment standard for pay-per-use API access with cryptocurrency.
Builds x402 protocol for HTTP 402 on-chain micropayments in paid APIs, paywalls, AI agents. Supports TypeScript, Python, Go SDKs on EVM, Solana, Stellar, Aptos.
Injects x402 payment middleware into Node.js/Express APIs for USDC micropayments on Base L2. Use to monetize API endpoints or MCP servers with machine-to-machine paywalls.
Guides HTTP 402 Payment Required implementation for crypto micropayments, Lightning Network LSAT/L402, L2 channels, stablecoin streaming, and API monetization.
Share bugs, ideas, or general feedback.
XActions supports the x402 payment protocol — an HTTP-native micropayment standard for pay-per-use API access with cryptocurrency.
| Goal | Route | Method |
|---|---|---|
| Discover payment capabilities | GET /.well-known/x402 | Public |
| Get OpenAPI spec with payment info | GET /api/x402/openapi | Public |
| Make a paid API call | Any protected route | REST API (with x402 headers) |
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
}
}
/.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:
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>
api/middleware/x402.js handles:
402 Payment Required with payment detailsAny x402-compatible client works automatically:
x402-axios — Axios adapter with auto-paymentx402-fetch — Fetch adapter with auto-payment/.well-known/x402 for discovery in agent applicationsbilling-management skill) remains an alternative for subscription access