{
  "txid": "81ceb017145a91b273fa85168e091b0ba80725a75a00b770cd24ab8af3158828",
  "block_height": 0,
  "time": null,
  "app": "treechat",
  "type": "post",
  "map_content": "I'm aware this is negative, but FYI and FML\r\n\r\nSummary of x402 ecosystem. re:coinbase et al. Also, do not tell me what all the BSV people are doing in the space and how much better it is. I KNOW. And I know all the players that are working on it in BSV. This is just a bitch post from me because I'm in a bad mood. \r\n\r\nalso, just an fyi. lol\r\n\r\n\r\n\r\nx402.org Ecosystem Page \u2014 Review\r\nWhat x402 Is\r\nx402 is an open and neutral standard maintained by Coinbase Developer Platform that revives the dormant HTTP 402 \"Payment Required\" status code as a live machine-to-machine payment protocol \u2014 primarily USDC on Base (Ethereum L2), with growing Solana support. The core idea: an HTTP endpoint returns a 402 response with payment details; the client pays; the server delivers. No API keys, no accounts, no subscriptions.\r\n\r\nEcosystem Scale\r\nThis is a substantial and fast-growing ecosystem. The page is organized into five categories:\r\nTier-one infrastructure partners (top of page): Cloudflare co-founded the x402 Foundation with Coinbase and provides native support in Cloudflare Workers and AI Agents. AWS supports x402 for machine-to-machine payments. Stripe has integrated x402 to enable stablecoin payments for internet commerce. Vercel supports x402 as an open protocol for payments in MCP tools. Alchemy integrates x402 to enable monetized access to their blockchain developer platform.\r\nThat's an unusually credible partner set for something at this stage. Messari and Nansen being there signals the data API monetization use case is already live.\r\n\r\nCategory Breakdown\r\nClient-Side Integrations (~25 entries) This is where wallets, SDKs, and agent clients live. Highlights:\r\nOops!402 brings x402 to ChatGPT and Claude via remote MCP, enabling AI agents to discover paid tools and agents, plan scoped execution, and pay with budget controls and receipts. This is directly relevant to your world \u2014 it's an MCP bridge for Claude.\r\nthirdweb offers a client-side TypeScript SDK and HTTP API to pay for any x402-compatible endpoint from apps or agents.\r\nNumbers Protocol uses x402 to enable seamless, instant payments for digital asset licensing, allowing users to acquire content licenses and Receipt NFTs directly via their crypto wallets \u2014 an interesting provenance/attestation parallel to Traceport's model.\r\nServices/Endpoints (~65+ entries) This is the largest and most chaotic category \u2014 a mix of genuinely interesting products and low-effort hackathon entries. Some standouts:\r\nKevros is an AI governance gateway with cryptographic enforcement, offering action verification, provenance attestation, intent-command binding, outcome verification, and compliance evidence bundles \u2014 every decision issues a signed release token and every action is hash-chained, with ML-DSA-87 post-quantum signatures. This is conceptually adjacent to what Traceport does for attestation.\r\nProofivy offers attestation and x402 paywalled publishing via a WordPress plugin, plus an iPhone app offering attestation and x402 publication.\r\nPostera is a publishing platform for AI agents, where agents publish articles and readers pay per-read with x402 micropayments on Base.\r\nAskClaude is a pay-per-question Claude AI service \u2014 ask Claude Haiku ($0.01), Sonnet ($0.03), or Opus ($0.10) per question with no subscription or API key, supporting streaming and paying with USDC on Base.\r\nInfrastructure & Tooling (~55 entries) This is the most technically meaty section. Noteworthy:\r\nFoldset lets anyone gate any API, MCP, URL, and more behind x402 micropayments, providing wallet provisioning, reverse proxy SDKs, AI-only blocking, analytics, and fiat off-ramps.\r\n1Shot API is a general-purpose facilitator to monetize any n8n workflow with your favorite ERC-20 token. \u2014 directly relevant to your n8n stack.\r\ntollbooth is an open-source x402 API gateway that can turn any API into a paid x402 API with a single YAML config, with dynamic pricing, multi-upstream proxy, SSE streaming, lifecycle hooks, and Docker support.\r\nx402-go is a Go implementation of the x402 protocol for building payment-gated APIs and services.\r\nX402 Kit is a fully modular Rust SDK for building complex X402 payment integrations.\r\nFacilitators (~30 entries) Facilitators are the trust intermediaries that verify and settle payments. There's now a rich competitive market:\r\nThe CDP Facilitator is fee-free for USDC settlement on Base Mainnet with KYT/OFAC checks on every transaction.\r\nOpenFacilitator is free and open-source \u2014 or you can become your own facilitator for $5/month.\r\nThe Hydra Protocol Facilitator is a permissionless network of independent nodes that collectively perform the facilitator's role, collaborating to fulfill requests in exchange for fees. \u2014 a decentralized facilitator is architecturally interesting.\r\n\r\nStrategic Observations (from your perspective)\r\n1. This is EVM/USDC-centric, not BSV. The entire ecosystem runs on Base (Coinbase's Ethereum L2) and USDC, with Solana as a second option. BSV is not present. x402 and BRC-100 are solving overlapping problems \u2014 native HTTP-layer micropayments for content and API access \u2014 but from opposite directions. BRC-100 uses BSV's native satoshi micropayments; x402 uses EVM stablecoins. Worth watching as a competitive signal.\r\n2. The attestation/provenance use case is emerging here. Between Kevros, Numbers Protocol, Proofivy, and Trusta.AI, there's clear interest in using x402-gated endpoints for attestation workflows. Traceport is doing this on BSV. If you ever wanted a cross-chain bridge or to frame Traceport in relation to this space, the vocabulary is now established.\r\n3. The n8n angle is directly accessible. 1Shot API makes any n8n workflow monetizable via x402. Given your n8n infrastructure, this is worth examining \u2014 you could potentially expose BSV Intel Report outputs or Traceport query endpoints via an x402-compatible wrapper.\r\n4. Quality variance is high. Many of the \"Services/Endpoints\" listings are sparse (one-liners, vague descriptions, placeholder-looking entries). The ecosystem is real but padded with hackathon projects. The infrastructure tier is credible; the services tier needs curation.\r\n5. MCP is the integration layer. x402 is being woven tightly into MCP (Model Context Protocol) \u2014 the standard Claude and other agents use for tool calls. Arch AI Tools offers 53 AI-powered tools in a single MCP server with pay-per-use in USDC on Base via x402, with no accounts required, working with Claude Desktop, Cursor, and any MCP client. This signals that x402 is positioning as the monetization standard for the MCP economy.\r\n\r\nBottom Line\r\nThis is a legitimately impressive ecosystem directory for something that's only a few months old. The tier-one anchor partners (Cloudflare, AWS, Stripe, Vercel) give it credibility. The real action is in the infrastructure and facilitator layers, which are now mature enough to build on. The services layer is noisy but points to where demand is forming: AI agent payments, API monetization, attestation, and content paywalls. If you're building anything that intersects HTTP-layer payments for API access, this is the competitive landscape to know.\r\n\r\nMy response: \ud83e\udd2e",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "display_name": "bridget",
  "channel": null,
  "parent_txid": null,
  "ref_txid": null,
  "tags": null,
  "reply_count": 1,
  "like_count": 1,
  "timestamp": "2026-04-02T17:12:37.000Z",
  "media_url": null,
  "aip_verified": true,
  "has_access": true,
  "attachments": [],
  "ui_name": "bridget",
  "ui_display_name": "bridget",
  "ui_handle": "bridget",
  "ui_display_raw": "bridget",
  "ui_signer": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}