# AX Check: onvibe.run Checked 2026-09-18. Agents can't find onvibe.run's pricing, even though it's on the page Pricing is stated openly on the homepage (€5–€15/month plans), but all 3 coding sessions reported finding no pricing at all. ## End-to-end onboarding not demonstrated ## Coding sessions All three independent sessions (DeepSeek V4 Pro, Kimi K3, Qwen 3.8 Max) completed their task but each concluded onvibe.run had no pricing to report, despite the homepage listing two priced plans with clear units and limits. ### DeepSeek V4 Pro [View public run](https://agents.withgauge.com/p/runs/ebfbbdd2-c00c-4cb7-babd-d63de157b9ca) · [Read transcript](https://www.ax-check.com/onvibe.run/sessions/deepseek.json) Final output states 'There is no pricing' and grounds it in explicit assumptions — self-hosted OSS, license TBD, 'Premium subscriptions'/'API for integrations' are unchecked roadmap items (seq 87). #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The agent never located a hosted product called onvibe with an SDK or API to onboard against. It found only an open-source, self-hosted GitHub repo (snowdamiz/onvibe) whose quickstart requires local Docker/Postgres/Elixir/Vite services, and a separate onvibe.dev site that turned out to be an unrelated music player. No credentials were ever obtained and no authenticated operation against a hosted product occurred. Event 42: ```text A social media platform specifically for the vibe coding community—developers and creators who embrace AI-assisted development. Unlike traditional portfolios that hide the "how," onvibe makes the AI tools, prompts, and creative process a first-class citizen. ``` Event 85: ```text This guide covers deploying the application to Fly.io with separate frontend and backend apps. ``` Event 87: ```text There's no npm/PyPI package, no official SDK, and no hosted API I can call. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No hosted onvibe product exists to test**: Product behavior/naming ambiguity, not agent error: searches across npm, PyPI, GitHub, and web search found no hosted SDK/API for a product called onvibe. The closest GitHub match is an early-stage, self-hosted open-source repo requiring local Docker Postgres, Elixir/Phoenix backend, and Vite frontend to run; a same-named domain (onvibe.dev) resolved to an unrelated local music player app. The agent correctly identified this and stopped rather than spinning up local services, per the session's explicit instructions. Event 16: ```text Enable JavaScript and cookies to continue ``` Event 33: ```text A private music player for importing, syncing, and streaming your own library. ``` Event 42: ````text ### Quick Start ```bash # Install root dependencies (concurrently) npm install # Install frontend and backend dependencies npm run setup # Start everything (frontend, backend, postgres) with one command npm run dev ``` ```` Event 87: ````text The quickstart requires exactly what you told me to avoid: ```bash npm install && npm run setup && npm run dev ``` ```` - **npm registry lookup for onvibe returned nothing**: Test environment / product naming issue: the npm registry has no package named onvibe, and npmjs.com's package page was blocked by a Cloudflare bot challenge, so the agent could not confirm via the registry UI either. This is an external service response, not agent error, since the agent correctly fell back to other sources (GitHub, PyPI) to triangulate. Event 24: ```text {"error":"Not found"} ``` Event 69: ```text {"message": "Not Found"} ``` #### Suggested Changes - **Publish a discoverable canonical URL for the product named onvibe**: If 'onvibe' is meant to be a distinct hosted developer product, publish it under a name/domain that does not collide with the existing onvibe.dev music player and the unrelated snowdamiz/onvibe open-source social portfolio project on GitHub. Verify the fix by searching npm, PyPI, and GitHub for 'onvibe' and confirming the top hit is the intended product's docs or package, not a namesake. Event 33: ```text OnVibe — Your music, anywhere ``` Event 42: ```text # onvibe > The social portfolio platform for vibe coders ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/2bf117f2-9984-4350-a8dd-02ef74337972) · [Read transcript](https://www.ax-check.com/onvibe.run/sessions/kimi.json) Final output only states 'no pricing page... nothing to price-compare or subscribe to' — no cost figure is given at all, let alone one paired with plan/region/workload assumptions as the rubric requires. #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: Agent never located any SDK, API documentation, or credential-issuance flow for OnVibe. It found a consumer PWA with only a health-check endpoint (returns {"ok":true}) and confirmed /api/docs, /docs, /developers, /pricing all 404. It concluded there was no developer workflow to act on and stopped without obtaining or using any credentials. Event 33: ```text {"ok":true} { "name": "OnVibe", ``` Event 35: ```text No public API surface — `/api/health` returns `{"ok":true}` but there are no API docs, no OpenAPI spec, and `/api/docs` / `/docs` / `/developers` all 404. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No developer-facing API, SDK, or docs exist for OnVibe**: This is product behavior, not agent error or missing credentials. OnVibe at onvibe.dev is a consumer PWA (private music player) with no npm/PyPI package, no OpenAPI spec, and every docs-related path returned 404. The only live API path found, /api/health, is an internal health check, not a usable integration surface. The agent correctly recognized this and stopped per the seed prompt's instruction to stop if no developer workflow exists. Event 25: ```text docs -> 404 api -> 404 pricing -> 404 developers -> 404 openapi.json -> 404 api/health -> 200 sitemap.xml -> 404 ``` Event 9: ```text npm error 404 Not Found - GET https://registry.npmjs.org/onvibe - Not found ``` Event 33: ```text 404 404 ``` #### Suggested Changes - **Publish a developers or API documentation page for OnVibe**: Add a /docs or /developers route on onvibe.dev describing any available API, SDK, or self-hosting integration path. Verify the fix by confirming that path returns a real documentation page instead of a 404, as seen when the agent checked /docs, /api, /developers, and /openapi.json. Event 25: ```text docs -> 404 api -> 404 pricing -> 404 developers -> 404 openapi.json -> 404 ``` - **Add a pricing page if OnVibe intends to offer a commercial tier**: Create a /pricing route on onvibe.dev listing plans or confirm the product is free/self-hosted only. Verify by checking that /pricing no longer 404s and reflects the intended pricing model. Event 25: ```text pricing -> 404 ``` Event 35: ```text There is no pricing page (`/pricing` → 404), no plans, no billing surfaced anywhere. ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/359221cb-eadb-454b-bb9a-b0b5f54c0e16) · [Read transcript](https://www.ax-check.com/onvibe.run/sessions/qwen.json) Final output explicitly states 'I found no published pricing... I won't guess' (seq 44) — no cost figure or assumptions are given at all, directly failing this rubric. #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: No product credentials were ever obtained or used. The agent searched npm, PyPI, and the web for an "onvibe" developer product, found only a consumer music-streaming PWA (onvibe.dev) with no public API/docs/pricing page, a Telegram redirect (onvibe.io), and an empty GitHub user. No SDK or API existed to authenticate against, so the session stopped before any onboarding attempt could occur. Event 33: ```text -- docs/api subdomains -- docs.onvibe.dev -> 404 api.onvibe.dev -> 404 ``` Event 44: ```text I can't give a real assessment, because there's **no developer surface to manage** — no SDK, no documented API, no keys/console. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No public SDK, API, or docs exist for onvibe**: Product behavior/absence, not agent error: npm and PyPI have no onvibe package (including scoped/alt-name guesses), and the only two onvibe domains found are a consumer music PWA with no /docs, /api, /pricing, or OpenAPI spec, and a Telegram redirect. This left no developer workflow to act on, so the agent correctly halted per its instructions rather than fabricating an example. Event 7: ```text npm error 404 npm error 404 'onvibe@*' is not in this registry. ``` Event 24: ```text /docs -> 404 /pricing -> 404 /api -> 404 /developers -> 404 ``` Event 44: ```text I couldn't find a developer workflow for "onvibe" that I can act on. Per your instruction, I'm saying so plainly and stopping rather than inventing an example. ``` #### Suggested Changes - **Publish a docs/pricing page for the intended onvibe developer product**: If "onvibe" refers to a developer-facing SDK/API rather than the onvibe.dev music PWA, publish it under a discoverable path (e.g. onvibe.dev/docs or /pricing) since those paths currently 404 and there's no OpenAPI/swagger spec, npm package, or PyPI package under the name. Verify the fix by re-running the same npm/PyPI lookups and hitting /docs and /pricing to confirm a 200 with real content. Event 33: ```text /robots.txt -> 404 /sitemap.xml -> 404 /openapi.json -> 404 /swagger.json -> 404 /.well-known/openapi -> 404 ``` ### Task given to each agent Help me build a simple example using onvibe. 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 · 53/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 even when text/markdown was requested; no Markdown representation offered. ``` - **Failed** — llms.txt provides an actionable documentation index ```text https://onvibe.run/llms.txt returns HTTP 404, so no documentation index exists. ``` - **Skipped** — llms.txt provides navigation guidance ```text llms.txt is 404, so its navigation guidance cannot be evaluated. ``` - **Skipped** — llms.txt mentions offered API, MCP, and skills ```text llms.txt is 404, so its mention of API, MCP or skills cannot be evaluated. ``` - **Pass** — A compact guide representation exists ```text onvibe.run/docs/app-mcp.md returns a standalone Markdown guide. ``` - **Pass** — A focused guide is directly retrievable ```text app-mcp.md is directly retrievable as text/markdown with concrete mountMcp steps. ``` - **Pass** — Equivalent instructions fit a token budget ```text Guide measured 830 tokens, well under the 8000-token budget. ``` - **Skipped** — Product-docs links survive format changes ```text Homepage Markdown unsupported, so link preservation across formats is unassessed. ``` - **Skipped** — The compact guide is independently actionable ```text No compact agent-specific guide fetched; only MCP doc pages and homepage were retrieved. ``` - **Pass** — Install and next-step links resolve ```text Homepage install/next-step links to /docs and /dashboard/signup both fetched successfully. ``` ### Onboarding - **Skipped** — Docs lead to a relevant quickstart ```text No docs or quickstart pages were fetched; only a signup page and a 404 llms.txt. ``` - **Skipped** — Installation commands are extractable ```text No installation or CLI guide was fetched for onvibe.run. ``` - **Skipped** — Code examples are available without interaction ```text No documentation or code example pages were fetched. ``` - **Skipped** — Prerequisites and auth boundaries are explicit ```text Signup page shows email/password only; no API auth or prerequisites documented. ``` ### Pricing - **Failed** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 2 fell short. DeepSeek V4 Pro: Final output states 'There is no pricing' and grounds it in explicit assumptions — self-hosted OSS, license TBD, 'Premium subscriptions'/'API for integrations' are unchecked roadmap items (seq 87). Kimi K3: Final output only states 'no pricing page... nothing to price-compare or subscribe to' — no cost figure is given at all, let alone one paired with plan/region/workload assumptions as the rubric requires. Qwen 3.8 Max: Final output explicitly states 'I found no published pricing... I won't guess' (seq 44) — no cost figure or assumptions are given at all, directly failing this rubric. This behavioural item does not affect the fast grade. ``` - **Pass** — Pricing is readable without interaction ```text Homepage pricing section lists both plans with prices and features, no interaction needed. ``` - **Pass** — Prices are stated, not gated ```text Prices stated openly: €5/month or €55/year, €15/month or €165/year. ``` - **Pass** — Pricing units and limits are explicit ```text Units explicit: vCPU, MB/GB storage, database, emails per month, monthly/yearly. ``` ### Activation - **Skipped** — An API reference or OpenAPI spec is reachable ```text No API reference or OpenAPI spec was fetched; only MCP and signup pages appear. ``` - **Pass** — An MCP server is documented and well-formed ```text Docs describe mountMcp MCP server with tools, OAuth, JSON-RPC over Streamable HTTP. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path or CLI guide was fetched in this sample. ``` - **Skipped** — SDK packages resolve on their registries ```text No SDK package registry lookup result was supplied for onvibe.run. ``` - **Skipped** — Agent skills are published ```text No agent skills documentation was fetched in this sample. ``` [Full report data](https://www.ax-check.com/onvibe.run/report.json)