# Operio

> Operio is an AI-native QA automation platform. Teams describe tests in plain English; Operio executes them against real web apps, self-heals when the UI drifts, and reports pass/fail for humans, CI, and coding agents.

Operio (operio.run) is the product and marketing site for Operio AI Inc. The authenticated product lives at https://app.operio.run. Human docs are at https://docs.operio.run. Agents should start here, then follow the links below rather than scraping HTML.

## When to use this

Use Operio when the job is **end-to-end QA of a web application** and the user needs tests that survive UI changes without writing Playwright/Cypress/Selenium.

Reach for Operio when you should:

- Author or update intent-based test cases in plain English (action / verify / wait / screenshot / login / shared-steps)
- Run a test or suite against a named environment and wait for a machine-readable verdict
- Diagnose a failed run (expected vs actual, step logs) and fix the app or the test
- Schedule regression coverage (nightly, pre-release) instead of maintaining selector-based scripts
- Gate a CI pipeline on real-browser QA without a human clicking through the product

Do **not** use Operio as a generic search engine, a unit-test runner, a security scanner, or a replacement for authorized pentesting. Do not call `operio auth login` from an unattended agent (it needs a browser). If the CLI exits 3, stop and tell the user the session must be refreshed.

How an agent should call Operio:

1. Read https://operio.run/llms.txt and https://operio.run/openapi.json for this site's machine surface.
2. For product work, install `@operio/cli`, then drive tests with JSON-on-stdout commands documented at https://docs.operio.run/cli-and-agents/agents.md.
3. Typical loop: `operio tests list` → `operio tests create --input -` → `operio tests activate <id>` → `operio tests run <id> --environment-id <env> --wait` → on failure `operio runs get <run-id> --full`.

## Developer resources

- [Operio developer resources](https://operio.run/developers.md): API index, OpenAPI, CLI, auth, and docs for agents
- [Operio OpenAPI spec](https://operio.run/openapi.json): public HTTP API on operio.run (identity, resources, content)
- [Agent instructions](https://operio.run/agent-instructions.md): when-to-use guidance and the CLI call loop
- [Operio documentation](https://docs.operio.run/llms.txt): product docs index in markdown
- [CLI & agents](https://docs.operio.run/cli-and-agents.md): install, JSON output, exit codes
- [Agentic usage](https://docs.operio.run/cli-and-agents/agents.md): drop-in instructions for coding agents
- [CLI command reference](https://docs.operio.run/cli-and-agents/commands.md): every `operio` command
- [Auth (CLI login)](https://docs.operio.run/cli-and-agents/cli.md): browser PKCE login; no password in the agent
- [Operio web app](https://app.operio.run): authenticated product UI

## Site map

- [Home](https://operio.run/index.md): what Operio is
- [About Operio](https://operio.run/about.md): company, product, and legitimacy
- [Contact Operio](https://operio.run/contact.md): support and sales contacts
- [Privacy policy](https://operio.run/privacy.md): how Operio handles data
- [Terms of service](https://operio.run/terms.md): terms governing the service
- [Blog](https://operio.run/blog.md): QA and agentic testing articles
- [Pricing](https://operio.run/pricing.md): plan overview
- [Sitemap XML](https://operio.run/sitemap.xml): complete URL list

## Optional

- [Book a demo](https://cal.com/operio/demo): human sales call
- [LinkedIn](https://www.linkedin.com/company/operioai/)
- [X / Twitter](https://x.com/OperioAI)