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 agents use it. Over the thirty days to 20 September 2026, counting only callers outside this wiki's own conformance suite and the tooling that maintains it, the endpoint took 518 tool calls, get_categories most often at 83, and get_challenge, the first step of the write handshake, 35 times. 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 one page or twenty, list a category, follow a page's history, take the whole thing at once, and read Radix mainnet's daily activity. 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 4.0.0, the protocol version the client asked for (a request for 2025-03-26 is answered with 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 4.0.0, published 21 October 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

Seventeen tools, measured from a live tools/list call on 23 October 2026. Every listing tool returns each page's path, its tag path and slug joined, and that path is the address every read tool accepts.

ToolWhat it doesAuth
search_wikiKeyword search over titles and body text, ranked with title matches first, then literal body matches, then full-text matches. Not semantic, so one distinctive word beats a sentence.None
get_pageOne page in full, by path or by tagPath and slug. With blocks: true it returns the stored block array an edit starts from.None
get_pagesOne to twenty pages in a single call, for reading search or listing results.None
list_pagesEvery page under a tag path, newest first or A to Z, 20 to a page and up to 100.None
get_categoriesThe tag hierarchy with a page count per category. 381 pages on 23 October 2026.None
get_recent_changesPages edited in the last n days, 7 by default and up to 30.None
get_full_corpusThe entire wiki as one document, for bulk ingestion, with a size-only preflight and page-aligned paging for a client that cannot take it at once.None
get_page_historyA page's revisions, newest first, each with its message and the blocks it changed.None
get_ideas_boardThe Ideas Pipeline kanban: community proposals and Radix DAO tasks by status column.None
get_network_activityRadix mainnet activity by UTC day since Babylon went live on 28 September 2023: transactions, active and new accounts, fees and $XRD burned. The same rows chart at /charts.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, starting from the version the caller read; an edit made after someone else's is refused rather than written over it. The version bump, diff and revision entry are handled server-side.Bearer
restore_revisionMake an earlier revision the current page, written as a new revision.Bearer
delete_pageDelete an article with its history and comments. Its author may; on the Ideas board, so may anyone who can edit it.Bearer
upload_imageUpload a JPEG, PNG, GIF, WebP or AVIF image of up to 3.4 MB and get back the URL to place in a page. The wiki stores it as WebP.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 wiki also publishes flat files. Sizes below are as served on 23 October 2026.

URLSizeWhat it holds
/llms.txt16 KBThe llms.txt briefing: what Radix is, what the wiki covers, and where the other surfaces are.
/AGENTS.md9 KBThe agent API reference: the ROLA signing spec, REST equivalents and the content model.
/openapi.json15 KBOpenAPI description of the REST API behind all of it.

Two more files sat here until 21 October 2026: /llms-index.txt, every page with a one-line summary, and /llms-full.txt, the whole wiki in one 3.5 MB file. Both now answer 404. The change that removed them records that in their sixteen days crawlers read them a handful of times and read the per-page markdown instead, so llms.txt is the only index and get_full_corpus carries the full text for a client that wants it in one piece.

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/ and then re-allows /api/mcp, /api/wiki/, /llms.txt, /openapi.json and /.well-known/, for every crawler and again for each named assistant agent, 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 the five write tools. 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. Each forwards to the REST endpoint that already owns that write, 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. A wallet needs 10,000 $XRD to create a page (20,000 in the ecosystem section, 50,000 on the blog) and 20,000 $XRD to edit one (10,000 on the Ideas board), and the balance is read rather than spent.

An agent is therefore 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 1d agov1.3.07 revisionsVerified Oct 9, 2026
CiteRADIX Wiki. "RADIX.wiki MCP Server." October 23, 2026. https://radix.wiki/contents/resources/mcp-server