Choose your path

The ways to start with IXO, compared side by side: build an evaluator, commission or do paid work, certify and finance outcomes, or run payouts.

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 toStart hereNeeds code
Turn what I know into a service that checks claimsBuild an evaluatorSome
Get a piece of work done and pay only for accepted resultsCommission workNo
Do work and be paid for itDo work and get paidNo
Measure results, then certify and sell themVerify, certify and sell outcomesYes
Tie funding to verified resultsFinance outcomesYes
Pay my organisation's people from our own accountsRun your own payoutsCommand line
Put identity, claims and decisions into my own applicationBuild on the protocolYes

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 nowYes. The @ixo/decision-oracle package runs on devnet, testnet and mainnet.
You needKnowledge of the work being judged. To build, a free Cloudflare account. An AI assistant can do most of the setup with you.
CostThe 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 withA deployed oracle that passes its tests, is hired by a claim collection, and records signed decisions.
If it goes wrongA 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 authorityWhoever 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.
Design an evaluator

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 nowYes, on asks.world, and with practice money in the sandbox.
You needA Google account, and a browser or an AI assistant.
CostThe 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 withA closed ask, a decision on every completion, and the unspent money back in your account.
If it goes wrongA 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 authorityYou set what counts as done. Unless you choose otherwise, you give the final OK. Only your own tap posts, approves or closes.
Post your first ask

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 nowYes, on asks.world.
You needA Google account. For Pro Asks, a pro page verified with LinkedIn. To cash out, LinkedIn verification and a verified identity credential.
CostNothing to complete an ask.
You end withAn approved completion, and its payment in your asks.world account in US dollars.
If it goes wrongA 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 authorityThe 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.
Earn from an ask

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 nowThe 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 needA 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.
CostNetwork fees on each transaction, and the decision fee for each claim, which the oracle's operator sets.
You end withDecided claims that record the verified outcome, a credential that certifies it, and tokens issued for it.
If it goes wrongA 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 authorityThe 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.

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 nowTwo 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 needA developer, and a clear statement of the outcome and how it will be proven.
CostThe funding itself, network fees, and the decision fee for each claim.
You end withFunding whose release is tied to decisions that anyone with access can check.
If it goes wrongNo approval means no payment. A collection whose account cannot cover a payment keeps the decision back until it is funded.
Who has authorityThe funder sets the payment terms and funds the account. The decision engine decides each claim. The payment terms pay only on an approved decision.

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 nowYes. The @ixo/payouts-facilitator tool installs it on your own Cloudflare account.
You needNode 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.
CostIXO charges no licence fee. You fund the payouts yourself. Stripe's approval for Connect can take days.
You end withA 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 wrongYou 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 authorityThe 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.
Host your own payouts facilitator

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 nowThe 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 needNode, and a funded account on a test network for anything that writes to the chain.
CostNetwork fees on each transaction. Use testnet or devnet while you build.
You end withYour own application reading and writing IXO records.
If it goes wrongA failed transaction returns a code and a log. The error reference covers the service APIs.
Who has authorityYour signer's keys, and whatever grants and delegations other parties have given it.

If you came for something else

You areGo to
A researcher testing a theory of changeReview a theory of change with Outcome Graph
Working with household energy programmesEmerging Platform overview
An AI agent, or someone connecting oneMCP servers for what an agent can connect to and do, and For AI agents to scaffold an oracle