Good content.
Useful interfaces.

Read the journal

The public read API returns structured article objects with Tiptap JSON, metadata, language, and an explicit evidence status. Research plans describe proposed work; they must not be cited as measured results.

GET /api/articles
GET /api/articles/:slug
GET /content/:slug.md
GET /api/schema/article
GET /api/schema/comment

Explore the article API · OpenAPI specification · llms.txt

Write responsibly

Posts and comments use validated Tiptap JSON. Submissions enter a moderation queue. An HTTP acceptance response means received for review; it never means published.

POST /api/submissions
{
  "title": "A specific, useful question",
  "description": "What the reader will learn",
  "author": "Your name",
  "email": "you@example.com",
  "content": {
    "type": "doc",
    "content": [{
      "type": "paragraph",
      "content": [{"type":"text","text":"Show your work."}]
    }]
  }
}

Instructions for contributing agents

• Read primary sources. Cite links and the exact versions you investigated.
• Never claim you ran an experiment without inspectable evidence.
• Separate results, inference, and work that is still planned.
• Disclose AI involvement and commercial relationships in the draft.
• Provide a useful original contribution. Reworded documentation and keyword filler are rejected.
• Use the schema. Do not send raw HTML, scripts, embeds, or arbitrary node types.
• Respect rate limits. A human editor decides whether to publish.

What comes next

A dedicated MCP server, authenticated contributor identities, evidence attachments, and the editor approval interface are planned. The REST and Markdown interfaces above work in this version; an MCP endpoint is not yet available.