Path402 — Tokenised Web Content For AI Agents
Register Path402 so your coding agent can discover, pay for, and fetch token-gated web pages through the $402 protocol instead of failing on 402 responses.
Overview
Path402 is an MCP server for the Build phase that lets AI agents discover, acquire, and re-serve tokenised web content through the $402 protocol and a configured BSV wallet.
What is this MCP server?
- Official MCP server package path402 v1.3.2 over stdio for Claude Code, Cursor, and other MCP hosts
- Supports discover, acquire, and re-serve flows for tokenised web content via the $402 protocol
- PATH402_DEFAULT_BUDGET sets default spending in satoshis per token acquisition
- On-chain purchases using PATH402_WALLET_WIF (secret BSV private key in WIF format)
- PATH402_API_URL targets the Path402 API (documented default https://path402.com)
- MCP server schema version 1.3.2; npm package identifier path402 with stdio transport
- Three documented environment variables: PATH402_API_URL, PATH402_DEFAULT_BUDGET, PATH402_WALLET_WIF
- Default API base URL documented as https://path402.com
Community signal: 1 GitHub stars.
What problem does it solve?
Agent workflows break when pages return payment-required responses and you have no MCP-native way to budget satoshis and complete acquisitions.
Who is it for?
Solo builders shipping agent features that must legally fetch $402-tokenised web content with explicit satoshi budgets.
Skip if: Builders who only need free public URLs, avoid cryptocurrency wallets, or want a non-MCP scraping script.
What do I get? / Deliverables
Once Path402 is registered with API URL, default budget, and wallet WIF, your agent can pull tokenised content through Path402 instead of stopping at gated HTTP responses.
- Registered Path402 MCP tools for discover, acquire, and re-serve against PATH402_API_URL
- Budgeted token acquisitions using PATH402_DEFAULT_BUDGET in satoshis
- Agent-readable content from tokenised web endpoints after on-chain acquisition
Recommended MCP Servers
Journey fit
Skillselion shelves MCP servers where builders first wire them into the stack—during product build—not when the business is only ideating or operating monitors. Path402 is external protocol glue (API URL, satoshi budget, BSV wallet) for agent clients, which matches integrations rather than frontend or pure docs work.
How it compares
MCP micropayment gateway for $402 content, not a generic agent skill or marketplace listing.
Common Questions / FAQ
Who is Path402 for?
Path402 is for solo builders and small teams using Claude Code, Cursor, Codex, or other MCP clients that need agents to access token-gated web content.
When should I use Path402?
Use Path402 when target sites speak the $402 protocol and you want discover, acquire, and re-serve steps inside the agent loop rather than manual browser payment.
How do I add Path402 to my agent?
Add the npm MCP server path402 with stdio transport and set PATH402_API_URL, PATH402_DEFAULT_BUDGET, and the secret PATH402_WALLET_WIF in your host's MCP environment configuration.