# Developer portal

> A map of everything for building on IXO: credentials, quickstarts, SDKs, APIs, the sandbox, capabilities, agent access and support, each linked to its page.

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](/status) 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

<CardGroup cols={2}>
  <Card title="Build an oracle" icon="play" href="/https/docs.ixo.world/build-an-oracle/quickstart">
    Scaffold a QiForge oracle, boot it, and watch the agent call a plugin tool, in about ten minutes.
  </Card>
  <Card title="Build a decision oracle" icon="scale-balanced" href="/https/docs.ixo.world/build-an-oracle/decision-oracle">
    A service that checks claims against a rubric and signs each decision, with unit tests and a dry run.
  </Card>
  <Card title="SDK patterns" icon="file-lines" href="/https/docs.ixo.world/guides/dev/examples">
    Illustrative TypeScript for the IXO MultiClient SDK and IXO Matrix Client SDK. Adapt it and build against a test network.
  </Card>
  <Card title="Workflows" icon="diagram-next" href="/https/docs.ixo.world/guides/dev/workflows">
    The common message sequences: create an entity, submit a claim, record an evaluation, mint tokens.
  </Card>
</CardGroup>

## 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.

<CardGroup cols={2}>
  <Card title="Authentication matrix" icon="table" href="/https/docs.ixo.world/reference/authentication-matrix">
    The table of which credential and header applies to each API.
  </Card>
  <Card title="Authentication guide" icon="key" href="/https/docs.ixo.world/guides/dev/authentication">
    Set up credentials, session keys, and authorization for IXO services.
  </Card>
  <Card title="Networks and endpoints" icon="network-wired" href="/https/docs.ixo.world/reference/networks-and-endpoints">
    Chain ids and the host of each service on mainnet, testnet and devnet.
  </Card>
  <Card title="Emerging Platform API keys" icon="id-badge" href="/https/docs.ixo.world/platforms/Emerging/emerging-api">
    How Emerging Platform keys are issued and scoped, and where they are managed.
  </Card>
</CardGroup>

<Warning>
  Keep credentials in secure runtime storage, never in source files, and rotate them according to your operator policy.
</Warning>

## 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.

<CardGroup cols={2}>
  <Card title="Try an endpoint" icon="play" href="/https/docs.ixo.world/api-reference/emerging/get-household-stats">
    `GET /households/stats` with the request console attached.
  </Card>
  <Card title="Test your oracle" icon="vial" href="/https/docs.ixo.world/build-an-oracle/develop/test-your-oracle">
    Run an oracle locally and exercise its plugins before deploying.
  </Card>
</CardGroup>

## Build specific capabilities

<CardGroup cols={3}>
  <Card title="Digital twins" icon="cube" href="/https/docs.ixo.world/guides/digital-twins">
    Create and manage domains for real-world systems, assets and organisations.
  </Card>
  <Card title="Claims and verification" icon="file-check" href="/https/docs.ixo.world/guides/dev/ixo-claims">
    Submit and verify claims with evidence using the IXO Protocol Claims module.
  </Card>
  <Card title="Claim disputes" icon="scale-balanced" href="/https/docs.ixo.world/guides/dev/claim-disputes">
    Challenge a claim's submitter or evaluator, and how adjudicators decide.
  </Card>
  <Card title="Digital MRV" icon="chart-line" href="/https/docs.ixo.world/guides/digital-mrv">
    Set up digital measurement, reporting, and verification workflows.
  </Card>
  <Card title="Agentic Oracles" icon="brain" href="/https/docs.ixo.world/build-an-oracle/understand/architecture">
    Build AI oracle services for verification, evaluation and automation.
  </Card>
  <Card title="Decision oracle" icon="scale-balanced" href="/https/docs.ixo.world/build-an-oracle/decision-oracle">
    Judge claims with `@ixo/decision-oracle` on a Cloudflare Worker.
  </Card>
  <Card title="Payments" icon="credit-card" href="/https/docs.ixo.world/payments/facilitator">
    Charge per decision in PAY, USDC on Base or card, and host your own payouts facilitator.
  </Card>
  <Card title="Domain settings" icon="sliders" href="/https/docs.ixo.world/guides/dev/domain-settings">
    Configure a domain's permissions, services and linked resources.
  </Card>
  <Card title="IXO Credentials" icon="id-card" href="/https/docs.ixo.world/guides/dev/credentials/overview">
    Issue, hold, share and revoke SD-JWT verifiable credentials over OpenID4VCI and OpenID4VP, on devnet, testnet and mainnet.
  </Card>
  <Card title="Model Context Protocol" icon="plug" href="/https/docs.ixo.world/mcp/model-context-protocol">
    Connect AI tools to IXO services through MCP servers.
  </Card>
</CardGroup>

## Interfaces

<CardGroup cols={3}>
  <Card title="API reference" icon="server" href="/https/docs.ixo.world/api-reference">
    RPC, REST, GraphQL, and service API interfaces for IXO Protocol and IXO application services.
  </Card>
  <Card title="SDK reference" icon="toolbox" href="/https/docs.ixo.world/sdk-reference">
    IXO MultiClient SDK, IXO SignX SDK, IXO Matrix Client SDK and JAMBO PWA SDK.
  </Card>
  <Card title="Errors" icon="triangle-exclamation" href="/https/docs.ixo.world/api-reference/errors">
    Status codes, the JSON error envelope, and how to recover from each class of failure.
  </Card>
  <Card title="Pagination" icon="rectangle-list" href="/https/docs.ixo.world/api-reference/pagination">
    Cursor and page patterns for large result sets.
  </Card>
  <Card title="Product and SDK map" icon="signs-post" href="/https/docs.ixo.world/reference/product-and-sdk-map">
    The list of products, SDKs and their package identifiers.
  </Card>
  <Card title="Glossary" icon="book" href="/https/docs.ixo.world/reference/glossary">
    One definition for each term used across the protocol, products and SDKs.
  </Card>
</CardGroup>

## Concepts worth reading first

<CardGroup cols={2}>
  <Card title="Core concepts" icon="hand-pointer" href="/https/docs.ixo.world/core-concepts">
    The vocabulary of IXO: domains, claims, evidence, decisions and who takes part.
  </Card>
  <Card title="IXO Protocol" icon="cube" href="/https/docs.ixo.world/protocols/ixo-protocol">
    The Cosmos SDK blockchain: entity management, claims, tokens, bonds, and smart accounts.
  </Card>
  <Card title="IXO Matrix" icon="database" href="/https/docs.ixo.world/articles/ixo-matrix">
    The encrypted data and communication layer behind data rooms, evidence storage, and messaging.
  </Card>
  <Card title="Qi and Agentic Oracles" icon="sparkles" href="/https/docs.ixo.world/articles/qi-intelligent-cooperating-system">
    Cooperation between people and agents, oracles, and agent tooling.
  </Card>
</CardGroup>

## 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](/status) says what is live, what runs only in the sandbox, and what is not available.
- [What each record proves](/trust-boundaries) says what an approval, a decision and a receipt do and do not show.
- The [Glossary](/reference/glossary) defines each term once.

`/llms.txt` names these pages at the top, and the documentation MCP server names them in its instructions.

<CardGroup cols={2}>
  <Card title="MCP servers" icon="code-simple" href="/https/docs.ixo.world/mcp/model-context-protocol">
    Every server an agent can connect to, the limits on what it may do, and the plugins for Claude Code and Codex.
  </Card>
  <Card title="For AI agents building an oracle" icon="robot" href="/https/docs.ixo.world/build-an-oracle/for-ai-agents">
    A single dense page an agent can scaffold a QiForge oracle from, with every signature, option and env var.
  </Card>
</CardGroup>

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

<CardGroup cols={2}>
  <Card title="Ask the docs assistant" icon="message-bot">
    The **Ask Assistant** control in the header answers from these docs, starting from the page you are reading.
  </Card>
  <Card title="Developer community" icon="slack" href="https://ixofoundation.slack.com/archives/C04UERAUHQT">
    Questions, discussions, and support on Slack.
  </Card>
  <Card title="Email" icon="envelope" href="mailto:assistant@ixo.world">
    assistant@ixo.world
  </Card>
  <Card title="Open-source repositories" icon="github" href="https://github.com/ixofoundation">
    Source code for the public SDKs, gateway tools and reference implementations.
  </Card>
</CardGroup>
