"Understanding HTTP Requests" matching MCP connectors:
Matching Connector Tools:
Pay for HTTP APIs and charge for your own: x402 micropayments in USDC on Base.
Agent-native helpdesk. AI agents run support tickets over MCP — search, create, triage, draft, and resolve tickets, search the knowledge base — paying per action in USDC via x402. Read tools are free; priced tools return HTTP 402 with payment terms.
Delegare provides secure payments for AI agents. Google AP2-powered payment authorization for AI agents. Issue scoped spending mandates with hard limits, merchant controls, and no exposure of card credentials or private keys. Agents pay across dual rails: cards and ACH via Stripe, or USDC and USDT on Coinbase Base. Supports paid API access and x402-protected requests through MCP.
Read-only buyer-side MCP spend gate for paid APIs, MCP endpoints, and x402 routes. Returns BUY / WAIT / AVOID with maxSpendUsd, receipt expectations, trust/freshness health, safety boundaries, and next action before an agent spends.
Read-only BUY / WAIT / AVOID spend gate for paid APIs, MCP endpoints, and x402 routes.
The first commercial implementation of HTTP 402 Payment Required for creator content monetization. AI agents pay $0.0025 per content pull from paywalled creator libraries. Patent-pending micropayment infrastructure — creators get paid automatically.
AI access to your Qualy payments back office: contacts, payment requests, and search.
Agent x402 Paywall MCP — Coinbase HTTP 402 protocol + on-chain settlement. Agents pay per-call
ommission infrastructure for AI-driven commerce. 7 MCP tools for program discovery, agent attribution, conversion tracking, and commission settlement. Supports stdio (npx syndicate-links-mcp) and remote HTTP transport.
- Shabaas TestDeprecated
ShabaasPay MCP is a secure Model Context Protocol connector that lets AI agents interact with ShabaasPay services for payment workflows, account operations, and transaction insights through a remote HTTP endpoint.