x402-enhancedInternet-native payments using the HTTP 402 Payment Required standard. Set up as a buyer to pay for API access, or as a seller to monetize your APIs.
Install via ClawdBot CLI:
clawdbot install notorious-d-e-v/x402-enhancedGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://docs.x402.orgAudited Apr 17, 2026 · audit v1.0
Generated Mar 21, 2026
Developers can monetize their AI agent APIs by implementing x402 payment endpoints. When external agents request data or services, the server responds with 402 Payment Required, enabling automated microtransactions for API access without user accounts.
A weather service provider can sell real-time weather data through x402. Clients request weather information, receive payment instructions, and upon payment verification, get instant access to the data. This eliminates subscription models and enables pay-per-query pricing.
News organizations can implement x402 for automated content access. When AI agents or automated systems request premium articles, they receive payment instructions and can instantly pay for single-article access, enabling microtransactions without human intervention.
Companies can create decentralized API marketplaces where multiple service providers offer APIs through x402. Each API call triggers an automated payment, enabling seamless integration between different services with instant settlement between parties.
Academic institutions or research organizations can monetize access to specialized datasets. Researchers or AI systems can pay per query for data access, with payments automatically verified and settled through the x402 protocol without manual invoicing.
Charge users per API call or data request using x402's automated payment flow. This eliminates subscription fees and enables precise billing based on actual usage, with instant settlement via stablecoins on supported blockchains.
Create a platform where multiple data providers can monetize their APIs through x402. The platform takes a small percentage of each transaction while providing the infrastructure for automated payment verification and settlement between buyers and sellers.
Operate a facilitator service that handles payment verification and blockchain settlement for x402 transactions. This service can charge a small fee for each verified transaction, providing reliable infrastructure for both buyers and sellers using the protocol.
💬 Integration Tip
Start with testnet environments like Base Sepolia or Solana Devnet to test payment flows before deploying to mainnet, and use the provided TypeScript client libraries for easier integration.
Scored May 17, 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...
Discover SameDayDesk's twenty-two account-free machine services and produce a verified, non-spending purchase intent from the live OpenAPI contract and unpaid HTTP 402 challenge. Use to select and preflight public web extraction, company or wallet enrichment, repository security scans, JSON-LD generation, AI-search audits, Morpho risk analysis, work opportunities, agent-service discoverability, agent-surface context budgets, contract-qualified service search, seller integrity, x402 or MPP payment offers, Base or Solana transaction evidence, or delegated-wallet policy conformance before a separately authorized payment executor is involved.
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.