Developer portal

You are wiring real-world workflows where agents and services act on verifiable entities, claims, and evidence — not only on generic LLM context.

IXO anchors what is true on-chain and in linked services: domains, claims, credentials. Qi, the Qi Intelligent Cooperating System, is where people and agents cooperate on that truth, through IXO Matrix, oracle and agent services, and automation. Most projects implement state first — protocol, claims, indexing — then add cooperation: Matrix, Agentic Oracles, SDKs.

This page is a map. Every card links to the canonical page for that topic; nothing here is restated from it.

Start building

Build an oracle

Scaffold a QiForge oracle, boot it, and watch the agent call a plugin tool — about ten minutes.

What you can build

The build tracks available on the stack, and which one fits your problem.

Implementation examples

Worked end-to-end TypeScript for the IXO MultiClient SDK and IXO Matrix Client SDK.

Workflows

The common build sequences: register a domain, collect claims, evaluate, settle.

Credentials and access

API credentials differ by surface — protocol gateways, service APIs, and platform APIs do not share one scheme. Confirm the literals for the interface you are calling before you write the request.

Authentication matrix

The canonical table: which credential and header applies to each API surface.

Authentication guide

Set up credentials, session keys, and authorization for IXO services.

Networks and endpoints

Chain IDs, base URLs, and environments for mainnet and testnet.

Emerging Platform API keys

How Emerging Platform keys are issued and scoped, and where they are managed.

Warning

Keep credentials in secure runtime storage, never in source files, and rotate them according to your operator policy.

Sandbox

The Emerging Platform API ships with a live console on every endpoint page. Set a bearer token, fill the typed parameters, and send a real request against the development server — no local setup, no CORS workarounds.

Try an endpoint

GET /households/stats with the request console attached.

Test your oracle

Run an oracle locally and exercise its plugins before deploying.

Build specific capabilities

Digital twins

Create and manage entity domains for real-world systems, assets, and organisations.

Claims and verification

Submit and verify impact claims with evidence using IXO Protocol claims modules.

Digital MRV

Set up digital measurement, reporting, and verification workflows.

Agentic Oracles

Build AI-powered oracle services for verification, evaluation, and automation.

Domain settings

Configure entity domain permissions, services, and linked resources.

Model Context Protocol

Connect AI tools to IXO services through MCP servers.

Interfaces

API reference

RPC, REST, GraphQL, and service API interfaces for IXO Protocol and IXO application services.

SDK reference

IXO MultiClient SDK, SignX SDK, IXO Matrix Client SDK, and JAMBO PWA SDK.

Error handling

Status codes, the JSON error envelope, and how to recover from each class of failure.

Pagination

Cursor and page patterns for large result sets.

Product and SDK map

The canonical list of products, SDKs, and their package identifiers.

Glossary

Canonical terms used across the protocol, products, and SDKs.

Concepts worth reading first

Core concepts

Vocabulary and mental models for IXO, Qi, entities, claims, evidence, verification, and workflows.

IXO Protocol

The Cosmos SDK blockchain: entity management, claims, tokens, bonds, and smart accounts.

IXO Matrix

The encrypted data and communication layer behind data rooms, evidence storage, and messaging.

Qi and Agentic Oracles

Human–agent cooperation, oracles, and agent tooling over verified workflows.

Build with AI agents

These docs are published for machines as well as people. Nothing here needs scraping.

Surface	URL	What it is
Markdown mirror	`<page-url>.md`	Any page as Markdown. Also served on `Accept: text/markdown`.
Page index	`/llms.txt`	Every navigation page with its description.
Full corpus	`/llms-full.txt`	The whole documentation set in one request.
MCP server	`/mcp`	Streamable HTTP JSON-RPC with `search_docs` and `read_page`.
MCP server card	`/.well-known/mcp.json`	Transport, capabilities, and tool schemas, readable before connecting.
OpenAPI	`/openapi.json`, `/openapi.yaml`	The Emerging Platform API, with an operation ID and typed schema per endpoint.
Sitemap	`/sitemap.xml`	Every canonical URL.

For AI agents

A single dense page an agent can scaffold a QiForge oracle from — every signature, option, and env var.

MCP servers

The MCP servers in the IXO ecosystem, including this documentation server.

Unknown paths on this site return a real HTTP 404 with a Markdown body listing these surfaces, so an agent that guesses wrong can recover in one request.

Support

Ask the docs assistant

The Ask Assistant control in the header answers from these docs, grounded in the page you are reading.

Developer community

Questions, discussions, and support on Slack.

assistant@ixo.world

Open-source repositories

Source code for the SDKs, gateway tools, and reference implementations.