# AX Check: cloudhq.net Checked 2026-09-18. Pricing page is clear, but agents still disagree on the numbers Prices are stated plainly on the page (Free $0, Premium $149/yr, Business $399/yr), yet only 2 of 3 agent sessions landed on consistent figures. ## End-to-end onboarding not demonstrated ## Coding sessions All three sessions completed. Kimi K3 correctly scraped Premium at $79/year per user with billing basis stated. DeepSeek V4 Pro reported different per-app price ranges and flagged its own pricing assumptions. Qwen 3.8 Max gave up entirely, saying it could not determine pricing. ### DeepSeek V4 Pro [View public run](https://agents.withgauge.com/p/runs/8034d978-d266-4335-90be-0b408c606ee9) · [Read transcript](https://www.ax-check.com/cloudhq.net/sessions/deepseek.json) Final output gives price ranges ($1.99–$69.90 per app, Free/Premium $14.90/Business $39.90 plans) and flags the assumption that pricing is 'per-user, per-app' based on JSON-LD offer data (seq 105). #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The agent never attempted to obtain or use product credentials. It only crawled public marketing/support pages, npm, PyPI, and GitHub search to look for a developer API/SDK, found none, and stopped per the seed prompt's explicit instruction to halt if there's no developer workflow to act on. No signup, API key request, or authenticated call was ever made. Event 105: ```text CloudHQ has no developer workflow I can act on. ``` Event 105: ```text No public REST API, SDK, or webhooks ``` #### Hallucinated URLs - **Guessed developer/API subdomains that failed**: The agent guessed several plausible developer-facing URLs (developer, api subpaths, and a developers subdomain) that it invented based on common conventions rather than any documented link. These returned 404 or connection failure, and the agent did not rely on them further, instead pivoting to search engines and code registries. Event 25: ```text === https://www.cloudhq.net/developer === 404 https://www.cloudhq.net/developer === https://developers.cloudhq.net === 000 https://developers.cloudhq.net/ ``` Event 25: ```text === https://www.cloudhq.net/api === 404 https://www.cloudhq.net/api ``` #### Blockers - **No developer API, SDK, or webhook surface exists for CloudHQ**: This is a product-level limitation, not a test-environment or agent-error issue. CloudHQ is a catalog of ~95 GUI-driven Gmail/Google Workspace/Chrome extensions configured by clicking, not a product with a programmatic API. The agent verified this by checking the marketing site, support KB, sitemap, npm, PyPI, and GitHub, finding only unrelated API mentions (OpenAI's own API key, Google's Workspace admin API for enabling third-party access), with no CloudHQ REST API, SDK, or webhook documented anywhere. Event 105: ```text No public REST API, SDK, or webhooks - No developer docs (only marketing pages + a support WordPress site) - No package on npm or PyPI named "cloudhq" - No official GitHub org with an SDK — one repo is just a static marketing page ``` Event 105: ```text CloudHQ is a GUI/extension product: you install add-ons from the Chrome Web Store / Google Workspace Marketplace and configure them by clicking. There's no programmatic surface to build a "simple example" against. ``` #### Suggested Changes - **Publish or link a discoverable API/developer reference if one exists**: Searches of the marketing site, sitemap, support.cloudhq.net search, npm, PyPI, and GitHub found no developer documentation, only tangential hits like OpenAI API key setup and Google Workspace admin API checks. If an API exists, link it from the main nav/footer so it's discoverable without guessing subdomains. Verify by searching support.cloudhq.net for "API" and confirming it surfaces real developer docs, not unrelated articles. Event 61: ```text How can I use my own OpenAI API key? ``` Event 105: ```text No developer docs (only marketing pages + a support WordPress site) ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/0a64db5e-d294-48c7-b6c5-51c2a4d5f1f4) · [Read transcript](https://www.ax-check.com/cloudhq.net/sessions/kimi.json) Final output gives Premium at $79/year per user with billing basis stated (per-user, annual) plus Free/Business/Enterprise tiers scraped from the live pricing page (seq 26-37). #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: Agent never obtained or used product credentials. It determined CloudHQ has no public API/SDK and stopped without attempting sign-up, API key retrieval, or any authenticated operation. Event 45: ```text No public API or SDK. `/api` and `/developers` on their site return 404, `api.cloudhq.net` just redirects to the marketing site, and there are no packages on npm. ``` Event 45: ```text this product has no developer workflow I can act on, so I'm stopping here rather than building an example. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No public developer API or SDK exists for CloudHQ**: This is a product limitation, not agent error or missing credentials. The agent checked standard developer entry points (/api, /developers, a dedicated developer subdomain, npm registry) and found no programmatic surface, only a web UI and browser-extension-based OAuth flows for end users. Event 20: ```text == https://www.cloudhq.net/api 404 -> == https://www.cloudhq.net/developers 404 -> == https://developer.cloudhq.net 000 -> == https://api.cloudhq.net 301 -> https://api.cloudhq.net/g_suite ``` Event 29: ```text npm error 404 Not Found - GET https://registry.npmjs.org/cloudhq - Not found ``` Event 45: ```text No developer docs, API keys, or CLI. Access is via interactive OAuth in a browser — not something scriptable or automatable as a hosted API. ``` #### Suggested Changes - **Publish a developer API or SDK entry point if one exists internally**: If CloudHQ has any programmatic access beyond the consumer web UI and Chrome extensions, surface it at a discoverable path such as /api or /developers on www.cloudhq.net (both currently 404) or document it under api.cloudhq.net (which currently just redirects to the marketing g_suite page). Verify the fix by confirming those URLs return actual documentation instead of 404/redirect. Event 20: ```text == https://www.cloudhq.net/api 404 -> == https://www.cloudhq.net/developers 404 -> ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/ff8fd17b-d8d5-497f-a62b-e2eb03830f6a) · [Read transcript](https://www.ax-check.com/cloudhq.net/sessions/qwen.json) Final output explicitly states pricing is unknown and refuses to guess ('I can't tell you how pricing works') — no figure or assumptions given at all. #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: Agent never obtained or used any CloudHQ credentials. It searched npm/PyPI for a CloudHQ SDK, found nothing, hit 404s on cloudhq.com/docs and cloudhq.com/pricing, and then stopped without attempting any authenticated operation. Event 16: ```text npm error 404 Not Found - GET https://registry.npmjs.org/cloud-hq - Not found ``` Event 31: ```text No SDK or API access: There is no `cloudhq` package on npm or PyPI (checked `cloudhq`, `cloud-hq`, `@cloudhq/sdk` — all 404). No API credentials, docs, or references exist in this workspace either. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No discoverable CloudHQ SDK, API, or documentation**: Agent searched npm and PyPI for a CloudHQ package under multiple plausible names and found nothing, then found cloudhq.com is a marketing site whose /docs and /pricing paths return 404 and docs.cloudhq.com fails to resolve. This is a product/documentation discoverability issue rather than an agent error or missing credentials — the agent could not even locate a starting point for a developer workflow, so it correctly stopped rather than guessing. Event 16: ```text ERROR: No matching distribution found for cloudhq ``` Event 21: ```text npm error 404 Not Found - GET https://registry.npmjs.org/@cloudhq%2fsdk - Not found ``` Event 29: ```text 404 404 000 Command exited with code 6 ``` #### Suggested Changes - **Publish an SDK package under a discoverable name on npm and PyPI**: Searches for cloudhq, cloud-hq, and @cloudhq/sdk on both npm and PyPI all returned 404. Publish an official package under one of these expected names so `npm view cloudhq` or `pip index versions cloudhq` succeeds, and verify by re-running those exact commands. Event 16: ```text npm error 404 Not Found - GET https://registry.npmjs.org/cloudhq - Not found ``` Event 21: ```text npm error 404 Not Found - GET https://registry.npmjs.org/@cloudhq%2fsdk - Not found ``` - **Fix or add a working docs/pricing path on cloudhq.com**: Both cloudhq.com/docs and cloudhq.com/pricing return HTTP 404, and docs.cloudhq.com does not resolve at all. Add a live developer documentation and pricing page reachable from the main site, and verify by curling https://cloudhq.com/docs and https://cloudhq.com/pricing for a 200 response. Event 29: ```text 404 404 000 Command exited with code 6 ``` ### Task given to each agent Help me build a simple example using CloudHQ. 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: B · 80/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 offered. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt lists sync/backup products, key URLs, app catalog, and support links. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt groups content under headings with descriptive links to wizards, apps, and policies. ``` - **Skipped** — llms.txt mentions offered API, MCP, and skills ```text llms.txt describes sync products and browser extensions but mentions no API, MCP, or skills. ``` - **Pass** — A compact guide representation exists ```text llms.txt fetched as text/markdown, a compact standalone guide covering sync, apps, and key URLs. ``` - **Pass** — A focused guide is directly retrievable ```text llms.txt is directly retrievable at cloudhq.net/llms.txt with 200 and markdown content. ``` - **Pass** — Equivalent instructions fit a token budget ```text llms.txt is 13232 tokens but far under 40% of the 13008-token HTML homepage extraction. ``` - **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 ChatGPT Sidebar guide gives three concrete steps: highlight text, pick prompt, copy response. ``` - **Pass** — Install and next-step links resolve ```text Sign-up and support links fetched successfully; llms.txt links resolve to live pages. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text llms.txt links Getting Started and support guides; ChatGPT Sidebar guide gives 3-step quickstart. ``` - **Skipped** — Installation commands are extractable ```text No install commands; product is hosted service and browser extensions, not a CLI/SDK. ``` - **Pass** — Code examples are available without interaction ```text ChatGPT Sidebar guide shows concrete steps and prompt examples without interaction. ``` - **Skipped** — Prerequisites and auth boundaries are explicit ```text No API auth or prerequisites documented; product uses OAuth signup, not API keys. ``` ### Pricing - **Failed** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 1 fell short. DeepSeek V4 Pro: Final output gives price ranges ($1.99–$69.90 per app, Free/Premium $14.90/Business $39.90 plans) and flags the assumption that pricing is 'per-user, per-app' based on JSON-LD offer data (seq 105). Kimi K3: Final output gives Premium at $79/year per user with billing basis stated (per-user, annual) plus Free/Business/Enterprise tiers scraped from the live pricing page (seq 26-37). Qwen 3.8 Max: Final output explicitly states pricing is unknown and refuses to guess ('I can't tell you how pricing works') — no figure or assumptions given at all. This behavioural item does not affect the fast grade. ``` - **Pass** — Pricing is readable without interaction ```text Pricing page renders plan tiers and prices directly in fetched HTML, no interaction needed. ``` - **Pass** — Prices are stated, not gated ```text Prices stated: Free $0, Premium $149/yr, Business $399/yr for 3 users, Enterprise contact. ``` - **Pass** — Pricing units and limits are explicit ```text Units explicit: per year, per user, 3 users, $79/additional user, file size limits. ``` ### Activation - **Skipped** — An API reference or OpenAPI spec is reachable ```text No API reference or OpenAPI spec appears in the fetched cloudHQ pages. ``` - **Skipped** — An MCP server is documented and well-formed ```text No MCP server is documented anywhere in the fetched cloudHQ content. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path is documented; cloudHQ is a hosted service and browser extensions. ``` - **Skipped** — SDK packages resolve on their registries ```text No SDK or developer package registry lookup was supplied for cloudHQ. ``` - **Skipped** — Agent skills are published ```text No agent skills are published or mentioned in the fetched cloudHQ pages. ``` [Full report data](https://www.ax-check.com/cloudhq.net/report.json)