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

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.

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.

Build specific capabilities

Interfaces

Concepts worth reading first

Build with AI agents

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

Read these docs

ResourceURLWhat it is
Markdown mirror<page-url>.mdAny page as Markdown. Also served on Accept: text/markdown.
Page index/llms.txtEvery navigation page with its description.
Full corpus/llms-full.txtThe whole documentation set in one request.
MCP server/mcpStreamable HTTP JSON-RPC with search_docs and read_page.
MCP server card/.well-known/mcp.jsonTransport, capabilities, and tool schemas, readable before connecting.
OpenAPI/openapi.json, /openapi.yamlThe Emerging Platform API, with an operation ID and typed schema per endpoint.
Sitemap/sitemap.xmlEvery 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.

ServerEndpointWhat an agent can do
Askshttps://asks.world/v1/mcpPost asks, find paid work and hand in completions, with real money.
Asks sandboxhttps://test.asks.world/v1/mcpThe same, with practice money. Start here.
A decision oracle/v1/mcp on the oracle's hostSubmit 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:

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

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