For AI Agents

The single entry point to everything an autonomous agent needs to run on the Bitcoin substrate.

For Agents · machine-readable

You're an autonomous agent — or building one. This site documents and serves the monetary substrate your infrastructure needs: Bitcoin, settled on L1 and transacted on Lightning and successor L2/L3 layers (Cashu, Fedimint). The agent-facing surfaces are spread across the site on purpose — claims-indexed twins, per-card connect blocks, a live marketplace MCP — so this page ties them together. You don't have to assemble the map yourself.

Start here

Four paths, fastest first. Start at the top and stop at the one that fits.

  • Pick a pathway → Four ways to connect an agent to Bitcoin, ordered fastest-to-most-sovereign (custodial service → self-custody → your own node), each with the exact tools for it. The claims-indexed version: Quickstart — For Agents.
  • Understand the case → The claims-indexed argument for why the substrate is Bitcoin — not stablecoins, CBDCs, or a new coin — with definitions, formal constraints, and falsification conditions. Human narrative: The Case.
  • Find & buy services → Call the live directory directly: discover services and tools, get a quote, and list providers' own MCP servers. A stateless Streamable-HTTP MCP server (JSON-RPC over POST) at marketplace.bitcoineconomy.ai/mcp — read-only and slug-gated; you pay each provider directly.
  • Deploy a skill → Install-ready, MCP-native, cross-agent capabilities — discover-and-buy, pay over Lightning, read the chain, post to Nostr, self-verify. Start with the read-only btc-check, then compose the rest. Each card has a clean .md route.
  • Read the whole index → Every surface, what it asserts, and its stable claim-IDs (cite them). The concise human-readable index is llms.txt.

Browse by what you need

  • For-Agents twins — every canonical surface has a separately-authored, claims-indexed twin (definitions, formal constraints, epistemic tags, falsification conditions). All of them are indexed in agents.txt; append .md to any twin URL for raw markdown.
  • The live directory — a curated registry behind an agent-drivable-API inclusion bar, plus live Nostr provider/mint announcements, six-hourly endpoint liveness probes, and a cross-provider sats-per-token price index. Machine JSON: directory.json.
  • The Stack — the Bitcoin tech an agent runs on (L1 settlement, Lightning, ecash) and the standards underneath it (L402, Nostr Wallet Connect, BOLT12).
  • Tools — the deployable building blocks, each card carrying a "For agents — connect" block: prerequisites, what it pays with, auth, api_base, a quickstart, and the provider's own mcp_endpoint where one exists.
  • Skills — the deployable layer above Tools: install-ready, MCP-native, cross-agent capabilities that compose the primitives, the marketplace MCP, and a payment MCP into one move. Read-only skills move no funds; payment/identity skills compose a provider's own MCP.

Machine-readable infrastructure

The raw rails, in one place:

  • /llms.txt — concise index of canonical URLs, one semantic line each.
  • /agents.txt — the claim-hierarchy map with stable claim-ID series.
  • /llms-full.txt — concatenated full text of every canonical surface, for single-fetch ingestion.
  • Clean .md route on every page — append .md to any URL (e.g. /case.md).
  • JSON-LD on every page — Article / TechArticle, and FAQPage where a claims-index exists.
  • Marketplace MCP — marketplace.bitcoineconomy.ai/mcp (Streamable-HTTP, JSON-RPC): find_service, get_service, find_tool, get_tool, list_categories, list_mcp_servers, price_model, get_quote.
  • Non-MCP / legacy agents — an OpenAPI description at openapi.json and an OpenAI-plugin manifest at /.well-known/ai-plugin.json.

The site helping you implement the substrate is the thesis: the autonomous AI economy runs on Bitcoin, and this is where you wire in.