# Developer portal

> The entry point for building on IXO: credentials, quickstarts, SDKs, API interfaces, a live sandbox, and the machine-readable surfaces agents can call.

You are wiring real-world workflows where agents and services act on **verifiable** entities, claims, and evidence — not only on generic LLM context.

**IXO** anchors what is true on-chain and in linked services: domains, claims, credentials. **Qi**, the Qi Intelligent Cooperating System, is where people and agents cooperate on that truth, through IXO Matrix, oracle and agent services, and automation. Most projects implement **state first** — protocol, claims, indexing — then add **cooperation**: Matrix, Agentic Oracles, SDKs.

This page is a map. Every card links to the canonical page for that topic; nothing here is restated from it.

## Start building

<CardGroup cols={2}>
  <Card title="Build an oracle" icon="play" href="/build-an-oracle/quickstart">
    Scaffold a QiForge oracle, boot it, and watch the agent call a plugin tool — about ten minutes.
  </Card>
  <Card title="What you can build" icon="lightbulb" href="/build-an-oracle">
    The build tracks available on the stack, and which one fits your problem.
  </Card>
  <Card title="Implementation examples" icon="file-lines" href="/guides/dev/examples">
    Worked end-to-end TypeScript for the IXO MultiClient SDK and IXO Matrix Client SDK.
  </Card>
  <Card title="Workflows" icon="diagram-next" href="/guides/dev/workflows">
    The common build sequences: register a domain, collect claims, evaluate, settle.
  </Card>
</CardGroup>

## Credentials and access

API credentials differ by surface — 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="/reference/authentication-matrix">
    The canonical table: which credential and header applies to each API surface.
  </Card>
  <Card title="Authentication guide" icon="key" href="/guides/dev/authentication">
    Set up credentials, session keys, and authorization for IXO services.
  </Card>
  <Card title="Networks and endpoints" icon="network-wired" href="/reference/networks-and-endpoints">
    Chain IDs, base URLs, and environments for mainnet and testnet.
  </Card>
  <Card title="Emerging Platform API keys" icon="id-badge" href="/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

The Emerging Platform API ships with a live console on every endpoint page. Set a bearer token, fill the typed parameters, and send a real request against the development server — no local setup, no CORS workarounds.

<CardGroup cols={2}>
  <Card title="Try an endpoint" icon="play" href="/api-reference/emerging/get-household-stats">
    `GET /households/stats` with the request console attached.
  </Card>
  <Card title="Test your oracle" icon="vial" href="/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="/guides/digital-twins">
    Create and manage entity domains for real-world systems, assets, and organisations.
  </Card>
  <Card title="Claims and verification" icon="file-check" href="/guides/dev/ixo-claims">
    Submit and verify impact claims with evidence using IXO Protocol claims modules.
  </Card>
  <Card title="Digital MRV" icon="chart-line" href="/guides/digital-mrv">
    Set up digital measurement, reporting, and verification workflows.
  </Card>
  <Card title="Agentic Oracles" icon="brain" href="/build-an-oracle/understand/architecture">
    Build AI-powered oracle services for verification, evaluation, and automation.
  </Card>
  <Card title="Domain settings" icon="sliders" href="/guides/dev/domain-settings">
    Configure entity domain permissions, services, and linked resources.
  </Card>
  <Card title="Model Context Protocol" icon="plug" href="/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="/api-reference">
    RPC, REST, GraphQL, and service API interfaces for IXO Protocol and IXO application services.
  </Card>
  <Card title="SDK reference" icon="toolbox" href="/sdk-reference">
    IXO MultiClient SDK, SignX SDK, IXO Matrix Client SDK, and JAMBO PWA SDK.
  </Card>
  <Card title="Error handling" icon="triangle-exclamation" href="/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="/api-reference/pagination">
    Cursor and page patterns for large result sets.
  </Card>
  <Card title="Product and SDK map" icon="signs-post" href="/reference/product-and-sdk-map">
    The canonical list of products, SDKs, and their package identifiers.
  </Card>
  <Card title="Glossary" icon="book" href="/reference/glossary">
    Canonical terms used across the protocol, products, and SDKs.
  </Card>
</CardGroup>

## Concepts worth reading first

<CardGroup cols={2}>
  <Card title="Core concepts" icon="hand-pointer" href="/core-concepts">
    Vocabulary and mental models for IXO, Qi, entities, claims, evidence, verification, and workflows.
  </Card>
  <Card title="IXO Protocol" icon="cube" href="/protocols/ixo-protocol">
    The Cosmos SDK blockchain: entity management, claims, tokens, bonds, and smart accounts.
  </Card>
  <Card title="IXO Matrix" icon="database" href="/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="/articles/qi-intelligent-cooperating-system">
    Human–agent cooperation, oracles, and agent tooling over verified workflows.
  </Card>
</CardGroup>

## Build with AI agents

These docs are published for machines as well as people. Nothing here needs scraping.

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

<CardGroup cols={2}>
  <Card title="For AI agents" icon="robot" href="/build-an-oracle/for-ai-agents">
    A single dense page an agent can scaffold a QiForge oracle from — every signature, option, and env var.
  </Card>
  <Card title="MCP servers" icon="code-simple" href="/mcp/model-context-protocol">
    The MCP servers in the IXO ecosystem, including this documentation server.
  </Card>
</CardGroup>

Unknown paths on this site return a real HTTP 404 with a Markdown body listing these surfaces, 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, grounded in 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 SDKs, gateway tools, and reference implementations.
  </Card>
</CardGroup>