The guides come in two kinds, and the difference matters. A task guide takes you through steps to a result you can check. A design guide helps you plan something, and gives you nothing to run. Each guide below says which kind it is.
If you have not chosen what to do yet, start with Choose your path.
Task guides
Follow these from the first step to a result.
| Guide | You end with | Money |
|---|---|---|
| Post your first ask | A closed ask, a decision on each completion, and the unspent money returned | Practice money first |
| Earn from an ask | An approved completion, paid, and a cash-out | Real money to cash out |
| Host your own payouts facilitator | A payouts service on your own account that passes its trust check | Yours |
| Decision oracle | A tested, deployed oracle that records signed decisions | Testnet first |
| Build an agentic oracle | An AI service with its own identity, running locally | Devnet |
| Review a theory of change with Outcome Graph | A reviewed causal chain and a recorded decision | |
| Build an agent skill | A packaged skill an agent can load | |
| Use IXO services via USSD | An account you can use from a basic phone | |
| Use your QiForge Personal Agent | A Personal Agent that answers you, with the privacy settings you chose |
Design guides
Use these to plan before you build. They are checklists and questions, with no commands.
| Guide | Helps you plan |
|---|---|
| Design an evaluator | The rules, facts, review tasks and tests behind a verifier |
| Design a POD | A workspace for one organisation or programme |
| Design a Flow | A sequence of steps for people and agents |
| Design a Blueprint | Reusable rules for one type of claim |
| Design a verified claims workflow | How claims are submitted, reviewed and decided |
| Design a market | Listings, fulfilment, checks and payment |
| Design a digital MRV workflow | Measurement, reporting and verification as one record |
| Design outcomes-based financing | Funding released only on a verified outcome |
Payments
| Page | What it covers |
|---|---|
| How payment works | The ways to pay for a decision, where the money goes, and how a cash-out is paid |
| Charge for decisions | The payment flow on the wire, for oracle builders and API clients |
Developer guides
The developer portal is the entry point for SDKs, APIs, credentials and the sandbox. The code on SDK patterns and Developer workflows is illustrative: adapt it, and build against a test network.
Before you rely on a feature
What works today lists what is live, what runs only in the sandbox, and what is not available. What each record proves says what an approval or a receipt does and does not tell you.