This is the entry point for building on IXO: creating domains, submitting and deciding claims, issuing credentials, taking payment, and running AI services with their own identity.
Most projects build in two stages. First the records: entities, claims and credentials on the IXO Protocol, with IXO Blocksync to query them. Then the cooperation around them: IXO Matrix rooms, oracles and agents. Build against a test network, and check What works today before you depend on a feature.
This page is a map. Every card links to the page that owns its topic, and nothing here is restated from it.
Start building
Scaffold a QiForge oracle, boot it, and watch the agent call a plugin tool, in about ten minutes.
Build a decision oracleA service that checks claims against a rubric and signs each decision, with unit tests and a dry run.
SDK patternsIllustrative TypeScript for the IXO MultiClient SDK and IXO Matrix Client SDK. Adapt it and build against a test network.
WorkflowsThe common message sequences: create an entity, submit a claim, record an evaluation, mint tokens.
Credentials and access
API credentials differ by interface. 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.
The table of which credential and header applies to each API.
Authentication guideSet up credentials, session keys, and authorization for IXO services.
Networks and endpointsChain ids and the host of each service on mainnet, testnet and devnet.
Emerging Platform API keysHow Emerging Platform keys are issued and scoped, and where they are managed.
Keep credentials in secure runtime storage, never in source files, and rotate them according to your operator policy.
Sandbox
Every endpoint page of the Emerging Platform API has a request console. Set a bearer token, fill in the typed parameters, and send a real request to the development server, with no local setup and no CORS workarounds.
GET /households/stats with the request console attached.
Run an oracle locally and exercise its plugins before deploying.
Build specific capabilities
Create and manage domains for real-world systems, assets and organisations.
Claims and verificationSubmit and verify claims with evidence using the IXO Protocol Claims module.
Claim disputesChallenge a claim's submitter or evaluator, and how adjudicators decide.
Digital MRVSet up digital measurement, reporting, and verification workflows.
Agentic OraclesBuild AI oracle services for verification, evaluation and automation.
Decision oracleJudge claims with @ixo/decision-oracle on a Cloudflare Worker.
Charge per decision in PAY, USDC on Base or card, and host your own payouts facilitator.
Domain settingsConfigure a domain's permissions, services and linked resources.
IXO CredentialsIssue, hold, share and revoke SD-JWT verifiable credentials over OpenID4VCI and OpenID4VP, on devnet, testnet and mainnet.
Model Context ProtocolConnect AI tools to IXO services through MCP servers.
Interfaces
RPC, REST, GraphQL, and service API interfaces for IXO Protocol and IXO application services.
SDK referenceIXO MultiClient SDK, IXO SignX SDK, IXO Matrix Client SDK and JAMBO PWA SDK.
ErrorsStatus codes, the JSON error envelope, and how to recover from each class of failure.
PaginationCursor and page patterns for large result sets.
Product and SDK mapThe list of products, SDKs and their package identifiers.
GlossaryOne definition for each term used across the protocol, products and SDKs.
Concepts worth reading first
The vocabulary of IXO: domains, claims, evidence, decisions and who takes part.
IXO ProtocolThe Cosmos SDK blockchain: entity management, claims, tokens, bonds, and smart accounts.
IXO MatrixThe encrypted data and communication layer behind data rooms, evidence storage, and messaging.
Qi and Agentic OraclesCooperation between people and agents, oracles, and agent tooling.
Build with AI agents
These docs are published for machines as well as people. Nothing here needs scraping.
Read these docs
| Resource | 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. |
Act through IXO
An agent can also do things on IXO for the person it acts for. Money always needs that person: an agent prepares a post or a payment, and the person confirms it.
| Server | Endpoint | What an agent can do |
|---|---|---|
| Asks | https://asks.world/v1/mcp | Post asks, find paid work and hand in completions, with real money. |
| Asks sandbox | https://test.asks.world/v1/mcp | The same, with practice money. Start here. |
| A decision oracle | /v1/mcp on the oracle's host | Submit claims and read decisions, when the operator has turned the API lane on. |
Before an agent answers or acts
Three pages keep an agent from saying more than is true:
- What works today says what is live, what runs only in the sandbox, and what is not available.
- What each record proves says what an approval, a decision and a receipt do and do not show.
- The Glossary defines each term once.
/llms.txt names these pages at the top, and the documentation MCP server names them in its instructions.
Every server an agent can connect to, the limits on what it may do, and the plugins for Claude Code and Codex.
For AI agents building an oracleA single dense page an agent can scaffold a QiForge oracle from, with every signature, option and env var.
Unknown paths on this site return a real HTTP 404 with a Markdown body listing these files and servers, so an agent that guesses wrong can recover in one request.
Support
The Ask Assistant control in the header answers from these docs, starting from the page you are reading.
Questions, discussions, and support on Slack.
(opens in a new tab)Email(opens in a new tab)Open-source repositoriesSource code for the public SDKs, gateway tools and reference implementations.
(opens in a new tab)