Automatic Http 402 Response Detection And Payment Metadata Extraction

x402 MCP server for AI agent payments. Lets Claude, Cursor, LangChain and CrewAI pay for HTTP 402–gated APIs with USDC micropayments on Base L2. Non-custodial, 0% fee. Unlike Cloudflare Pay-Per-Crawl, works on any host and settles directly on-chain.

Unique: Implements automatic 402 detection at the HTTP layer with strict metadata parsing, allowing agents to treat payment-gated APIs identically to free APIs. Uses header-based metadata (x402-*) rather than response body parsing, enabling payment requirements to be communicated without changing API response schemas.

vs others: More transparent than requiring agents to check response status codes manually; more flexible than hardcoding payment amounts per API endpoint.

via “x402-payment-protocol-negotiation”

The AI agent with a wallet — spends USDC autonomously to get real work done. Apache-2.0, TypeScript.

Unique: Implements the HTTP 402 Payment Required standard as a first-class protocol in the agent runtime, treating payment negotiation as part of the HTTP request/response cycle rather than a separate concern. Automatically handles payment proof generation and submission.

vs others: Most agent frameworks ignore HTTP 402 or treat it as an error; Franklin agents natively understand and execute the payment protocol, enabling seamless integration with future X.402-compliant service ecosystems.

via “payment metadata extraction and response formatting”

The native monetization layer for MCP tool servers — x402 payment enforcement via OWS CLI

Unique: Standardizes payment metadata extraction from OWS CLI into HTTP 402 response format, enabling interoperability between MCP servers and payment-aware clients

vs others: Provides structured payment instructions in HTTP responses rather than opaque error messages, making it easier for clients to understand and complete payment flows