Skip to content
Gauge

ax-check.com

by Gauge

onvibe

onvibe.run

ax-check.com

Checked 18 September 2026

C

53/100

Agents haven’t verified setup

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.

3 fixes to start with

Concrete changes, backed by what we found.

Onboarding

Resolve the blocker that stopped agent setup.

Agents cannot progress through onboarding without human help. Provide an agent-accessible path through authentication and setup.

Docs

Return Markdown when clients request text/markdown.

Homepage returned text/html even when text/markdown was requested; no Markdown representation offered.

Docs

Add links to your product documentation and quickstart in /llms.txt.

https://onvibe.run/llms.txt returns HTTP 404, so no documentation index exists.

Recorded coding sessions

Same task, 3 models, no onvibe.run account. Recorded 18 September 2026 on Pi.

3 recorded · 4m 12s

4m 12s · recorded

Session findings

Select a finding to see it in context.

piv0.84.2
modelQwen 3.8 Maxcwd/sandbox/repo
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.
Thinking…

Let me understand what's being asked. The user wants me to build a simple example using "onvibe." They want to know how pricing works, and whether this product will be easy for me to manage.

First, I need to figure out what "onvibe" is. Let me look at the current environment. It could be a package, a service, or something in the repo. Let me investigate.

Let me start by exploring the current working directory and checking if onvibe is something I know about.

I'll start by investigating what "onvibe" is—checking the repo and any available packages/docs.

$ cd /sandbox/repo && ls -la && echo "---GIT---" && git log --oneline -5 2>/dev/null && echo "---SEARCH onvibe---" && grep -ri "onvibe" . --include="*.md" --include="*.json" --include="*.js" --include="…{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 18 21:43 ..\ndrwxr-xr-x 8 root root 4096 Sep 18 08:00…ctrl+o
cd /sandbox/repo && ls -la && echo "---GIT---" && git log --oneline -5 2>/dev/null && echo "---SEARCH onvibe---" && grep -ri "onvibe" . --include="*.md" --include="*.json" --include="*.js" --include="*.ts" -l 2>/dev/null | head -20

{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 18 21:43 ..\ndrwxr-xr-x 8 root root 4096 Sep 18 08:00 .git\n-rw-r--r-- 1 root root  408 Sep 18 08:00 .gitignore\n---GIT---\n9ebf5fb Initial workspace\n---SEARCH onvibe---\n","type":"text"}]}
$ which npm node pip pip3 2>/dev/null; echo "---NPM onvibe---"; npm view onvibe 2>&1 | head -30; echo "---PYPI---"; pip3 index versions onvibe 2>&1 | head -10{"content":[{"text":"/usr/local/bin/npm\n/usr/local/bin/node\n/usr/local/bin/pip\n/usr/local/bin/pip3\n---NPM onvibe---\nnpm error code E404\nnpm error 404 Not …ctrl+o
{"content":[{"text":"/usr/local/bin/npm\n/usr/local/bin/node\n/usr/local/bin/pip\n/usr/local/bin/pip3\n---NPM onvibe---\nnpm error code E404\nnpm error 404 Not Found - GET https://registry.npmjs.org/onvibe - Not found\nnpm error 404\nnpm error 404  'onvibe@*' is not in this registry.\nnpm error 404\nnpm error 404 Note that you can also install from a\nnpm error 404 tarball, folder, http url, or git url.\nnpm error A complete log of this run can be found in: /sandbox/.npm/_logs/2026-09-18T21_43_15_996Z-debug-0.log\n---PYPI---\nERROR: No matching distribution found for onvibe\n","type":"text"}]}
Thinking…

"onvibe" doesn't exist on npm or PyPI, and there's nothing in the repo about it. Let me check a few more things - maybe it's a scoped package, or maybe there's something in the environment. Let me also check for network access and any documentation.

No results yet. Let me check for scoped package variants, any local config, and network reachability.

$ cd /sandbox/repo && cat .gitignore; echo "---ENV---"; env | grep -iE "onvibe|vibe|api_key|token" | sed 's/=.*/=<set>/' ; echo "---scoped npm variants---"; for p in "@onvibe/sdk" "onvibe-sdk" "onvibe-c…{"content":[{"text":"# Keep generated and vendored files out of source diffs.\n\n# Logs / OS cruft\n*.log\n.DS_Store\n\n# JavaScript / TypeScript\nnode_modules/…ctrl+o
cd /sandbox/repo && cat .gitignore; echo "---ENV---"; env | grep -iE "onvibe|vibe|api_key|token" | sed 's/=.*/=<set>/' ; echo "---scoped npm variants---"; for p in "@onvibe/sdk" "onvibe-sdk" "onvibe-client" "@onvibe/api"; do echo "== $p =="; npm view "$p" version 2>&1 | head -3; done

{"content":[{"text":"# Keep generated and vendored files out of source diffs.\n\n# Logs / OS cruft\n*.log\n.DS_Store\n\n# JavaScript / TypeScript\nnode_modules/\n.next/\ndist/\nbuild/\ncoverage/\n\n# Python\n.venv/\nvenv/\n__pycache__/\n*.py[cod]\n.pytest_cache/\n*.egg-info/\n\n# Rust\ntarget/\n\n# Go / PHP / Ruby vendored deps\nvendor/\n.bundle/\n\n# Java / Kotlin / Scala\n.gradle/\n\n# .NET\nbin/\nobj/\n\n# Elixir\n_build/\ndeps/\n\n# Dart / Flutter\n.dart_tool/\n---ENV---\nPI_GATEWAY_API_KEY=<set>\n---scoped npm variants---\n== @onvibe/sdk ==\nnpm error code E404\nnpm error 404 Not Found - GET https://registry.npmjs.org/@onvibe%2fsdk - Not found\nnpm error 404\n== onvibe-sdk ==\nnpm error code E404\nnpm error 404 Not Found - GET https://registry.npmjs.org/onvibe-sdk - Not found\nnpm error 404\n== onvibe-client ==\nnpm error code E404\nnpm error 404 Not Found - GET https://registry.npmjs.org/onvibe-client - Not found\nnpm error 404\n== @onvibe/api ==\nnpm error code E404\nnpm error 404 Not Found - GET https://registry.npmjs.org/@onvibe%2fapi - Not found\nnpm error 404\n","type":"text"}]}
$ echo "---web check---"; curl -sS -m 10 -o /dev/null -w "%{http_code}\n" https://onvibe.com 2>&1; curl -sS -m 10 -o /dev/null -w "%{http_code}\n" https://onvibe.dev 2>&1; curl -sS -m 10 -o /dev/null -w…{"content":[{"text":"---web check---\ncurl: (28) Operation timed out after 10001 milliseconds with 0 bytes received\n000\n200\n200\n---npm search---\nNo matches…ctrl+o
echo "---web check---"; curl -sS -m 10 -o /dev/null -w "%{http_code}\n" https://onvibe.com 2>&1; curl -sS -m 10 -o /dev/null -w "%{http_code}\n" https://onvibe.dev 2>&1; curl -sS -m 10 -o /dev/null -w "%{http_code}\n" https://onvibe.io 2>&1; echo "---npm search---"; npm search onvibe 2>&1 | head -10

{"content":[{"text":"---web check---\ncurl: (28) Operation timed out after 10001 milliseconds with 0 bytes received\n000\n200\n200\n---npm search---\nNo matches found for \"onvibe\"\n","type":"text"}]}
Thinking…

Interesting. onvibe.dev and onvibe.io return 200. But onvibe.com times out. Let me check what those sites actually return. However, I should be careful - a 200 could be a parking page or a generic error. Let me look at the content.

Actually, wait. Let me reconsider. The npm registry doesn't have onvibe at all. The websites onvibe.dev and onvibe.io return 200. Let me fetch content to understand what these are. But I should be cautious about whether these are real products or just domain-squatting/parking pages.

Let me check the actual content of these sites.

onvibe.dev and onvibe.io respond 200. Let me see what they actually are before assuming anything.

$ for d in onvibe.dev onvibe.io; do echo "==== $d ===="; curl -sS -m 12 "https://$d" 2>&1 | tr -d '\n' | sed 's/<[^>]*>/ /g' | tr -s ' ' | head -c 800; echo; echo; done{"content":[{"text":"==== onvibe.dev ====\n OnVibe — Your music, anywhere Loading OnVibe... (self.__next_f=self.__next_f||[]).push([0]) self.__next_f.push([1,\"…ctrl+o
{"content":[{"text":"==== onvibe.dev ====\n OnVibe — Your music, anywhere Loading OnVibe... (self.__next_f=self.__next_f||[]).push([0]) self.__next_f.push([1,\"1:\\\"$Sreact.fragment\\\"\\n2:I[39756,[\\\"/_next/static/chunks/0mc.xzdwkp~zy.js\\\"],\\\"default\\\"]\\n3:I[37457,[\\\"/_next/static/chunks/0mc.xzdwkp~zy.js\\\"],\\\"default\\\"]\\n4:I[47272,[\\\"/_next/static/chunks/0bnrziukdmij2.js\\\",\\\"/_next/static/chunks/0tkjdmop2g~rh.js\\\"],\\\"PwaInstallPrompt\\\"]\\n5:I[55883,[\\\"/_next/static/chunks/0bnrziukdmij2.js\\\",\\\"/_next/static/chunks/0tkjdmop2g~rh.js\\\"],\\\"Toaster\\\"]\\n6:I[98504,[\\\"/_next/static/chunks/0bnrziukdmij2.js\\\",\\\"/_next/static/chunks/0tkjdmop2g~rh.js\\\"],\\\"Analytics\\\"]\\n7:I[8802,[\\\"/_next/static/chunks/0bnrziukdmij2.js\\\",\\\"/_next/static/chunks/0tkjdmop2g~rh.js\\\",\\\"/_next/static/chunks/0hjwu-2z~6lm_.js\\\"],\\\"MusicApp\\\"]\\n8:I[97367,[\\\"/_next/static/ch\n\n==== onvibe.io ====\n Переход на Telegram window.location.replace(\"https://t.me/onvibe\"); Если перенаправление не произошло, перейдите по ссылке: https://t.me/onvibe \n\n","type":"text"}]}
$ for d in onvibe.dev onvibe.io; do echo "==== $d headers ===="; curl -sS -m 12 -I "https://$d" 2>&1 | grep -iE "server|x-powered|location|content-type" | head; echo "-- try /docs /pricing /api --"; for…{"content":[{"text":"==== onvibe.dev headers ====\nx-powered-by: Next.js\r\ncontent-type: text/html; charset=utf-8\r\nserver: Fly/57f2b87df (2026-09-16)\r\n-- t…ctrl+o
for d in onvibe.dev onvibe.io; do echo "==== $d headers ===="; curl -sS -m 12 -I "https://$d" 2>&1 | grep -iE "server|x-powered|location|content-type" | head; echo "-- try /docs /pricing /api --"; for p in docs pricing api developers; do code=$(curl -sS -m 8 -o /dev/null -w "%{http_code}" "https://$d/$p" 2>&1); echo "  /$p -> $code"; done; done

{"content":[{"text":"==== onvibe.dev headers ====\nx-powered-by: Next.js\r\ncontent-type: text/html; charset=utf-8\r\nserver: Fly/57f2b87df (2026-09-16)\r\n-- try /docs /pricing /api --\n  /docs -> 404\n  /pricing -> 404\n  /api -> 404\n  /developers -> 404\n==== onvibe.io headers ====\nserver: GitHub.com\r\ncontent-type: text/html; charset=utf-8\r\n-- try /docs /pricing /api --\n  /docs -> 404\n  /pricing -> 404\n  /api -> 404\n  /developers -> 404\n","type":"text"}]}
Thinking…

Let me analyze what I found:

  1. onvibe.io — This is a GitHub Pages site that just redirects to https://t.me/onvibe (a Telegram channel). This is not a developer product; it's a redirect to a Telegram page. No SDK/API.

  2. onvibe.dev — This is a Next.js app called "OnVibe — Your music, anywhere". It's a music streaming app (a PWA — "MusicApp", "PwaInstallPrompt"). It's a consumer music player product. The /docs, /pricing, /api, /developers all return 404.

So "onvibe" appears to be:

  • Either a consumer music app (onvibe.dev) — a PWA for listening to music
  • Or a Telegram channel (onvibe.io)

Neither of these is a developer-facing product with an SDK or API that I could build an example against. There's:

  • No npm package (onvibe, @onvibe/sdk, etc. — all 404)
  • No PyPI package
  • No /docs, /api, /developers, /pricing endpoints (all 404)
  • The .dev site is a client-side rendered music PWA with no public developer surface
  • The .io site is a Telegram redirect

Let me do a bit more diligence to be thorough before concluding. Let me check:

  • Is there a public API referenced in the JS bundles of onvibe.dev?
  • Is there any docs subdomain (docs.onvibe.dev, api.onvibe.dev)?
  • Any GitHub org?

The user explicitly said: "If this product has no developer workflow you can act on, say so plainly and stop." and "Stay light: use the hosted product through its SDK or API."

So I need to determine whether there's a developer workflow. Let me do a focused check for API endpoints and docs subdomains. But I should stay light and not go overboard. Let me do one more round of checks.

Let me check:

  1. docs.onvibe.dev / api.onvibe.dev
  2. The JS bundle for any API base URL
  3. GitHub for an "onvibe" org/repo

Actually, let me be careful and efficient. Let me do these checks in parallel.

Both point away from a developer product: onvibe.io just redirects to a Telegram channel (t.me/onvibe), and onvibe.dev is a client-side music-streaming PWA ("Your music, anywhere") with no /docs, /api, /pricing, or /developers. Let me do a final diligence pass for any developer surface before concluding.

$ echo "-- docs/api subdomains --"; for h in docs.onvibe.dev api.onvibe.dev developer.onvibe.dev developers.onvibe.dev; do code=$(curl -sS -m 8 -o /dev/null -w "%{http_code}" "https://$h" 2>&1); echo " …{"content":[{"text":"-- docs/api subdomains --\n docs.onvibe.dev -> 404\n api.onvibe.dev -> 404\n developer.onvibe.dev -> 404\n developers.onvibe.dev -> 404…ctrl+o
echo "-- docs/api subdomains --"; for h in docs.onvibe.dev api.onvibe.dev developer.onvibe.dev developers.onvibe.dev; do code=$(curl -sS -m 8 -o /dev/null -w "%{http_code}" "https://$h" 2>&1); echo "  $h -> $code"; done
echo "-- grep JS bundles for API base / sdk hints --"
curl -sS -m 12 "https://onvibe.dev" 2>&1 | grep -oE '/_next/static/chunks/[a-zA-Z0-9~._-]+\.js' | sort -u | head -6 | while read u; do curl -sS -m 10 "https://onvibe.dev$u" 2>&1 | grep -oiE 'https?://[a-z0-9.-]*onvibe[a-z0-9./_-]*|/api/[a-z0-9/_-]+|api\.onvibe[a-z.]*' ; done | sort -u | head -30

{"content":[{"text":"-- docs/api subdomains --\n  docs.onvibe.dev -> 404\n  api.onvibe.dev -> 404\n  developer.onvibe.dev -> 404\n  developers.onvibe.dev -> 404\n-- grep JS bundles for API base / sdk hints --\n/api/account/tracks/wipe\n/api/admin/entry-keys\n/api/admin/storage-objects\n/api/auth/google/start\n/api/auth/logout\n/api/auth/refresh\n/api/csv-imports/batches\n/api/csv-imports/batches/\n/api/csv-imports/preview\n/api/csv-imports/uploads\n/api/csv-imports/uploads/\n/api/entry-keys/redeem\n/api/external-discovery/youtube\n/api/external-import-jobs/\n/api/external-imports/youtube\n/api/import-policy\n/api/library/events\n/api/library/summary\n/api/me\n/api/playback-state\n/api/playlists\n/api/playlists/\n/api/search\n/api/songs\n/api/songs/\n/api/songs/import\n","type":"text"}]}
$ echo "-- GitHub org/repo search --"; curl -sS -m 10 "https://api.github.com/search/repositories?q=onvibe" 2>&1 | grep -E '"full_name"|"total_count"|"description"' | head -20{"content":[{"text":"-- GitHub org/repo search --\n \"total_count\": 11,\n \"full_name\": \"snowdamiz/onvibe\",\n \"description\": \"A social media p…ctrl+o
echo "-- GitHub org/repo search --"; curl -sS -m 10 "https://api.github.com/search/repositories?q=onvibe" 2>&1 | grep -E '"full_name"|"total_count"|"description"' | head -20
echo "-- npm/gh org 'onvibe' --"; curl -sS -m 8 -o /dev/null -w "github.com/onvibe -> %{http_code}\n" "https://github.com/onvibe" 2>&1
echo "-- robots/sitemap on .dev --"; for p in robots.txt sitemap.xml openapi.json swagger.json .well-known/openapi; do code=$(curl -sS -m 8 -o /dev/null -w "%{http_code}" "https://onvibe.dev/$p" 2>&1); echo "  /$p -> $code"; done

{"content":[{"text":"-- GitHub org/repo search --\n  \"total_count\": 11,\n      \"full_name\": \"snowdamiz/onvibe\",\n      \"description\": \"A social media platform specifically for the vibe coding community—developers and creators who embrace AI-assisted development\",\n      \"full_name\": \"barisha-app/onvibes.online\",\n      \"description\": null,\n      \"full_name\": \"Agure-la/onvibes\",\n      \"description\": \"This Django web application serves as a music catalog, allowing users to manage artists, genres, songs, comments, and likes.\",\n      \"full_name\": \"barisha-app/haber-onvibes\",\n      \"description\": null,\n      \"full_name\": \"itbeard/onvibe-podcast-redirect\",\n      \"description\": null,\n      \"full_name\": \"satybaldyermkan-jpg/Onvibe.kz\",\n      \"description\": null,\n      \"full_name\": \"itbeard/onvibe-redirect\",\n      \"description\": null,\n      \"full_name\": \"ChaitanyaPawar21/codeOnvibes\",\n      \"description\": \"Official Code-on-Vibes website repository containing hackathon schedules, event information, and resources to help participants stay informed and organized.\",\n      \"full_name\": \"rameenft/onvibe-competitor-analysis\",\n      \"description\": null,\n      \"full_name\": \"Hostileca/OnVibeAPI\",\n-- npm/gh org 'onvibe' --\ngithub.com/onvibe -> 200\n-- robots/sitemap on .dev --\n  /robots.txt -> 404\n  /sitemap.xml -> 404\n  /openapi.json -> 404\n  /swagger.json -> 404\n  /.well-known/openapi -> 404\n","type":"text"}]}
Thinking…

Now I have a much clearer picture. Let me analyze:

The /api/* endpoints I found in the onvibe.dev JS bundle are internal application routes for the music PWA itself — things like /api/auth/google/start, /api/me, /api/playlists, /api/songs, /api/search, /api/admin/entry-keys, /api/csv-imports/*. These are the app's own backend routes consumed by its own frontend. They are:

  • Not documented (no /docs, no openapi.json, no swagger.json — all 404)
  • Not a public/documented developer API or SDK
  • They require authentication (Google OAuth) and are internal to the product's own UI

So this is NOT a developer-facing product with a public SDK or API. It's a consumer music app whose internal API routes happen to be visible in the client bundle.

The GitHub search shows "onvibe" matches are all unrelated projects — a vibe-coding social platform, a Django music catalog, podcast redirects, competitor analysis, etc. None of these is an official "onvibe" developer product. There's a github.com/onvibe that returns 200 but that's likely a user profile page (GitHub returns 200 for org/user pages; but there's no clear official SDK).

Let me reconsider the key facts:

  1. No SDK: Not on npm (onvibe, @onvibe/sdk, onvibe-sdk, onvibe-client, @onvibe/api all 404), not on PyPI.
  2. No public API/docs: /docs, /api (root), /developers, /pricing, openapi.json, swagger.json all 404. The /api/* routes found are the app's private internal routes (auth-gated, undocumented).
  3. The two candidate products:
    • onvibe.dev = consumer music-streaming PWA
    • onvibe.io = redirect to a Telegram channel

Neither is a developer product I can build a hosted SDK/API example against.

The user's instructions are explicit:

  • "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."
  • "Let me know if you get blocked."

So I'm blocked. There is no developer workflow (no SDK, no documented public API, no quickstart) for "onvibe." I should say so plainly and stop.

I should also address the specific questions:

  1. How pricing works — I couldn't find any pricing info. /pricing 404s. There's no documented pricing. I should be honest that I found no pricing information. I should NOT fabricate pricing. I noticed /api/admin/entry-keys and /api/entry-keys/redeem and /api/import-policy — suggesting some kind of access/entry-key model, but that's speculation and not published pricing. I should not invent it.
  2. Whether this product will be easy for me to manage — I can't manage what has no developer surface. I should be honest.

I must NOT fabricate an example, pricing, or a manageability assessment for a product that doesn't have a developer workflow. That would be making things up.

Let me be careful and honest here. This is the crux of the task: the honest answer is "there's no developer workflow I can act on; here's what I found; stopping."

Let me verify the github.com/onvibe 200 — is it a real org with a developer SDK? Let me quickly check, to be thorough, since it's the one remaining lead. Actually, GitHub returns 200 even for 404 pages sometimes via the SPA... no, GitHub returns 404 for non-existent users. A 200 means the user/org onvibe exists. Let me check what repos it has. But I should stay light. Let me do one quick check to close this lead responsibly, then conclude.

Actually, let me quickly check github.com/onvibe to see if it's an official product org with an SDK. This is worth one check because it's the last plausible developer surface.

Let me close the last plausible lead — the github.com/onvibe account that returned 200 — before concluding.

$ echo "-- github.com/onvibe identity --"; curl -sS -m 10 "https://api.github.com/users/onvibe" 2>&1 | grep -E '"login"|"type"|"name"|"public_repos"|"blog"|"bio"|"message"' | head{"content":[{"text":"-- github.com/onvibe identity --\n \"login\": \"onvibe\",\n \"type\": \"User\",\n \"name\": null,\n \"blog\": \"\",\n \"bio\": null,\n…ctrl+o
echo "-- github.com/onvibe identity --"; curl -sS -m 10 "https://api.github.com/users/onvibe" 2>&1 | grep -E '"login"|"type"|"name"|"public_repos"|"blog"|"bio"|"message"' | head
echo "-- its repos --"; curl -sS -m 10 "https://api.github.com/users/onvibe/repos?per_page=20" 2>&1 | grep -E '"full_name"|"description"|"language"|"message"' | head -30

{"content":[{"text":"-- github.com/onvibe identity --\n  \"login\": \"onvibe\",\n  \"type\": \"User\",\n  \"name\": null,\n  \"blog\": \"\",\n  \"bio\": null,\n  \"public_repos\": 0,\n-- its repos --\n","type":"text"}]}
Thinking…

The github.com/onvibe account is an empty user account (0 public repos, no name, no bio, no blog). Not a developer product org.

So my conclusion is solid. Let me summarize my findings honestly:

"onvibe" has no developer workflow I can act on. There is:

  • No SDK on npm or PyPI (all 404)
  • No documented public API — /docs, /api, /developers, /pricing, openapi.json, swagger.json all 404
  • The only /api/* routes are the private internal routes of a consumer music PWA (onvibe.dev), auth-gated and undocumented — not a public developer API
  • onvibe.io is just a redirect to a Telegram channel
  • The github.com/onvibe account is empty (0 repos)
  • GitHub search results for "onvibe" are all unrelated third-party projects

Per the user's explicit instruction, I should say so plainly and stop. I should NOT fabricate:

  • An example (can't build against a non-existent SDK/API)
  • Pricing (none published — I won't invent it)
  • A manageability assessment (nothing to manage)

I got blocked. Let me report clearly and concisely, and stop. I'll be honest about the pricing question (no published pricing found) and the manageability question (can't assess/manage — no dev surface).

Let me write a concise, plain report. I won't create any files or code since there's nothing to build against. This is the correct "stop" behavior.

I should be direct and not overstate. Let me note what I checked so the user can trust the conclusion, and offer next steps (e.g., if they have credentials/docs/link for the actual product, or meant a different "onvibe").

Blocked — stopping here as instructed

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.

What I checked

  • Package registries: onvibe, @onvibe/sdk, onvibe-sdk, onvibe-client, @onvibe/api → all 404 on npm; nothing on PyPI.
  • Hosted products behind the name:
    • onvibe.dev → a client-side music-streaming PWA ("Your music, anywhere", Next.js/Fly). /docs, /api, /developers, /pricing, openapi.json, swagger.json → all 404.
    • onvibe.io → just redirects to a Telegram channel (t.me/onvibe).
    • github.com/onvibe → empty user account (0 public repos). GitHub search hits for "onvibe" are all unrelated third-party projects.
  • The only API-looking surface: /api/* routes I found inside the onvibe.dev JS bundle (/api/me, /api/songs, /api/playlists, /api/search, /api/auth/google/start, /api/admin/entry-keys, …). These are the app's own private, auth-gated backend routes consumed by its own frontend — not a documented public API, and there's no OpenAPI spec or docs for them.

Your specific questions

  • How pricing works: I found no published pricing. /pricing 404s and there's no docs page. I won't guess — the only faint hints (entry-keys, import-policy) are undocumented internal routes, not a stated pricing model.
  • Will it be easy for me to manage: I can't give a real assessment, because there's no developer surface to manage — no SDK, no documented API, no keys/console. Anything I said would be made up.

Why I stopped instead of building: Your constraints were to stay light and use the product via its SDK or API. Neither exists publicly, and the only fallback (reverse-engineering the music app's private routes) would mean driving an undocumented, auth-walled consumer app — not a supported developer workflow, and it risks being both fragile and inappropriate.

To unblock, send me one of:

  • The correct product link/docs (maybe it's a different "onvibe" than the music app or the Telegram channel), or
  • An SDK package name / OpenAPI spec / API base URL + credentials, or
  • Confirmation you want me to build against one of the other GitHub "onvibe" projects (e.g. a music-catalog Django app), which I'd then treat as a normal local code task.

AX Fundamentals

23 checks. Open an area for details.

This check is a quick preview. Test more tasks and models with Gauge Agents.

Test your product with Gauge Agents

AX Check by Gauge