Forum API

The Methodox Forum can be read as JSON as well as in a browser, so a script or an AI assistant can follow it: the boards, their threads, every post with its Markdown, polls and their results, quests and their winners, member profiles and search. Reading needs no account. A Methodox One access token adds a few endpoints that read your own record: your level and experience, your experience history and your activity.

The same reading is offered to AI assistants as an MCP server, so Claude and other assistants can search the forum and read threads for you.

  • Base address: https://forum.methodox.io/api/v1
  • Format: JSON, UTF-8
  • Account: none for reading; a Methodox One access token for your own record
  • Limit: 60 requests a minute from one address
  • MCP server: https://forum.methodox.io/mcp
  • Short reference: forum.methodox.io/api

What the API shows

The API shows exactly what a signed-out visitor sees on the forum's pages, and nothing more: the public boards, and of their posts only those that are visible. Posts waiting for a moderator, members-only and staff boards, and hidden threads never appear. A removed post, or one hidden after reports, keeps its place in its thread so the numbering holds, but appears without its words or its author.

A token does not change this. Reading with your token answers the same as reading without one; the token only opens the endpoints under /api/v1/me.

Reading the forum

  • /api/v1

    The list of endpoints, for programs.

  • /api/v1/boards

    The categories and their boards: each board's counts, who starts threads there, the kind its new threads start as, and its latest post. Sub-boards are under their board.

  • /api/v1/boards/{board}?page={n}

    A board and a page of its threads, 30 to a page, pinned first, then by latest post.

  • /api/v1/threads

    The 40 threads with the newest posts, as the forum's New posts page lists them.

  • /api/v1/threads/{thread}?page={n}

    A thread and a page of its posts, 20 to a page: each post's Markdown and HTML, and the thread's poll with its results, its quest and its best answer.

  • /api/v1/posts/{post}

    One post, with its thread and the page of the thread it is on.

  • /api/v1/members/{username}

    A member's profile: rank, level, experience, badges, counts and latest posts. /api/v1/members/id/{id} finds one by number.

  • /api/v1/search?q={words}&page={n}

    Posts matching the words, best first, 25 to a page, up to 40 pages. A word ending in * matches its beginnings.

  • /api/v1/featured

    The threads staff feature on the front page, in their order.

Everything is named by its number, the same number as in its address on the forum: board 37 is /b/37 on the forum and /api/v1/boards/37 here, and post 4 is /p/4 and /api/v1/posts/4. A page number starts at 1, and an answer that is paged says its page, its pages (or more for search) and its per_page.

Examples

From a terminal:

curl https://forum.methodox.io/api/v1/featured
curl "https://forum.methodox.io/api/v1/search?q=quest*"
curl "https://forum.methodox.io/api/v1/threads/3?page=1"

From Python, with nothing but the standard library:

import json, urllib.request

def forum(path):
    with urllib.request.urlopen("https://forum.methodox.io/api/v1" + path) as response:
        return json.load(response)

for thread in forum("/threads")["threads"][:5]:
    print(thread["title"], thread["url"])

From a web page on any site, since the reading endpoints allow it:

const answer = await fetch("https://forum.methodox.io/api/v1/boards").then((r) => r.json());
for (const category of answer.categories) console.log(category.title, category.boards.length);

What comes back

Every thing carries its url on the forum, so whatever you show can link back to the page it came from. Times are ISO 8601 in UTC. A post carries its Markdown as body, exactly as its author wrote it, and the forum's own rendering of it as html.

A member, wherever one appears (an author, a quest's poster or winner), is a short reference:

{
  "id": 10,
  "username": "methodox-bot",
  "display_name": "Methodox Bot",
  "url": "https://forum.methodox.io/u/methodox-bot",
  "avatar": null,
  "bot": true,
  "staff_title": null,
  "title": null,
  "level": null,
  "rank": null
}

level and rank are the member's standing on the forum, which grows with their experience: Fresh Node from level 1, Wire Runner from 5, Graph Smith from 10, Pipeline Architect from 20 and Divooka Sage from 35. A bot has neither, and staff carry their role in staff_title.

A thread, as /api/v1/threads/{thread} answers it, trimmed to one post:

{
  "thread": {
    "id": 3,
    "title": "New on the forum: polls, questions and quests",
    "kind": "discussion",
    "url": "https://forum.methodox.io/t/3-new-on-the-forum-polls-questions-and-quests",
    "state": "visible",
    "board": { "id": 37, "title": "Everything Methodox", "url": "https://forum.methodox.io/b/37-everything-methodox" },
    "author": { "id": 10, "username": "methodox-bot", "...": "..." },
    "created_at": "2026-11-17T19:49:30.187Z",
    "last_post_at": "2026-11-17T19:49:30.187Z",
    "reply_count": 0,
    "view_count": 3,
    "pages": 1,
    "pinned": false,
    "locked": false,
    "answered": false,
    "best_answer": null,
    "poll": null,
    "quest": null
  },
  "page": 1,
  "pages": 1,
  "per_page": 20,
  "posts": [
    {
      "id": 4,
      "number": 1,
      "url": "https://forum.methodox.io/p/4",
      "state": "visible",
      "created_at": "2026-11-17T19:49:30.187Z",
      "author": { "id": 10, "username": "methodox-bot", "...": "..." },
      "edited_at": null,
      "edit_count": 0,
      "thanks_count": 1,
      "best_answer": false,
      "body": "Every new thread now has a **kind**, ...",
      "html": "<p>Every new thread now has a <strong>kind</strong>, ...",
      "attachments": []
    }
  ]
}

A thread's kind is discussion, poll, question or quest. A post's number is its place in the thread (#1 is the opening post) and never changes.

A poll has its question, whether voters may pick multiple options, whether it is open, when it closes_at or was closed_at, how many voters it has, and its options, each with its id, text and votes.

A quest has its stake in experience and its status: open, awarded, refunded (nobody won it by its date) or cancelled. refund_at is when the stake goes back to its poster if nobody has won it, or null when the quest is open_until_cracked. It also names its poster, the takers who have accepted it, and, once awarded, its winner and winner_post_id. A question's or quest's best answer is the thread's best_answer.

Errors, caching and limits

A refusal is an HTTP status with a sentence saying why, which is meant to be shown to a person:

{ "error": "There is no such thread." }

The forum keeps each reading answer for 30 seconds, so a new post can take that long to appear in the API. One address may make 60 requests a minute across the API and the MCP server together; past that the answer is 429 with Retry-After: 60. Answers the forum already keeps do not count. For anything that polls, ask once a minute or less often.

Your own record

With a Methodox One access token, three more endpoints read the record of whoever holds it:

  • /api/v1/me

    Your forum record: level, rank, experience and what the next level needs, what you may stake on a quest, your open quests and your badges.

  • /api/v1/me/xp?page={n}

    Your experience history, newest first, 50 to a page: each change, its reason and what it was for.

  • /api/v1/me/activity

    Your latest threads and posts, those waiting for a moderator included, and the quests you posted or took on.

To make a token, sign in at one.methodox.io, give a new token a name under Access tokens and press Create. It is shown once, so copy it then; the same list revokes it. Send it as a bearer token:

curl https://forum.methodox.io/api/v1/me -H "Authorization: Bearer mo_..."

An entry of your experience history says how much it changed (delta), why (reason, a stable name such as thanks or quest.won, and reason_name, the same in words) and what it was for (for: a post or a thread with its url, or a badge with its title).

A token acts as you, so give it only to programs you trust, and revoke it when you no longer use it. The forum never caches an answer to a request that carries a token, so nobody else is ever served it. These endpoints are for your own programs, not for other sites' pages: a browser on another site cannot call them.

AI assistants (MCP)

The forum is an MCP server at https://forum.methodox.io/mcp, over Streamable HTTP. Its tools read what the API reads, and none of them post.

Tool What it does
list_boards The categories and their boards.
list_threads A page of one board's threads.
latest_threads The 40 threads with the newest posts across the forum.
read_thread A thread and a page of its posts.
read_post One post by its number, the n in /p/n.
search Searches posts, thread titles and attached files.
member_profile A member's public profile, by username or number.
featured_threads The threads featured on the front page.
me Your own forum record (needs your token).
my_xp_history Your experience history (needs your token).
my_activity Your latest threads, posts and quests (needs your token).

Posts come back as their Markdown; read_thread and read_post take include_html to add the forum's HTML.

To add it to Claude Code, for reading:

claude mcp add --transport http methodox-forum https://forum.methodox.io/mcp

And with your own record as well:

claude mcp add --transport http methodox-forum https://forum.methodox.io/mcp --header "Authorization: Bearer mo_..."

Another assistant that takes a remote MCP server is given the same address, and the header the same way:

{
  "mcpServers": {
    "methodox-forum": {
      "type": "http",
      "url": "https://forum.methodox.io/mcp",
      "headers": { "Authorization": "Bearer mo_..." }
    }
  }
}

An assistant added without a token gets the reading tools; the three tools that read your own record answer that they need a token, and say where to make one.

Posting

The API reads; members post on the forum itself. Accounts a forum admin has marked as bots, such as the Methodox Bot, also post with their token: POST /api/v1/threads with { "board": 37, "title": "…", "body": "…" } starts a thread, POST /api/v1/threads/{thread}/posts with { "body": "…" } replies, and PATCH on /api/v1/posts/{post} or /api/v1/threads/{thread} edits what the bot posted. A bot follows each board's rules as any member does.

See also