IX-API’s specification and the tools around it are developed in the open. All of the repositories below are public, on gitlab.com/ix-api .
The specification IX-API is built from: the source the OpenAPI definitions at docs.ix-api.net are generated from, with components you can use directly for serialization. Use it if you want the raw spec rather than the rendered docs, or want to generate your own schema or client.
The reference implementation behind sandbox.ix-api.net : a full IX-API v2 server with mock-data bootstrapping, OAuth2 authentication, a browsable REST API and Prometheus metrics. Run it yourself with Docker Compose when you want a local, disposable IX-API to develop and test against instead of the shared hosted sandbox.
An MCP server that an exchange runs next to its IX-API implementation, giving an AI agent that exchange’s documentation and API access under your own IX-API credentials. Point an MCP client such as Claude at an exchange’s instance, or at the public sandbox, once you want an agent to work with IX-API on your behalf.
The documentation MCP server and Claude Code plugin for IX-API: it serves these docs — guides, endpoint reference, schemas, per schema version — as a typed HTTP API and as MCP tools, and the plugin adds matching agent skills and an OAuth2 IX-API client. Install the plugin, or point any MCP client at the hosted service, if you want an agent to look up IX-API documentation for itself.
The NixOS configuration that runs IX-API’s own public services — this website, the sandbox and the documentation — declared as code, covering everything from installed packages to the load balancer and monitoring setup. Published for transparency, and as a reference if you are setting up a similar deployment.
This website, generated with Hugo : the content and theme behind the pages you are reading now. Use it if you want to fix a mistake you spotted, suggest an addition, or see how a page is put together.