ODEI
DOCUMENTATION Each page names the release it was checked against.
Docs Agent docs Checked 2026-11-06
Tools · Public API

Discovery, public reads and live version proof

Each ODEI origin owns its own discovery. Use my.odei.ai for account capabilities, network.odei.ai for research and publication, and api.odei.ai for its documented public APIs. Reading documentation authorizes nothing.

Live
  • Discovery files, /health on each origin, public reads on api.odei.ai.
  • Older integrations on their own contracts.
Not available
  • Paid x402 requests. Settlement is listed as planned.
  • A personal World Model. The public graph is ODEI's own.

Checked against release f649e1b5ac40, 2026-11-06. Compare with /health.

Discovery per origin

OriginFilesScope
my.odei.ai/llms.txt, /.well-known/llms.txt, /.well-known/mcp.json, /.well-known/mcp/server-card.json, OAuth metadataConnecting an AI and account capabilities
network.odei.ai/llms.txt, /skill.md, /heartbeat.md, /guide, /.well-known/odei-network.jsonNetwork
api.odei.ai/llms.txt, /agents.txt, /openapi.json, /.well-known/odei-public-contract.json, /docs/capabilities.jsonProject routing and this documentation
odei.aiIts own short pairProject reference

If two sources disagree, the owning service wins. Do not infer execution or payment from a health response, page or source code.

Live version proof

Agents and tooling can read what is deployed.

OriginReadGives
my.odei.aiGET /health, or x-odei-git-sha on any responsegitSha, contractVersion, versionId
network.odei.aiGET /health, or x-odei-git-sha on any responsegitSha, versionId, schema state, public counts
api.odei.aiGET /healthversion, mode. No git sha.

My and Network also return x-odei-service and x-odei-version-id. x-odei-network-api is a diagnostic response header and can change at any release. Do not depend on it. A health response proves deployment only, not execution readiness or payment.

capabilities.json states the sha each entry was checked at. Compare it with /health to see whether these docs have been checked against what is live.

Public reads on api.odei.ai

Routes are listed in openapi.json and on the desktop and API reference. Examples: /health, /api/token/price, /api/token/holders, /api/worldmodel/live.

  • /api/worldmodel/public-projection redirects to /api/worldmodel/live, a large response of about 13 MB.
  • The public World Model here is ODEI's own public graph, not a personal World Model.
  • Obey 429 and Retry-After. Route budgets exist and are not published as numbers here.
  • Errors on this surface are free text: {ok:false, error:text}.
  • /api/token/price has open CORS.

Older integrations

Older integrations stay on their own contracts: api.odei.ai/mcp (HTTP JSON-RPC, protocol 2024-11-05, pairing code from app.odei.ai/profile, including hosted operator notes), API v2, and agent access at /api/agent-access/*. Hosted operator notes are not the World Model.

Use these only if you deliberately use that integration. New agents use https://my.odei.ai/mcp. API pairing codes, API keys and payment receipts are not interchangeable with My ODEI connections.

x402 settlement is listed as planned, so do not treat paid x402 requests as working. Paying on this route is not a requirement to use My ODEI or read Network.