neckr0ik-x402-paymentsx402 payment protocol for AI agents. Enables autonomous micropayments using HTTP 402 status codes and stablecoins. Use when you need to pay for API access, a...
Install via ClawdBot CLI:
clawdbot install neckr0ik/neckr0ik-x402-paymentsGrade 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/premiumAudited Apr 17, 2026 · audit v1.0
Generated Mar 21, 2026
AI agents autonomously pay for premium API calls using stablecoins via HTTP 402 responses, eliminating the need for manual API key management or subscriptions. This enables on-demand access to data services, such as financial analytics or weather forecasts, with micropayments per request. Ideal for dynamic agent workflows requiring intermittent access to paid endpoints.
Developers deploy x402-enabled APIs that automatically charge per request, allowing monetization of individual microservices without user accounts. For example, a machine learning model endpoint can charge a small fee per inference, facilitating pay-per-use models. This supports scalable revenue streams for niche or high-cost computational services.
Data providers use x402 to sell access to datasets or real-time feeds directly to AI agents, with payments settled on blockchain for transparency. Agents can purchase specific data slices, such as stock prices or sensor readings, without intermediaries. This fosters trustless transactions in decentralized ecosystems like DeFi or IoT.
Media platforms integrate x402 to allow AI agents to pay for premium content, such as news articles or research papers, on a per-access basis. Agents can autonomously retrieve paid content for analysis or summarization, bypassing subscription barriers. This enhances accessibility for automated content consumption in publishing or education.
IoT devices with x402-enabled APIs charge AI agents for data access or control commands, enabling autonomous transactions in smart environments. For instance, an agent might pay to retrieve sensor data from a smart city infrastructure or trigger a device action. This supports machine-to-machine economies in automation and smart grids.
API providers charge a small fee per request using x402, allowing users to pay only for what they consume without upfront commitments. Revenue is generated from micropayments in stablecoins, scalable across high-volume endpoints. This model reduces barriers to entry for users and ensures predictable income for providers.
Operators run x402 facilitators that handle payment processing and blockchain interactions, earning fees for transaction settlement and verification. Facilitators bridge AI agents and API servers, ensuring reliable payment flows. Revenue comes from service fees per transaction, incentivizing network growth and reliability.
Companies offer tools or middleware that simplify x402 integration for developers, such as SDKs or plugins for popular frameworks. These tools help businesses adopt the protocol quickly, generating revenue through licensing, support, or premium features. This model capitalizes on the growing demand for autonomous payment solutions.
💬 Integration Tip
Start by testing with the 'check' command to verify endpoint compatibility, then use 'pay' for simple transactions before deploying a full 'serve' setup. Ensure wallet configuration is secure using environment variables for private keys.
Scored Apr 19, 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...
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.