Everything on IXO starts from a signed decision about a claim. People come to it for different reasons: to make those decisions, to pay for work on the strength of them, or to certify, sell and finance the outcomes they confirm. This page compares the paths, so you can pick one and go straight to its guide. Each section says what is available now, what you need, what it costs, what you end up with, what to do when it goes wrong, and who holds the authority.
| I want to | Start here | Needs code |
|---|---|---|
| Turn what I know into a service that checks claims | Build an evaluator | Some |
| Get a piece of work done and pay only for accepted results | Commission work | No |
| Do work and be paid for it | Do work and get paid | No |
| Measure results, then certify and sell them | Verify, certify and sell outcomes | Yes |
| Tie funding to verified results | Finance outcomes | Yes |
| Pay my organisation's people from our own accounts | Run your own payouts | Command line |
| Put identity, claims and decisions into my own application | Build on the protocol | Yes |
Whichever you pick, try it with practice money first. What works today lists what is live and what is not.
Build an evaluator
You write the rules for judging a type of work, and run a service that checks each claim against them and signs its decisions. Posters can pick it as their verifier.
| Available now | Yes. The @ixo/decision-oracle package runs on devnet, testnet and mainnet. |
| You need | Knowledge of the work being judged. To build, a free Cloudflare account. An AI assistant can do most of the setup with you. |
| Cost | The decision engine bills each decision to the account that registered the oracle. AI checks spend model tokens. You can charge a fee for each decision. |
| You end with | A deployed oracle that passes its tests, is hired by a claim collection, and records signed decisions. |
| If it goes wrong | A dry run previews a decision with nothing saved and nothing billed. If the engine cannot match your rubric to the claim form, it stops there. Fix the rubric before sending claims. |
| Who has authority | Whoever commissions the work owns the rules. Your oracle produces facts. The decision engine decides. A collection's owner must grant your oracle the right to record decisions. |
Plan the rules, facts, review tasks and tests on paper, then follow the build guide.
Commission work
You post an ask, people and agents complete it, a verifier checks each completion, and you pay for the ones that are approved.
| Available now | Yes, on asks.world, and with practice money in the sandbox. |
| You need | A Google account, and a browser or an AI assistant. |
| Cost | The payment for each completion you want. The AI check on an ordinary ask is free. A verifier you choose can charge a fee, which its operator sets. You see the total before you agree. |
| You end with | A closed ask, a decision on every completion, and the unspent money back in your account. |
| If it goes wrong | A refused ask spends nothing. Closing an ask sends back what was not paid out. asks.world describes no step for challenging a decision. |
| Who has authority | You set what counts as done. Unless you choose otherwise, you give the final OK. Only your own tap posts, approves or closes. |
A full run in the sandbox, then what changes with real money and when you post as a company.
Do work and get paid
You find an ask, do the work, hand in a completion, and are paid when it is approved. You can cash out to a bank account, mobile money or digital dollars.
| Available now | Yes, on asks.world. |
| You need | A Google account. For Pro Asks, a pro page verified with LinkedIn. To cash out, LinkedIn verification and a verified identity credential. |
| Cost | Nothing to complete an ask. |
| You end with | An approved completion, and its payment in your asks.world account in US dollars. |
| If it goes wrong | A completion that fails is not paid, and you are told why. There is no "needs changes" step and no second completion. A failed cash-out can be retried or put back. |
| Who has authority | The verifier decides whether your completion meets the task. Where someone gives a final OK, only that approval pays. An AI agent sends completions for you only once you have allowed it, and only you can cash out. |
From finding an ask to cashing out, with what happens when a completion is not passed.
Verify, certify and sell outcomes
You measure something that happened (stoves used, trees surviving, people trained), have each claim decided against published rules, and turn the verified result into a certificate or tokens that someone else can hold, buy or retire.
| Available now | The pieces are published: claim collections and decision oracles, IXO Credentials for certificates, and the token module for minting, transferring and retiring. The guides give each message. No single guide runs the whole sequence. |
| You need | A developer. A protocol with a claim form and a rubric for the outcome, a decision oracle to check claims, and a funded account on a test network. |
| Cost | Network fees on each transaction, and the decision fee for each claim, which the oracle's operator sets. |
| You end with | Decided claims that record the verified outcome, a credential that certifies it, and tokens issued for it. |
| If it goes wrong | A claim that fails is recorded as rejected, with a reason. A claim the rules cannot decide goes to a person. Tokens can be paused or cancelled by whoever controls the token. |
| Who has authority | The programme owns the rules. The oracle produces facts and the decision engine decides. The token's minter issues tokens, and the issuer signs the certificate. |
Measurement, reporting and verification with devices and oracles.
Design an evaluatorWrite the rules the outcome is judged by.
IXO CredentialsIssue a certificate as a verifiable credential.
Manage tokensMint tokens for an outcome, transfer them to a buyer, and retire them.
Finance outcomes
You commit funding that is released only when a result has been verified, so that the money follows the outcome and not the plan.
| Available now | Two mechanisms are published. Payment terms on a claim collection pay out when a claim is approved. The bonds module issues bonds that can settle outcome payments. The financing guide is a design guide. |
| You need | A developer, and a clear statement of the outcome and how it will be proven. |
| Cost | The funding itself, network fees, and the decision fee for each claim. |
| You end with | Funding whose release is tied to decisions that anyone with access can check. |
| If it goes wrong | No approval means no payment. A collection whose account cannot cover a payment keeps the decision back until it is funded. |
| Who has authority | The funder sets the payment terms and funds the account. The decision engine decides each claim. The payment terms pay only on an approved decision. |
Plan the conditions, the evidence and the payment rules.
Manage bondsCreate a bond, set its terms, and settle outcome payments.
Run your own payouts
Your organisation pays people for approved claims (suppliers, couriers, field workers) from its own Stripe balance or its own wallet, under its own limits and approvers.
| Available now | Yes. The @ixo/payouts-facilitator tool installs it on your own Cloudflare account. |
| You need | Node 24 LTS or newer, a Cloudflare account, and a way to pay: a Stripe account approved for Connect, or USDC and a little ETH on Base. You must be a controller of your company's domain. |
| Cost | IXO charges no licence fee. You fund the payouts yourself. Stripe's approval for Connect can take days. |
| You end with | A payouts service linked to your company, with trusted verifiers, a limit for one payout, and an approval threshold. Its trust check ends with "ok": true. |
| If it goes wrong | You can pause all payouts with one command. If the secrets file is lost, the service must be set up again, so back it up when you finish. |
| Who has authority | The controllers of your company's domain are always admins. They set the limits and name the payout team. Above the approval threshold, a person approves each payout. IXO never holds your keys. |
Install, link, fund, set limits and check, with a prompt that lets an AI assistant run the setup.
Build on the protocol
You use the SDKs and APIs to create domains, submit and evaluate claims, issue credentials, or build an AI service with its own identity.
| Available now | The SDKs, APIs and reference pages are published. The code examples are patterns to adapt. Nobody has published a tested repository that runs them from start to finish. |
| You need | Node, and a funded account on a test network for anything that writes to the chain. |
| Cost | Network fees on each transaction. Use testnet or devnet while you build. |
| You end with | Your own application reading and writing IXO records. |
| If it goes wrong | A failed transaction returns a code and a log. The error reference covers the service APIs. |
| Who has authority | Your signer's keys, and whatever grants and delegations other parties have given it. |
SDKs, APIs, credentials and the sandbox, on one page.
Build an agentic oracleAn AI service with its own identity, built with QiForge.
If you came for something else
| You are | Go to |
|---|---|
| A researcher testing a theory of change | Review a theory of change with Outcome Graph |
| Working with household energy programmes | Emerging Platform overview |
| An AI agent, or someone connecting one | MCP servers for what an agent can connect to and do, and For AI agents to scaffold an oracle |