Discovery URLs

Use these predictable ota.run URLs when integrating agents, crawlers, API catalogs, or internal developer portals.

The current ota.run site is static. Public discovery and documentation endpoints are unauthenticated read-only resources, so they do not route normal page traffic through an application Worker.

OpenAPI spec

Describes the public ota.run discovery API, docs indexes, OAuth metadata, and agent discovery files.

When to use it

Use this when an agent or API catalog needs a standard machine-readable description.

Example

LLM crawl guide

Lists canonical docs, blog posts, section anchors, and retrieval rules for agents.

When to use it

Use this as the first crawl target for AI systems.

Example

Docs index JSON

Lists documentation pages, summaries, intents, and section anchors.

When to use it

Use this when a bot needs structured docs inventory without scraping HTML.

Example

Agent skills index

Lists agent-oriented resources, commands, integration guides, and the official ota-run/skills distribution.

When to use it

Use this when a coding agent needs the highest-signal entry points first.

Example

OAuth 2.0 metadata

ota.run publishes OAuth 2.0 discovery metadata at standards-friendly well-known URLs so agents can identify the intended protected-resource boundary.

Current public discovery endpoints do not require access tokens. Protected hosted control-plane APIs should use this OAuth boundary when they are introduced.

OAuth discoverytext

https://ota.run/.well-known/oauth-authorization-serverhttps://ota.run/.well-known/oauth-protected-resource

Official agent skills

Ota's supported agent extension surface today is the official ota-run/skills repository. It gives agents Ota-specific guidance for contract authoring, contract review, repo readiness modeling, and Studio boundaries.

Use the skills repository or skills.sh listing when an agent needs operating instructions beyond static site discovery.

Official Ota skilltext

https://github.com/ota-run/skillshttps://skills.sh/ota-run/skillshttps://github.com/ota-run/skills/blob/main/skills/ota/SKILL.md

MCP metadata only

ota.run publishes MCP metadata for future discovery, but it does not run a live MCP protocol endpoint today.

Do not attempt an MCP handshake against ota.run. Use llms.txt, llms-full.txt, docs/index.json, and the official Ota skill for supported agent workflows.

Metadata-only MCP filestext

https://ota.run/.well-known/mcp.jsonhttps://ota.run/.well-known/mcp/server-card.json

Canonical automation docs

GitHub Action

Use the official action wrapper for CI readiness checks and pull-request feedback.

When to use it

Use this when ota should run inside GitHub Actions.

Example

JSON Output

Use stable machine-readable output instead of scraping terminal text.

When to use it

Use this when automation needs reliable status, blockers, and task inventory.

Example

Execution Receipt

Use receipts when task execution needs an auditable artifact.

When to use it

Use this for CI, agents, or hosted gates that need to explain what ran.

Example