Give every model the same grounded world.

Compile knowledge once, then reach it live over MCP and the API, or take it away as a signed portable package. The model is replaceable. The compiled knowledge is the asset.

Three ways to use a Compiled World

From sources to a grounded answer

1. Compile and activate a WorldUpload or connect sources, review the candidate, and activate it. Activation is a human decision, and nothing is served from a candidate.
2. Create accessMint a scoped API key, or point an agent at the MCP server. Creating, rotating and revoking a key each write an audit row.
3. Query the active WorldSearch, read objects and relations, or ask a question against the revision that is live right now.
4. Receive evidence-bound contextEvery result carries the source version and the exact location inside it that it was compiled from.
5. Follow citations back to sourceOpen that location and read the original. Where the evidence does not support an answer, the answer says so.

A finished Compiled World is open to read in full today, with its evidence attached. Compiling your own sources is set up with us rather than enabled by a plan purchase.Explore a Compiled WorldDiscuss your sources

• The endpoint reference, the error catalogue and the package format are in the documentation.
• If you are deciding between live MCP/API access and a portable package, start with Use your results with AI.
• Current availability is on the status page.

# Every readable format, with its tier and its stated limitations. No key.
curl -fsS https://tavonel.com/api/v1/capabilities | jq '{schemaVersion, entries: (.entries | length), contentSha256}'

# The pin a caller keeps: drop contentSha256 -- it is the last key -- and re-serialize.
curl -fsS https://tavonel.com/api/v1/capabilities \
  | jq -S 'del(.contentSha256)' --indent 0 | tr -d '\n' | sha256sum

# The contract, and the two paths it deliberately does not have.
curl -fsS https://tavonel.com/api/openapi | jq '[.paths | keys[] | select(test("promote|rollback"))]'
# []

# Who signs an export here, or the refusal that says nobody does.
curl -fsS https://tavonel.com/api/export/trust | jq '{activeKeyId, keys: [.keys[] | {keyId, status, publicKeySpkiSha256}]}'

curl -fsSO https://tavonel.com/developer/tavonel-public-sample.py
python tavonel-public-sample.py --base-url https://tavonel.com
# sample: 3 objects, 2 evidence records, ... bytes
# digest: sha-256=:...:
#   ev-01 -> src_v_01 page 4 bbox [118, 214, 886, 374]
#   ev-02 -> src_v_01 page 4 bbox [118, 214, 886, 374]
# PUBLIC SAMPLE OK

curl -H "Authorization: Bearer $TAVONEL_API_KEY" \
  https://tavonel.com/api/v1/documents

const response = await fetch("https://tavonel.com/api/v1/documents", {
  headers: { Authorization: `Bearer ${process.env.TAVONEL_API_KEY}` },
});
if (!response.ok) {
  const { code } = await response.json();
  throw new Error(`tavonel_read_refused: ${code}`);
}

const { workspaceId, documents } = await response.json();
for (const document of documents) {
  console.log(workspaceId, document.documentId, document.state, document.sourceVersionKey);
}

import json
import os
import urllib.request

request = urllib.request.Request(
    "https://tavonel.com/api/v1/documents",
    headers={"Authorization": f"Bearer {os.environ['TAVONEL_API_KEY']}"},
)
with urllib.request.urlopen(request) as response:
    body = json.load(response)

for document in body["documents"]:
    print(body["workspaceId"], document["documentId"], document["state"], document["sourceVersionKey"])

{
  "mcpServers": {
    "tavonel": {
      "command": "node",
      "args": ["/absolute/path/to/tavonel-mcp.mjs"],
      "env": {
        "TAVONEL_API_KEY": "tvnl_live_...",
        "TAVONEL_BASE_URL": "https://tavonel.com"
      }
    }
  }
}

Next