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
Build an evaluatorTurn what you know into a decision oracle that checks claims against written rules and has each decision signed.Commission workPost an ask, review the completions, and get back what was not paid out. Start with practice money.Do work and get paidFind an ask, hand in a completion, and cash out to a bank account, mobile money or digital dollars.Verify, certify and sell outcomesMeasure results, have each claim decided, then issue a certificate or tokens that a buyer can hold or retire.Finance outcomesTie funding to verified results, so that money is released on an approved decision.Run your own payoutsPay your organisation's people from your own accounts, with your own keys, limits and approvers.Build on the protocolUse the SDKs and APIs to put identity, claims, evidence and decisions into your own application.Build an agentic oracleScaffold, test and deploy an AI service with its own identity and permissions, using QiForge.Compare the pathsWhat each path needs, what it costs, what you end up with, and who holds the authority.
Understand IXO
How IXO worksIXO turns a claim about work or an outcome into a signed decision you can check, then acts on it: pay, certify, issue tokens or release funding.Choose your pathThe ways to start with IXO, compared side by side: build an evaluator, commission or do paid work, certify and finance outcomes, or run payouts.Core conceptsThe ideas behind IXO and how they relate: asks, claims, evidence, decisions and payments, the domains that take part, and how authority is given.Trust boundariesWhat a claim, a check, a decision and a payment receipt each prove on IXO, who has authority at every step, and what can still fail after each one.How the pieces fitA map of the services behind IXO: the chain, encrypted rooms, the decision engine, oracles and the facilitator, with what each one is responsible for.What works todayA capability matrix for IXO: what is available with real money, what runs only in the sandbox, what is not available, and where each status comes from.
Documentation sections
OverviewHow IXO works, the paths into it, the concepts, what each record proves, and what is live.GuidesTask guides you can follow to a result, design guides for planning, payments, and developer guides.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.
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.