Agent resources

These docs are written for humans and machines alike. If you’re an AI agent (or building one) that needs to consume this documentation programmatically, use these artifacts instead of scraping rendered HTML.

/llms.txt

A navigation index following the llmstxt.org convention — one line per page: title, one-line summary, and a link. Fetch this first to get an overview of every page on the site and decide what to fetch next.

https://docs.omniocto.com/llms.txt

/llms-full.txt

The entire docs corpus concatenated as plain markdown in a single file. Use this for single-fetch ingestion when you want the whole site in one request rather than crawling page by page.

https://docs.omniocto.com/llms-full.txt

Per-page markdown

Every rendered page is also available as raw markdown — append .md to any page’s URL:

https://docs.omniocto.com/openai-api/statefulness.md
https://docs.omniocto.com/mcp/overview.md

This gives you the source content of a single page without HTML markup, useful when you only need one topic rather than the whole corpus.

OpenAPI JSON

Both interactive API references on this site are backed by plain OpenAPI 3.1 documents you can fetch directly:

https://docs.omniocto.com/openapi/v1.json         # OpenAI-compatible API
https://docs.omniocto.com/openapi/platform.json   # Platform REST API

Use these to generate a client, validate requests, or feed a tool-use / function-calling setup that needs a formal schema rather than prose.

Skills catalog

A machine-readable catalog of task-oriented “skills” is published on the API host. Each entry names a common job and links to the markdown instructions for it (a docs page served as raw markdown):

https://api.omniocto.com/.well-known/skills/index.json

Fetch this to discover what Octo can do — authenticate, create a key, keep state across turns, handle confirmations, respect rate limits, connect an MCP client — and where to read the how-to for each. Every instructions_url points at a .md page you can fetch directly.

Live docs-search MCP

For an agent that wants to query the docs interactively instead of ingesting the whole corpus, a docs-search MCP server is available at:

https://api.omniocto.com/mcp-docs

It’s read-only, unauthenticated (these are public docs — no workspace data is involved), and exposes search-style tools for finding and retrieving relevant documentation on demand. This is a separate server from the two workspace MCP servers described in MCP overview — those require a workspace API key and expose Octo’s actual tools and conversations, whereas /mcp-docs only ever answers questions about this documentation site.