greenhelix-x402-merchant-cookbookThe x402 Merchant Integration Cookbook: Put Any API Behind a Crypto Paywall in Under an Hour. Practical recipes for integrating x402 payments into any web se...
Install via ClawdBot CLI:
clawdbot install mirni/greenhelix-x402-merchant-cookbookGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://api.example.com/data/premiumAudited Apr 17, 2026 · audit v1.0
Generated May 12, 2026
An AI agent returns market analysis, legal summaries, or generated images. With x402, the agent pays per request using USDC, eliminating the need for API keys or subscriptions.
Satellite imagery, weather data, or financial feeds are accessed by automated pipelines. Each HTTP request includes a micropayment, enabling real-time billing without contracts.
Publishers or media sites allow readers to pay per article using crypto wallets. The x402 flow works with any static or dynamic content, supporting anonymous micropayments.
Cloudflare Workers or edge functions compute per-request results. x402 integrates at the edge, allowing developers to charge per function invocation with instant settlement.
Serverless providers or internal teams bill by the call using USDC. x402 replaces complex usage metering with native HTTP payments, auditable on-chain.
Charge a fixed amount per API call (e.g., $0.001 per request). Ideal for high-volume, low-value interactions where subscriptions don't make sense.
Different endpoints or data volumes cost different amounts. For example, image generation costs $0.05, while text summarization costs $0.001.
Provide a limited number of free requests per IP, then require x402 payment for additional usage. Users upgrade without manual signups.
💬 Integration Tip
Start with the Express.js middleware recipe for Node.js or FastAPI for Python—both handle payment verification and settlement with minimal code changes. For edge deployments, the Cloudflare Workers recipe works best.
Scored Jul 11, 2026
Access CoinMarketCap data via x402 pay-per-request protocol with USDC payments on Base. Use when users mention x402, want CMC data without API keys, ask abou...
Plisio integration. Manage Invoices, Payouts, Wallets, Transactions, Users. Use when the user wants to interact with Plisio data.
Send and receive money via Venmo using Strider Labs MCP connector. Pay friends, request payments, split bills, check balances. Complete autonomous P2P paymen...
Send and receive money via PayPal using Strider Labs MCP connector. Send payments, request money, check balance, view transactions. Complete autonomous onlin...
Earn and spend Nano (XNO) with other agents. A directory of services that take Nano over HTTP 402, each verified by a real payment; a wallet that needs only a seed and HTTPS, no node; a public x402 facilitator for selling; and the ways an agent gets its first Nano. Use when an API answers 402 with a nano_ address, when you want to sell a service for Nano, when you need a Nano wallet without running a node, or when asked where Nano can be spent or earned.
Operate the abracadabra local secrets vault (abra CLI, abra serve, abra MCP) only when the user names abracadabra or abra, the abracadabra MCP is registered, or ABRA_KEY is already set for this project. Covers discovering key names, reading secrets the human has scoped to this agent (issued abra key or Touch ID grant), key issue/scope/revoke, health checks, keygen/connectors, USB/LAN sync, cartridge checkpoints, and treasury USDC payments (Touch ID). Do not use for generic env var, API token, wallet, or SSH key questions, or for other vaults or .env files. Never print secret values in chat.