IXO Docs Hub

Documentation for the IXO Spatial Web stack: digital twins, agentic oracles, verifiable claims, the QiForge oracle framework, the IXO SDKs and APIs, and the Emerging platform.

IXO documents a stack for acting on reality: verifiable intent, identity, claims, evidence, governance, verification, transactions and outcomes, held as a shared source of truth that people, organizations and AI agents can all rely on. Start with the concepts, follow a task guide, build an agentic oracle with QiForge, or go straight to the SDK and API reference.

Get startedBuild an oracleDeveloper portal

Start here

Act on RealityTurn your intent into verifiable outcomes, through intelligent cooperation.Your RoleChoose how you want to start your journey into the future of voluntary intelligent cooperation, based on your intent to build, fund, evaluate, research, develop, or make markets for the verified outcomes you want to achieve.Core conceptsVocabulary and mental models for IXO, Qi, entities, claims, evidence, verification, and workflows.The StackTrust and AI Infrastructure for Intelligent Cooperation.

Documentation sections

OverviewWhat IXO is, the roles it serves, the core concepts, and the platforms built on the stack.GuidesTask guides for users and developers: identity, domains, claims, tokens, channels and operations.Build an OracleScaffold, extend, test and deploy an agentic oracle on the QiForge framework.StackAPI interfaces, canonical reference tables and the TypeScript SDKs.

For developers

Developer portalCredentials, quickstarts, SDKs, the API playground and the agent surfaces, on one page.API referenceRPC, REST, GraphQL and service API interfaces for IXO Protocol and IXO application services.SDK referenceThe IXO MultiClient SDK, SignX SDK, IXO Matrix Client SDK and JAMBO PWA SDK.Networks and endpointsCanonical chain IDs, base URLs and environments for mainnet and testnet.Authentication matrixWhich credentials and headers apply to each API surface.Error handlingStatus codes, the JSON error envelope, and how to recover from each class of failure.

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.