Docs are coming with the API.
The API is in development, so there is nothing to document yet that would still be true at launch. Here is the shape it will take — three families, matching the three paths underapi.combycode.com.
oaiOpenAI-compatibleAt launch
/docs/oai/
Quickstart and the baseURL diff, chat completions, responses, embeddings, documents, media generation, files — and a page on where we deliberately differ from OpenAI.
orxaORXA nativeIn design
/docs/orxa/
Tasks, tool flows, skills, memory, cache and files as first-class resources. Long-running work that survives a disconnect.
teamManagementIn design
/docs/team/
Keys, projects, budgets, teams, usage and audit.
What ships alongside the reference
A versioned OpenAPI definition per family, at/openapi/{family}.v1.yaml. The specs are the source the client SDKs and the reference pages are generated from, rather than a description written afterwards.
A markdown mirror of every page. Append.mdto any docs URL and you get the raw source, so agents and LLMs can read the documentation without scraping HTML.
In the meantime, the engine underneath is open source and documented today:ORXA LLM-SDK.