mppBuild with MPP (Machine Payments Protocol), open machine-to-machine payments over HTTP 402. Use for paid APIs, payment-gated endpoints, agent payment flows, MCP tool payments, or metered billing. Covers mppx (TS), pympp, and mpp Rust SDKs.
Install via ClawdBot CLI:
clawdbot install tenequm/mppGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Accesses sensitive credential files or environment variables
process.env.OPENAISends data to undocumented external endpoint (potential exfiltration)
post → https://api.example.com/submitCalls external URL not in known-safe list
https://datatracker.ietf.org/doc/draft-ryan-httpauth-payment/AI Analysis
The skill definition describes a legitimate payment protocol and SDK documentation. The flagged external URL (IETF datatracker) is a public standards document, not a data sink. The credential access signal appears to be a false positive from scanning code not shown in the provided excerpt.
Generated May 5, 2026
An AI model provider charges per inference request using MPP's charge intent. Clients automatically pay via HTTP 402 without API keys or manual billing. Ideal for LLM-as-a-service platforms.
A real-time language model service uses MPP session intents to bill customers based on tokens generated during a streaming session. Enables granular usage-based pricing for chatbots and content generation APIs.
Premium content platforms (e.g., research papers, video streams) gate individual articles or streams behind MPP charge intents. Users pay per piece without subscription commitments, using stablecoins or cards.
A middleware service that wraps existing APIs (e.g., OpenAI, Stripe) with MPP payment gating. Downstream clients pay the proxy per request, enabling reselling or metered access without direct subscriptions.
AI agents autonomously pay for tool calls, data feeds, or compute resources via MPP. Agents use session intents for streaming data and charge intents for one-time operations, enabling fully automated machine-to-machine commerce.
Charge a fixed amount for each API call, settled instantly via MPP. Revenue scales with usage, and customers avoid upfront commitments. Suitable for data enrichment, image processing, or verification services.
Bill customers based on consumption (e.g., tokens, bandwidth) during a session using MPP's session intent. Revenue increases with usage duration or volume, ideal for AI inference or content delivery.
Provide a white-label payment gateway that other APIs integrate via MPP. Earn transaction fees per payment processed. Scalable to numerous merchants with minimal integration effort.
💬 Integration Tip
Start with the mppx TypeScript SDK and test with Tempo test tokens in a sandbox environment before using real methods. Enable both charge and session intents to support a variety of use cases from the start.
Scored Oct 6, 2026
Audited Apr 18, 2026 · audit v1.0
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.