# AX Check: omni.co
Checked 2026-10-13.

CLI and docs are solid, but pricing stays out of reach
13 of 23 checks passed, led by a clean CLI quickstart and MCP/API docs. All 3 pricing checks were unassessed since no pricing page was ever fetched.

## Onboarding needs a login

## Coding sessions
All three sessions completed. One quoted specific Free/Pro/Team prices and usage terms, while the other two found no pricing page (one hit a 404 and stopped, the other gave only a vague per-seat description with no figures or source).

### DeepSeek V4.1 Flash
[View public run](https://agents.withgauge.com/p/runs/d53216af-6e08-4289-8006-581eb21b87ea) · [Read transcript](https://www.ax-check.com/omni.co/sessions/deepseek.json)
Quoted the Free/Pro/Team prices along with request quotas, overage rates, BYOK vs managed-credit 15% margin, and noted the prices cover the hosted service only. (seq 42, seq 64)
#### End-to-end onboarding
- **Onboarding needs a login**: The agent never obtained a real Synapse API key. It only probed the hosted gateway with a deliberately invalid key to confirm reachability (HTTP 401), then shipped example code that requires a human to sign up at synapse.omni.dev and paste in a real key. No self-service credential acquisition occurred, so no authenticated operation was demonstrated.
  Event 46:

  ```text
  curl -sS -m 15 -o /tmp/syn_resp.txt -w "HTTP %{http_code}\n" -X POST "https://gateway.synapse.omni.dev/v1/chat/completions" \
    -H "Authorization: Bearer synapse_INVALID_TEST_KEY"
  ```
  Event 48:

  ```text
  HTTP 401
  invalid API key
  ```
  Event 64:

  ```text
  Blocker: I don't have a Synapse API key, so I could not complete a successful call. Everything else is wired and ready.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No self-service way to obtain a Synapse API key**: The hosted gateway quickstart requires signing up at synapse.omni.dev and manually creating a key through a dashboard UI. The agent had no credential and no path to generate one programmatically, so it could only validate reachability with an intentionally invalid key and had to stop short of a real authenticated call. This is a missing-credentials limitation of the test environment/product, not an agent error.
  Event 48:

  ```text
  HTTP 401
  invalid API key
  ```
  Event 64:

  ```text
  Blocker: I don't have a Synapse API key, so I could not complete a successful call. Everything else is wired and ready.
  ```
- **Product name 'Omni' is ambiguous across multiple unrelated products**: Web search and doc crawling surfaced at least two distinct, real developer products both called 'Omni' (Omni Analytics BI platform at omni.co, and an AI gateway called Synapse under omni.dev), plus several unrelated SaaS tools using the same name. The agent had to spend multiple search/fetch cycles disambiguating before picking one, which is a product-discovery friction rather than an agent mistake.
  Event 64:

  ```text
  There are multiple developer-facing products named Omni. I found two with real docs
  ```
  Event 21:

  ```text
  Quickstart | Omni Docs 
   omni.channel/docs/quickstart
   Quickstart | Omni Docs 
   docs.omni.dev/products/synapse/quickstart
   Quickstart - Omni CLI - Omni Docs 
   docs.omni.co/developers/cli/quickstart
  ```

#### Suggested Changes
- **Add a public pricing page link for Omni Analytics (omni.co)**: Requesting https://omni.co/pricing currently returns a 404 ('Page not found - Omni Analytics'). Add a working pricing or 'contact sales' redirect at that path on the omni.co marketing site so developers evaluating the BI product don't hit a dead end; verify by curling omni.co/pricing and confirming a 200 with pricing or lead-gen content instead of the 404 page.
  Event 25:

  ```text
  ===== https://omni.co/pricing =====
   Page not found - Omni Analytics
  ```
- **Fix broken .md quickstart links on docs.omni.dev**: Appending '.md' to Synapse doc URLs (as recommended by the docs.omni.co llms.txt convention) returns a 404 on docs.omni.dev, e.g. https://docs.omni.dev/products/synapse/quickstart.md and https://docs.omni.dev/llms.txt both return 'Page Not Found'. Either implement the markdown/llms.txt endpoints on docs.omni.dev consistently with docs.omni.co, or remove any documentation references implying they exist; verify by curling the .md and llms.txt paths and confirming real content is returned.
  Event 33:

  ```text
  <h1 class="font-bold text-6xl text-fd-muted-foreground">404</h1><h2 class="font-semibold text-2xl">Page Not Found</h2>
  ```
- **Clarify product naming between Omni Analytics and Omni/Synapse (omni.dev)**: Both docs.omni.co (Omni Analytics, a BI tool) and docs.omni.dev (an open-source ecosystem including the Synapse AI gateway) use the bare name 'Omni', causing real ambiguity in search results and docs crawling. Add a disambiguation note or distinct naming (e.g., keep 'Synapse' as the primary product name rather than 'Omni/Synapse') on the omni.dev marketing site landing page so new developers don't need multiple search/fetch cycles to figure out which product they're being pointed to.
  Event 64:

  ```text
  There are multiple developer-facing products named Omni. I found two with real docs
  ```

### Kimi K3
[View public run](https://agents.withgauge.com/p/runs/ed4d70b2-e5b3-4ef3-b9c6-d99d6e337e50) · [Read transcript](https://www.ax-check.com/omni.co/sessions/kimi.json)
Gave no cost figure and no plan or trial assumptions. It said 'contact sales' after a 404 on omni.co/pricing, without following the 301 from www.omni.co/pricing. (seq 28, seq 84)
#### End-to-end onboarding
- **Onboarding needs a login**: The agent never obtained real Omni credentials. It inspected docs/OpenAPI, wrote a Python script and README, then ran the script which immediately exited with a credential-missing error. No Omni account, API key, or hosted instance URL was ever acquired or used, so no authenticated operation against the actual product occurred.
  Event 82:

  ```text
  BLOCKED: set OMNI_BASE_URL and OMNI_API_KEY.
  Both come from an existing Omni instance (Settings > API access); they can't be self-provisioned.
  exit=1
  
  ```
  Event 84:

  ```text
  I'm blocked on credentials, and this is a hard stop. API keys are minted inside an existing Omni organization (Settings → API access), and getting an organization requires a trial/demo signup with sales — there's no self-serve key I can provision, and this environment has no Omni instance URL or key.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No self-serve way to obtain an Omni API key**: Omni requires an existing organization (created via sales demo/trial) before any API key or PAT can be minted in Settings > API access. The sandbox had no OMNI_BASE_URL or OMNI_API_KEY pre-provisioned, so the agent could not authenticate against the hosted product at all. This is a credential/test-environment limitation, not a product defect — Omni's auth model (org admin or user-scoped tokens) is standard and documented.
  Event 82:

  ```text
  BLOCKED: set OMNI_BASE_URL and OMNI_API_KEY.
  Both come from an existing Omni instance (Settings > API access); they can't be self-provisioned.
  exit=1
  
  ```
  Event 84:

  ```text
  there's no self-serve key I can provision, and this environment has no Omni instance URL or key
  ```
- **No public pricing page for Omni**: omni.co/pricing and omni.co/plans both returned 404, and the only pricing-adjacent path found was the in-app billing settings page (admin-only, invoice-based). This blocked the agent from giving the user concrete pricing figures; it's product/business behavior (sales-led pricing) rather than agent error.
  Event 28:

  ```text
  == https://omni.co/pricing/
  404
  
  ```
  Event 44:

  ```text
  - [Managing billing & invoices](https://docs.omni.co/administration/billing.md): View your organization's Omni billing information & invoices.
  
  ```

#### Suggested Changes
- **Add a public pricing page or link from the marketing site**: omni.co/pricing and omni.co/plans both 404; the only pricing info found pointed to in-app, admin-only billing docs. Publish a pricing page (or clear link to a pricing explainer) linked from the omni.co navigation footer, and verify it resolves with a 200 instead of a 404.
  Event 28:

  ```text
  == https://omni.co/pricing/
  404
  == https://www.omni.co/pricing
  301
  == https://omni.co/plans
  404
  
  ```
- **Offer a self-serve sandbox/trial API key for developer evaluation**: The CLI/API docs describe OAuth and Organization API keys, but both require an existing Omni organization obtained through a sales/demo signup. Add a free self-serve trial path (e.g., a sandbox org with a scoped demo API key) on the developers quickstart page so first-time evaluators can exercise GET /v1/whoami and POST /v1/query/run without contacting sales; verify by confirming a new signup can generate a working key end-to-end.
  Event 84:

  ```text
  getting an organization requires a trial/demo signup with sales — there's no self-serve key I can provision
  ```

### Qwen 3.8 Max
[View public run](https://agents.withgauge.com/p/runs/c1f684fe-20c9-4ca5-929a-ac2784167680) · [Read transcript](https://www.ax-check.com/omni.co/sessions/qwen.json)
Described pricing only as per-seat with workspace/enterprise plans. It gave no figure, no source and no stated assumptions, and it never read a pricing page. (seq 32)
#### End-to-end onboarding
- **Onboarding needs a login**: The agent never obtained Omni credentials. It searched the sandbox for API keys/SDKs, found none, then probed the live Omni API directly and hit a 404/auth wall. No account creation, token issuance, or authenticated operation occurred.
  Event 11:

  ```text
  No Omni-related credentials, API keys, or environment variables exist (only pi's own).
  ```
  Event 30:

  ```text
  {"error":{"code":404,"message":"Not found"}}
  ```
  Event 32:

  ```text
  every endpoint requires per-user credentials (an API key ID + secret from an Omni workspace). There's no sandbox, public, or credential-free tier to hit.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No Omni SDK, docs, or credentials present in environment**: The repo was empty and no Omni-related environment variables, keys, or installed packages existed, so the agent could not identify or access the actual product referenced by the user (agent/environment limitation, not product defect, since the user never supplied which Omni product or any credentials).
  Event 11:

  ```text
  No Omni-related credentials, API keys, or environment variables exist (only pi's own).
  ```
  Event 24:

  ```text
  The repo (`/sandbox/repo`) is empty (just a `.gitignore` and an initial commit) — no Omni SDK, docs, or config.
  ```
- **Ambiguous product identity and no free-tier API access**: Public registry lookups for 'omni' returned unrelated packages (an old PyPI entry and a dormant npm framework), and the live omniapp.co API required per-user credentials with no public/sandbox tier, so no example could be built or verified (product behavior: no self-serve or anonymous access, combined with name ambiguity).
  Event 22:

  ```text
  {"_id":"omni","_rev":"47-822555402709507be2202c6f3e4cdcb7","name":"omni","description":"Omni.js - Javascript framework to easily build real-time web apps."
  ```
  Event 30:

  ```text
  {"error":{"code":404,"message":"Not found"}}
  ```
  Event 32:

  ```text
  Omni's API (`https://omniapp.co/api/v1/...`) is live, but every endpoint requires per-user credentials (an API key ID + secret from an Omni workspace). There's no sandbox, public, or credential-free tier to hit.
  ```

#### Suggested Changes
- **Add a public sandbox or free-tier API key option for Omni**: At omniapp.co, provide a way for a new developer to obtain a test API key without a paid workspace (e.g., a trial endpoint or public demo credentials). Verify by having an unauthenticated developer hit https://omniapp.co/api/v1 and receive a usable response instead of a 404/auth-required error.
  Event 30:

  ```text
  {"error":{"code":404,"message":"Not found"}}
  ```
  Event 32:

  ```text
  There's no sandbox, public, or credential-free tier to hit.
  ```

### Task given to each agent
Help me build a simple example using Omni. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop.

No product credentials were supplied and no purchases were authorized.

## Score: C · 57/100 (provisional)
Grades come from completed site checks. Coding sessions and skipped checks do not affect the score.

### Clarity
- **Failed** — Homepage answers Markdown requests

  ```text
  Homepage returned text/html for a Markdown Accept header; no Markdown representation served.
  ```

- **Failed** — llms.txt provides an actionable documentation index

  ```text
  llms.txt lists only four Markdown pages and related HTML links, no docs index or starting guidance.
  ```

- **Failed** — llms.txt provides navigation guidance

  ```text
  llms.txt gives no navigation guidance or ordering beyond a flat list of links.
  ```

- **Failed** — llms.txt mentions offered API, MCP, and skills

  ```text
  llms.txt omits any mention of the offered API, MCP server, CLI or agent skills.
  ```

- **Pass** — A compact guide representation exists

  ```text
  Omni publishes standalone Markdown pages, e.g. CLI quickstart and MCP docs served as text/markdown.
  ```

- **Pass** — A focused guide is directly retrievable

  ```text
  CLI quickstart is directly retrievable as Markdown with install, auth and first commands.
  ```

- **Pass** — Equivalent instructions fit a token budget

  ```text
  CLI quickstart Markdown is 591 tokens, well within the 8000-token budget.
  ```

- **Skipped** — Product-docs links survive format changes

  ```text
  Homepage Markdown unsupported, so link preservation across formats cannot be measured.
  ```

- **Pass** — The compact guide is independently actionable

  ```text
  CLI quickstart gives concrete steps: install, omni config init, login, then whoami/models/documents commands.
  ```

- **Pass** — Install and next-step links resolve

  ```text
  Fetched CLI quickstart, install, agent-skills and API pages all returned 200 with usable next steps.
  ```


### Onboarding
- **Pass** — Docs lead to a relevant quickstart

  ```text
  CLI quickstart gives concrete steps: install, config init, authenticate, run first commands.
  ```

- **Pass** — Installation commands are extractable

  ```text
  Install page shows brew tap/install, curl install script, and build-from-source commands.
  ```

- **Pass** — Code examples are available without interaction

  ```text
  Quickstart and install pages show inline bash commands without interaction.
  ```

- **Pass** — Prerequisites and auth boundaries are explicit

  ```text
  Requirements list Omni account; auth page details OAuth and API key boundaries.
  ```


### Pricing
- **Failed** — Agents identify pricing and its assumptions

  ```text
  3 of 3 sessions were judged on pricing; 2 fell short. DeepSeek V4.1 Flash: Quoted the Free/Pro/Team prices along with request quotas, overage rates, BYOK vs managed-credit 15% margin, and noted the prices cover the hosted service only. (seq 42, seq 64) Kimi K3: Gave no cost figure and no plan or trial assumptions. It said 'contact sales' after a 404 on omni.co/pricing, without following the 301 from www.omni.co/pricing. (seq 28, seq 84) Qwen 3.8 Max: Described pricing only as per-seat with workspace/enterprise plans. It gave no figure, no source and no stated assumptions, and it never read a pricing page. (seq 32) This behavioural item does not affect the fast grade.
  ```

- **Skipped** — Pricing is readable without interaction

  ```text
  No pricing page was fetched; homepage only offers Free Trial and demo links.
  ```

- **Skipped** — Prices are stated, not gated

  ```text
  No pricing page was fetched; no stated prices appear in the evidence.
  ```

- **Skipped** — Pricing units and limits are explicit

  ```text
  No pricing page was fetched, so units and limits cannot be judged.
  ```


### Activation
- **Pass** — An API reference or OpenAPI spec is reachable

  ```text
  Omni REST API reference at /api and OpenAPI specs embedded in endpoint pages.
  ```

- **Pass** — An MCP server is documented and well-formed

  ```text
  MCP server documented with connection URLs, OAuth/API-key auth, tools and client setup.
  ```

- **Pass** — A CLI install path is documented

  ```text
  CLI install documented via Homebrew, install script, GitHub releases, build from source.
  ```

- **Skipped** — SDK packages resolve on their registries

  ```text
  No registry lookup result for an Omni SDK or CLI package was supplied.
  ```

- **Pass** — Agent skills are published

  ```text
  Agent skills published: open-source repo, install paths, supported platforms, example prompts.
  ```



[Full report data](https://www.ax-check.com/omni.co/report.json)