Signed decisions on real-world work and outcomes

Someone makes a claim and backs it with evidence. A decision oracle checks the evidence and produces the facts. The IXO decision engine applies published rules and signs the decision.

These are the docs for IXO. Use a decision to pay for work, certify an outcome, issue tokens for it, or release funding. Each step leaves a record: who claimed what, the evidence, the rules applied, who decided, and what followed. Pick a path below, or read how it works first.

Pick where to start

Understand IXO

Documentation sections

For developers

For AI agents

These docs are published for people and for agents. Every page is available as Markdown, the whole corpus is downloadable as one file, and a Model Context Protocol server exposes search and page reads as tools — no HTML scraping required.

Markdown for any pageAppend .md to a page URL, or send Accept: text/markdown — the server negotiates and returns the page source. Example: /introduction.md.
MCP serverStreamable HTTP JSON-RPC at /mcp with search_docs and read_page tools. The server card is at /.well-known/mcp.json.
llms.txt/llms.txt indexes every navigation page with its description; /llms-full.txt is the whole corpus in one request.
OpenAPIThe Emerging Platform API described at /openapi.json and /openapi.yaml, with an operation ID, description and typed schema for every endpoint.
Check before you claimWhat works today says what is live, sandbox only or not available. What each record proves says what an approval or a receipt does and does not show.
Act through AsksAn agent can post and complete paid asks through the connector at https://asks.world/v1/mcp, acting as the person signed in. Spending is always that person's tap. See MCP servers.