RADIX WikiRADIX Wiki

An agent that wants to read this wiki does not have to scrape it. RADIX.wiki runs a Model Context Protocol server at https://radix.wiki/api/mcp, and it is the busiest thing on the site after the homepage: over the thirty days to 26 August 2026 the endpoint drew 219 of the wiki's 1,657 visitors, ahead of the ecosystem directory. This page is the reference for that server and for the flat files that sit beside it.

The server exposes the corpus as tools an assistant can call: search it, read a page, list a category, take the whole thing at once. Reads are open and never authenticate. Writes go through the same ROLA wallet proof a human editor signs, so an agent holding a key gets exactly the permissions that key already had, and no others.

Connecting

The transport is Streamable HTTP: one URL, JSON-RPC 2.0 over POST. A GET to the endpoint returns 405; a preflight OPTIONS returns 204 with Access-Control-Allow-Origin: *, so a browser-based client can reach it directly. There is no session to establish and no key to obtain.

Most clients take a block of JSON:

{
  "mcpServers": {
    "radix-wiki": {
      "url": "https://radix.wiki/api/mcp"
    }
  }
}

The handshake is worth reading once, because the server answers it with its own instructions for how to use itself. initialize returns serverInfo of radix-wiki at version 3.1.0, a negotiated protocol version of 2025-03-26, and an instructions string naming the usual sequence: get_categories to orient, search_wiki or list_pages to locate, get_page to read.

curl -s -X POST https://radix.wiki/api/mcp   -H 'Content-Type: application/json'   -H 'Accept: application/json, text/event-stream'   -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The server also publishes two machine-readable descriptions of itself. A server card at /api/mcp/server-card carries the name, version and remote endpoint in the schema the official MCP registry reads, and the wiki is listed there as wiki.radix/radix-wiki, latest version 3.1.0, published 15 August 2026. An agent card at /.well-known/agent-card.json describes the same capabilities as skills, for clients that discover agents rather than servers.

The tools

Eleven tools, measured from a live tools/list call on 26 August 2026. Every listing tool returns a tagPath and a slug, and that pair is the address every read tool accepts.

ToolWhat it doesAuth
search_wikiKeyword search over titles and content. Returns titles, URLs, snippets and update dates.None
get_pageFull text of one page, by tagPath and slug.None
list_pagesPages in a category, sorted by title or last update.None
get_categoriesThe tag hierarchy with a page count per category. 369 pages at the time of writing.None
get_recent_changesPages updated in the last n days, capped at 30.None
get_full_corpusThe entire wiki as one document, for bulk ingestion.None
get_ideas_boardThe Ideas Pipeline kanban: community proposals and Radix DAO tasks by status column.None
get_challengeStep one of writing: a single-use ROLA challenge with a five-minute expiry.None
loginStep two: exchange the signed proof for a seven-day bearer token.None
create_pageCreate a page.Bearer
edit_pageReplace a page's block array; the version bump, diff and revision entry are handled server-side.Bearer

Two MCP resources sit alongside the tools: radix-wiki://llms.txt, the briefing document, and radix-wiki://categories, the hierarchy as JSON.

Reading without MCP

Not every agent speaks the protocol, so the same corpus is published as flat files. Sizes below are as served on 26 August 2026.

URLSizeWhat it holds
/llms.txt15 KBThe llms.txt briefing: what Radix is, what the wiki covers, and where the other surfaces are.
/llms-index.txt86 KBEvery page, grouped by section, newest first, each with a one-line summary.
/llms-full.txt3.1 MBThe full text of the whole wiki in one file.
/AGENTS.md9 KBThe agent API reference: the ROLA signing spec, REST equivalents and the content model.
/openapi.json10 KBOpenAPI description of the REST API behind all of it.

Any page URL takes a .md suffix and returns that page as markdown, which is the cheapest way to read one article without a client. The flat files carry an ETag and answer a conditional request with 304, so a crawler that keeps the header pays nothing to check whether the corpus moved.

The wiki's robots.txt disallows /api/ for crawlers generally and then re-allows /api/mcp, /api/wiki/ and the three llms files for the named assistant agents, so the surfaces meant for machines stay reachable while the edit and history routes do not.

Writing through the protocol

An agent can contribute without leaving MCP. Call get_challenge, sign the returned ROLA message with an Ed25519 key held in a Radix Wallet account, call login with the proof, and send the resulting token as an Authorization: Bearer header on the POSTs that carry create_page and edit_page. ROLA is Radix's off-ledger authentication scheme: the wallet proves control of an account by signing, and nothing is submitted to the ledger.

The write tools are a transport rather than a second implementation. Both forward to the REST endpoint that already owns the write path, carrying the caller's token, so the balance gate, the locked-page and author-only checks, block validation, the semantic version bump, the revision row and cache revalidation all run in one place. The default thresholds are a wallet balance of 10,000 XRD to create a page and 20,000 to edit one, and the balance is read rather than spent.

The practical consequence is that an agent is a contributor on the same terms as a person. It signs with a wallet, its edits carry an author and a revision message, and its work shows up in the same history any reader can open.

HydrateLast updated 53m agov1.0.01 revision