# AX Check: supademo.com Checked 2026-11-11. Supademo's docs, pricing, and setup are all clear to agents. 21 of 23 checklist items passed, with none flagged for attention. Pricing is posted in plain text with plans, seats, and credit rates spelled out. ## Onboarding needs a login ## Coding sessions All three independent sessions (DeepSeek V4.1 Flash, Kimi K3, Qwen 3.8 Max) completed successfully and read pricing straight from the page. Each quoted plan prices along with their basis, like annual billing, per-creator seats, free viewer seats, the 14-day trial, and AI credit rates, with no login wall encountered. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/26966bc5-7aec-4a6b-87ab-fad71dd1e74c) · [Read transcript](https://www.ax-check.com/supademo.com/sessions/deepseek.json) Quoted prices by plan with their basis: annual vs list price, per-creator vs bundled seats, $50 extra seats, 14-day trial, free viewers, and agent credit tiers with per-call usage assumptions (seq 67, seq 85, seq 86, seq 108) #### End-to-end onboarding - **Onboarding needs a login**: No real Supademo credentials were obtained. The agent only hit the public, unauthenticated Zapier sample-data endpoint (HTTP 200, mock payloads). Every authenticated path (workspace API key check, webhook subscribe, MCP server) went unexecuted since no API key/OAuth token existed, and MCP auth needs an interactive browser flow the agent said it couldn't do headlessly. The example script exits early with a 'key not set' message instead of performing any authenticated operation. Event 60: ```text === sample data: new-lead (no auth) === [{"email":"john@example.com","fullName":"John Doe" ``` Event 59: ```text {"status":"error","message":"Missing or invalid Authorization header"} ``` Event 80: ```text SUPADEMO_API_KEY not set -> skipping. ``` Event 108: ```text MCP auth is an **interactive browser OAuth flow**, which I can't complete headlessly. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No workspace API key or OAuth session available for authenticated Supademo access**: Both real developer surfaces require credentials unavailable in the sandbox: a workspace API key (obtained from a logged-in dashboard) for REST, and interactive browser OAuth for the MCP server. This is a normal login requirement, not a product defect; the agent correctly identified it rather than fabricating a workaround. Event 59: ```text {"status":"error","message":"Missing or invalid Authorization header"} ``` Event 60: ```text === me without key === {"message":"Unauthorized"} [http=401] ``` Event 108: ```text MCP auth is an **interactive browser OAuth flow**, which I can't complete headlessly. ``` #### Suggested Changes - **Add a scoped, non-interactive API key option for MCP automation testing**: MCP docs at docs.supademo.com/customize/mcp-server describe only browser-redirect OAuth for Claude, Cursor, and Copilot connections. For headless agent or CI workflows, consider a non-interactive token path so automation can authenticate without a human present. Verify by confirming a script can call https://mcp.supademo.com/mcp with a static credential and receive a successful 'initialize' response without opening a browser. Event 34: ```text your browser will open to Supademo's login and redirect back after OAuth completes. ``` - **Clarify that the REST developer docs page is Zapier-scoped, not general demo management**: The 'Developer docs' page under data-and-api/developer-docs covers only Zapier triggers (new-lead, demo-view), with no endpoints to create or edit demos. A first-time developer could expect general CRUD. Add a scope note at the top of that page linking to MCP docs for actual demo management, and confirm a new reader understands within seconds that demo editing is MCP-only. Event 34: ```text # Developer docs Developer reference for building on the Supademo Zapier integration: triggers, actions, and the New Lead payload. ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/2058206c-deac-48b6-ab11-314d19984c64) · [Read transcript](https://www.ax-check.com/supademo.com/sessions/kimi.json) Quoted Free (5 demos), Scale $38 per creator, Business $199 and Growth $350 per month. Assumptions named: annual billing, per-creator seats, extras $50/mo, 14-day no-card trial, AI credits billed separately. (seq 19, seq 80, README.md) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: No Supademo account or API key was ever obtained during the session. The agent only called the one endpoint that requires zero auth (GET .../zapier/connect sample payload) and explicitly left the authenticated calls (whoami, webhook subscribe) untested because it had no SUPADEMO_API_KEY. No self-service credential acquisition flow (e.g. signup) was attempted or completed. Event 73: ```text Sample new-lead payload (no auth required): ``` Event 80: ```text I can't run an end-to-end authenticated example because I have no Supademo account/API key — signup and key creation are human steps in their web app. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service credentials obtained for authenticated API calls**: The session never created a Supademo workspace or API key, so the authenticated portion of the example (whoami, webhook subscribe/unsubscribe) was written but never executed against the live API. This is a session/environment limitation (no login flow run), not a product defect — key creation is designed to be self-serve per the docs, but doing so requires a human to complete web signup, which was out of scope for this agent run. Event 80: ```text I can't run an end-to-end authenticated example because I have no Supademo account/API key — signup and key creation are human steps in their web app. ``` Event 73: ```text Set SUPADEMO_API_KEY to run the authenticated calls (whoami, webhook subscribe). ``` - **Public REST API has no demo CRUD endpoints**: Product behavior: the entire documented REST surface is 4 Zapier-oriented endpoints (verify key, subscribe/unsubscribe/sample webhook trigger). There is no API to create, read, or edit a demo, which limits what a developer workflow can accomplish beyond embedding and webhook wiring. Event 39: ```text The API is confirmed live — but it's only 4 endpoints for webhook subscriptions (Zapier-oriented), plus auth check. No demo CRUD. ``` Event 36: ```text GET /api/integration/zapier/me GET /api/integration/zapier/connect POST /api/integration/zapier/connect DELETE /api/integration/zapier/connect ``` #### Suggested Changes - **Add demo-creation/read endpoints to the public REST API**: Current OpenAPI spec at https://supademo.com/openapi.json only exposes auth-check and webhook subscription operations; demo authoring is restricted to the Chrome extension, desktop app, dashboard, or MCP (paid, OAuth). Adding CRUD endpoints for demos would let free-tier developers build real programmatic workflows. Verify by checking that supademo.com/openapi.json lists operations beyond /api/integration/zapier/*. Event 39: ```text The API is confirmed live — but it's only 4 endpoints for webhook subscriptions (Zapier-oriented), plus auth check. No demo CRUD. ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/1cd3d820-333a-456f-b5a1-9db4641ad6fc) · [Read transcript](https://www.ax-check.com/supademo.com/sessions/qwen.json) Priced each plan with its basis: per creator seat, billed annually, free viewer seats, 14-day trial, AI credit rates. The pricing page output was clipped, so not every figure can be checked. (seq 22, seq 111, README.md) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The agent built an embed demo and a REST client for Supademo's API, but never created a workspace account or API key. All authenticated endpoints (verifyKey, subscribe, unsubscribe) were only exercised with no key present, producing a 'Missing API key' client-side error. The agent explicitly states it did not sign up or log in, and left authenticated calls 'wired up and ready for a key' rather than demonstrating a real authenticated operation. Event 104: ```text Supademo API error: Missing API key. Set SUPADEMO_API_KEY (create one at https://app.supademo.com/settings/workspace#api) ``` Event 53: ```text -- me (no key) {"message":"Unauthorized"} [401] ``` Event 111: ```text No Supademo credentials — I didn't create an account. So `--verify`/`--subscribe`/`--unsubscribe` and the MCP server (`mcp.supademo.com/mcp`) are wired up but unexercised; drop in `SUPADEMO_API_KEY` and they run as-is. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to obtain a Supademo API key**: Every authenticated REST call and the MCP server require a workspace API key created inside the app.supademo.com UI behind a human login, or interactive OAuth. This is normal product authentication, not a defect, but it capped the session to unauthenticated endpoints and local file-based examples. Event 30: ```text Authentication is a workspace API key sent as a bearer token; create one at https://app.supademo.com/settings/workspace#api ``` Event 111: ```text No Supademo credentials — I didn't create an account. So `--verify`/`--subscribe`/`--unsubscribe` and the MCP server (`mcp.supademo.com/mcp`) are wired up but unexercised ``` - **Public REST API too narrow for demo lifecycle automation**: The documented REST surface only covers two Zapier/webhook event-trigger paths (sample payload, subscribe, unsubscribe, key verification) — there is no create/edit/list/delete endpoint for demos themselves, so headless demo authoring is not possible via API regardless of credentials. Event 30: ```text [{'url': 'https://app.supademo.com', 'description': 'Production'}]\n['/api/integration/zapier/me', '/api/integration/zapier/connect'] ``` Event 111: ```text the public REST API is only 2 paths scoped to Zapier/webhook triggers — you can't create/edit/list demos over REST ``` #### Suggested Changes - **Add a sandbox or self-service API key for evaluation**: Provide a way to obtain a scoped, short-lived API key without full human login/billing setup (e.g., a public demo workspace key), so developers and automated agents can exercise authenticated endpoints like /api/integration/zapier/me without the current app.supademo.com/settings/workspace#api login wall. Verify by confirming a fresh unauthenticated session can call /api/integration/zapier/me with a self-issued key and get a 200. Event 30: ```text create one at https://app.supademo.com/settings/workspace#api ``` Event 52: ```text {"message":"Unauthorized"} [401] ``` - **Expand the public REST API beyond Zapier event triggers**: The current openapi.json at supademo.com/openapi.json exposes only /api/integration/zapier/me and /api/integration/zapier/connect. Add endpoints for core demo lifecycle operations (create, list, update, delete demos) so developers can automate demo management headlessly, and confirm by checking the same openapi.json lists additional resource paths beyond zapier. Event 30: ```text print(list(d.get('paths',{}).keys())[:60])... ['/api/integration/zapier/me', '/api/integration/zapier/connect'] ``` ### Task given to each agent Help me build a simple example using Supademo. 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: A · 100/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Pass** — Homepage answers Markdown requests ```text Homepage returned text/markdown with Accept: text/markdown, so Markdown negotiation works. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt is a rich index linking docs, API, MCP, skills, pricing and guides. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt groups links under clear headings and gives AI instructions and starting guidance. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt documents the OpenAPI spec, MCP server, and 23 downloadable SKILL.md files. ``` - **Pass** — A compact guide representation exists ```text llms.txt and docs pages are published as Markdown; docs pages offer .md versions. ``` - **Pass** — A focused guide is directly retrievable ```text Quick Start Guide .md gives install, record, edit, share, analyze steps directly. ``` - **Pass** — Equivalent instructions fit a token budget ```text Quick Start Guide Markdown is 1421 tokens, well under the 8000-token budget. ``` - **Pass** — Product-docs links survive format changes ```text Homepage Markdown is supported and retains docs, pricing, and feature links. ``` - **Pass** — The compact guide is independently actionable ```text Quick Start Guide gives concrete steps: install recorder, record, edit, share, analyze. ``` - **Pass** — Install and next-step links resolve ```text Quick Start install links (Chrome extension, desktop download) and doc next-steps fetched successfully. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text Docs quick-start guide gives four concrete steps: install recorder, record, edit, share, analyze. ``` - **Pass** — Installation commands are extractable ```text Quick-start lists Chrome Extension and Mac/Windows desktop app install links with download URLs. ``` - **Pass** — Code examples are available without interaction ```text llms.txt publishes OpenAPI spec URLs and a no-credential sample endpoint returning a payload. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text llms.txt states API key sent as Bearer, created at workspace settings with no sales contact. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page renders plan table with monthly and annual prices in plain text. ``` - **Pass** — Prices are stated, not gated ```text Free $0, Scale $50, Business $249, Growth $450 stated; Enterprise custom. ``` - **Pass** — Pricing units and limits are explicit ```text Seats, demo limits, credits and per-credit rates are explicit per plan. ``` - **Pass** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4.1 Flash: Quoted prices by plan with their basis: annual vs list price, per-creator vs bundled seats, $50 extra seats, 14-day trial, free viewers, and agent credit tiers with per-call usage assumptions (seq 67, seq 85, seq 86, seq 108) Kimi K3: Quoted Free (5 demos), Scale $38 per creator, Business $199 and Growth $350 per month. Assumptions named: annual billing, per-creator seats, extras $50/mo, 14-day no-card trial, AI credits billed separately. (seq 19, seq 80, README.md) Qwen 3.8 Max: Priced each plan with its basis: per creator seat, billed annually, free viewer seats, 14-day trial, AI credit rates. The pricing page output was clipped, so not every figure can be checked. (seq 22, seq 111, README.md) This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text OpenAPI 3.1 spec served at /openapi.json and /openapi.yaml, with auth and endpoints documented. ``` - **Pass** — An MCP server is documented and well-formed ```text MCP server URL, OAuth, client setup, and 23 skills documented on the MCP page. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path documented; only Chrome extension and desktop apps are offered. ``` - **Skipped** — SDK packages resolve on their registries ```text No SDK or package registry evidence supplied for any Supademo developer package. ``` - **Pass** — Agent skills are published ```text 23 downloadable SKILL.md files published, with several fetched and well-formed. ``` [Full report data](https://www.ax-check.com/supademo.com/report.json)