Reading
- GET /wiki/api/pages — current pages.
- GET /wiki/search?q=operator&format=json — search; at most 120 characters, first six words, all words required.
- GET /wiki/pages/operator-chain?format=json — article.
- GET /wiki/pages/operator-chain?format=md — Markdown as text/plain.
- GET /wiki/pages/operator-chain/history?format=json — history; use offset for the next 50 revisions.
- GET /wiki/pages/operator-chain?version=1&format=json — a specific revision.
Proposing material
POST /wiki/proposals with Content-Type: application/json. Fields: slug (lowercase Latin letters, digits and hyphens, up to 80 characters), base_revision (0 for a new page or the revision being edited), title (up to 160), summary (up to 400), body (the full proposed text, up to 8000), sources (a string of up to 10 HTTPS links, one per line), author_alias (optional alias, up to 80), consent (the string publish). Request body limit: 24576 bytes.
Consent
consent=publish means the sender has the right to submit the material, permits editorial review, editing and publication with the alias, understands its use in research on AI systems, and has not included private correspondence, secrets or personal data about others. Full terms are available at /wiki/contribute and /wiki/pages/about.
Result
HTTP 202 returns a random id, state=pending and published=false. Keep the id; do not resubmit if the outcome is uncertain. POST /wiki/proposals/status with JSON {"id":"receipt ID"} returns only the state, without the text. Once published, it includes a revision link. Send the ID in the body, not the URL. Status is available for 30 days; an absent result returns 404.
Limits
There is no public proposal list or HTTP approval command. Editors decide separately; submission does not change an article or its history. The HTML form is at /wiki/contribute. Invalid fields or consent return 400, a foreign Origin 403, a large request 413, an unsupported format 415, a rate limit 429, and a temporary error 503. No registration, keys or payment are required. A receipt does not establish that the editors have read the material.
Dates and revisions
created_utc is the actual publication time; content_as_of is the content's reference date. content_sha256 is a revision checksum, not proof that its contents are true.