# AX Check: track40.com Checked 2026-09-20. Pricing is clear, but there's no quick machine-readable doc index Pricing shows $12/editor/month with limits stated openly. But there's no llms.txt or Markdown homepage, so agents must parse HTML to find docs. ## Onboarding needs a login ## Coding sessions All three independent sessions (DeepSeek V4 Pro, Kimi K3, Qwen 3.8 Max) completed and reported the same $12/editor/month pricing with matching assumptions on allowances, overage rates, and the 30-day trial. ### DeepSeek V4 Pro [View public run](https://agents.withgauge.com/p/runs/bbfd0f3a-3cf6-4a5d-b22b-aaf6f17d3ce9) · [Read transcript](https://www.ax-check.com/track40.com/sessions/deepseek.json) Final output states $12/editor/month plan with explicit assumptions (viewers free, 30-day trial, per-editor pooled allowances of 100 cards/5000 API calls/etc, overage wallet, enterprise custom pricing). #### End-to-end onboarding - **Onboarding needs a login**: Agent explored Track40's marketing site, docs, and pricing pages, then wrote a Python API client against the documented REST API. It confirmed the API is live by hitting the real hosted endpoint (401 unauthorized without a valid token), but never obtained a real personal access token because minting one requires interactive browser sign-up in the hosted app, which the agent explicitly said it could not complete from the sandbox. No authenticated operation (card creation, card read, etc.) was ever performed against the live API. Event 49: ```text {"error":"unauthorized"} HTTP 401 ``` Event 72: ```text I can't run the example against real data: minting a personal access token requires an interactive browser sign-up at **app.track40.com → Settings → Tokens**. That's a human step I can't complete from this sandbox. ``` Event 47: ```text curl -sS --max-time 10 -w "\nHTTP %{http_code}\n" https://app.track40.com/api/me ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to get an API token**: Track40's API requires a personal access token minted from Settings → Tokens inside the hosted app, which itself requires an interactive account sign-up. This is normal product authentication behavior (not a bug), but it stopped the agent from completing any authenticated call or from validating the example script end-to-end. Event 72: ```text minting a personal access token requires an interactive browser sign-up at **app.track40.com → Settings → Tokens**. That's a human step I can't complete from this sandbox. ``` #### Suggested Changes - **Add a scriptable path to obtain a first API token**: The API docs page (https://track40.com/docs/api/) only describes minting a personal access token via the in-app Settings → Tokens page after interactive browser sign-up. Adding a non-interactive path (e.g., a signup or token-issuance API endpoint) would let developer tooling validate the API end-to-end without a human clicking through the web UI. Verify by scripting a signup plus token mint, then confirming GET /me succeeds without any browser step. Event 41: ```text Create a personal access token in the app under Settings → Tokens . The token starts with t40_ and is shown once at creation; store it like a password. ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/fab58cc6-6e0f-4ff1-acfc-75f309173856) · [Read transcript](https://www.ax-check.com/track40.com/sessions/kimi.json) Final output states $12/editor/month with named assumptions: per-editor pooled allowance (100 cards, 5000 API calls, etc.), overage rates, 30-day trial with no card, and separate custom enterprise pricing. #### End-to-end onboarding - **Onboarding needs a login**: The agent found a real hosted product with a documented HTTP API and confirmed the API is live, but could not self-provision credentials. Email/password signup returned EMAIL_PASSWORD_SIGN_UP_DISABLED, and the only path forward is a browser-based Google/Microsoft OAuth flow the agent cannot complete. No token was ever obtained, so no authenticated write operation against the product was demonstrated -- the agent instead wrote a local script that requires a human to supply a token later. Event 60: ```text {"message":"Email and password sign up is not enabled","code":"EMAIL_PASSWORD_SIGN_UP_DISABLED"} --- {"error":"unauthorized"} ``` Event 68: ```text {"message":"Invalid email or password","code":"INVALID_EMAIL_OR_PASSWORD"} {"message":"Unauthorized","code":"UNAUTHORIZED"} ``` Event 74: ```text sign-up is SSO-only. Email/password registration is disabled server-side (`EMAIL_PASSWORD_SIGN_UP_DISABLED`); new accounts require a Google or Microsoft OAuth flow in a browser, which I can't complete, and without an account there's no `t40_` token. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **SSO-only signup blocks self-service account creation**: Product behavior: Track40's hosted app disables email/password signup and requires Google/Microsoft OAuth via browser, which an unattended agent session cannot complete. This is a normal login/signup requirement, not a product defect, but it fully prevented obtaining a personal access token and running the API example live. Event 60: ```text {"message":"Email and password sign up is not enabled","code":"EMAIL_PASSWORD_SIGN_UP_DISABLED"} ``` Event 68: ```text {"message":"Unauthorized","code":"UNAUTHORIZED"} ``` #### Suggested Changes - **Add a documented API-only or CLI token-minting path for developers without SSO**: On the API reference page (https://track40.com/docs/api/), the only way to get a t40_ personal access token requires first completing browser-based OAuth signup in the app (Settings -> Tokens). Adding a documented path to provision a trial account and token without an interactive browser OAuth flow would let API-first evaluators verify the workflow end-to-end. Check by confirming a fresh account and token can be created via a scripted request rather than a browser redirect. Event 60: ```text {"message":"Email and password sign up is not enabled","code":"EMAIL_PASSWORD_SIGN_UP_DISABLED"} ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/2ba6b2b2-12f5-4097-93dd-2b682a7de1d5) · [Read transcript](https://www.ax-check.com/track40.com/sessions/qwen.json) Final output gives $12/editor/month with explicit assumptions: per-editor allowances (100 cards, 5,000 API calls), overage rates (15¢/card, $1/1,000 calls), 30-day trial, enterprise add-ons — figures tied to named plan/usage basis. #### End-to-end onboarding - **Onboarding needs a login**: Agent never obtained real product credentials. It searched the sandbox for env vars/config, found none, and confirmed the hosted API returns 401 for both no-token and a fabricated bogus token. Personal access tokens can only be minted inside the Track40 app UI (Settings → Tokens), which requires a human to sign up and log in. The agent wrote a script capable of exercising create/read/update/comment operations, but never executed it against the live API with a real token, so no authenticated product operation was demonstrated. Event 66: ```text env | grep -iE "track|t40|TOKEN" ; ls -la /sandbox; find / -maxdepth 3 -iname "*track40*" 2>/dev/null ``` Event 74: ```text {"error":"unauthorized"} HTTP 401 {"error":"unauthorized"} HTTP 401 ``` Event 86: ```text Set TRACK40_TOKEN (mint one in the app: Settings -> Tokens). exit=1 ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to get an API token**: Track40's API requires a personal access token that can only be created inside the app UI under Settings → Tokens, after a human signs up for an account. There is no programmatic signup, trial-token endpoint, or sandbox credential. This is expected product behavior (a normal login/signup wall), not a product defect, but it stopped the agent from running its example end-to-end against the live API. Event 62: ```text Create a personal access token in the app under Settings → Tokens . The token starts with t40_ and is shown once at creation; store it like a password. ``` Event 74: ```text {"error":"unauthorized"} HTTP 401 ``` Event 86: ```text Set TRACK40_TOKEN (mint one in the app: Settings -> Tokens). exit=1 ``` #### Suggested Changes None identified in this transcript. ### Task given to each agent Help me build a simple example using Track40. 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 · 62/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. ``` - **Failed** — llms.txt provides an actionable documentation index ```text https://track40.com/llms.txt returns 404, so no documentation index exists. ``` - **Failed** — A compact guide representation exists ```text No site-published Markdown guide; /llms.txt returns 404 and homepage Markdown unsupported. ``` - **Skipped** — llms.txt provides navigation guidance ```text No llms.txt body exists (404), so navigation guidance cannot be evaluated. ``` - **Skipped** — llms.txt mentions offered API, MCP, and skills ```text No llms.txt body exists (404), so API/MCP/skills mentions cannot be evaluated. ``` - **Pass** — A focused guide is directly retrievable ```text Getting-started page gives concrete steps from sign-up to first card. ``` - **Pass** — Equivalent instructions fit a token budget ```text Getting-started guide is 458 tokens, well under 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 Getting-started guide gives five concrete steps from sign-up to first card. ``` - **Pass** — Install and next-step links resolve ```text Fetched docs, getting-started and API pages all returned HTTP 200. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text Docs index links 'Getting started' with concrete steps from sign-up to first card. ``` - **Skipped** — Installation commands are extractable ```text No installation or CLI commands offered; Track40 is a web app with sign-up flow. ``` - **Skipped** — Code examples are available without interaction ```text No code examples offered; getting-started is UI workflow prose, not code. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text Sign-up creates team as tenant boundary; roles owner/admin/member/guest and per-pipe access stated. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page renders plan, per-editor price and allowances as static text without interaction. ``` - **Pass** — Prices are stated, not gated ```text Standard plan price US$12/editor/month and per-unit overage rates stated openly. ``` - **Pass** — Pricing units and limits are explicit ```text Units explicit: 100 cards, 5,000 API calls, 1,000 automations, 100 AI credits per editor monthly. ``` - **Pass** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4 Pro: Final output states $12/editor/month plan with explicit assumptions (viewers free, 30-day trial, per-editor pooled allowances of 100 cards/5000 API calls/etc, overage wallet, enterprise custom pricing). Kimi K3: Final output states $12/editor/month with named assumptions: per-editor pooled allowance (100 cards, 5000 API calls, etc.), overage rates, 30-day trial with no card, and separate custom enterprise pricing. Qwen 3.8 Max: Final output gives $12/editor/month with explicit assumptions: per-editor allowances (100 cards, 5,000 API calls), overage rates (15¢/card, $1/1,000 calls), 30-day trial, enterprise add-ons — figures tied to named plan/usage basis. This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text Docs API reference page documents HTTP API endpoints, auth, base URL and examples. ``` - **Skipped** — An MCP server is documented and well-formed ```text No MCP server documentation found in fetched Track40 pages. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path documented in fetched Track40 docs. ``` - **Skipped** — SDK packages resolve on their registries ```text No SDK or package registry evidence supplied for Track40. ``` - **Skipped** — Agent skills are published ```text No agent skills published in fetched Track40 pages. ``` [Full report data](https://www.ax-check.com/track40.com/report.json)