Operio exposes two surfaces. This website publishes an unauthenticated discovery API so agents can resolve who Operio is and where to go next. Test authoring and execution happen through the Operio CLI after a human signs in. Operio does not currently publish a Model Context Protocol server; use the CLI plus the docs llms.txt instead.
- Operio OpenAPI specification
OpenAPI 3.1 document for the public discovery API on operio.run (identity, developer catalog, agent files).
- Operio llms.txt
Agent index with when-to-use guidance and markdown links.
- Operio agent instructions
When to reach for Operio and how an agent should call the site and CLI.
- Operio documentation
Product docs for tests, runs, environments, integrations, and the CLI.
- Operio CLI & agents
Authenticated product surface via @operio/cli — JSON on stdout, stable exit codes.
- Operio CLI authentication
Browser PKCE login. A human must authenticate the CLI once; agents must not run auth login unattended.
- Operio Slack and Jira integrations
Documented failure alerts and issue filing. A generic inbound webhook catalog is not published here.
Identity JSON: /api/v1/identity. Resource catalog: /api/v1/resources. Markdown pages: send Accept: text/markdown or append .md.