# AX Check: developer.toradex.com Checked 2026-09-18. Quickstart docs stall agents; install and pricing details fare better Quickstart pages just say "select your product configuration" with no concrete steps. Install commands and pricing were findable elsewhere on the site. ## End-to-end onboarding not demonstrated ## Coding sessions All three independent sessions completed and reported pricing. Each pulled different figures and framing from the site or general knowledge, from concrete tiered plans to rough per-unit cost estimates with caveats about uncertainty. ### DeepSeek V4 Pro [View public run](https://agents.withgauge.com/p/runs/989b7de6-d661-4794-88f9-5bb9321f1cdf) · [Read transcript](https://www.ax-check.com/developer.toradex.com/sessions/deepseek.json) Final output gives concrete tiered pricing (Maker free/5 devices, Developer $249/mo or $2,500/yr for 50 devices, Enterprise custom, 30-day trial) sourced live from torizon.io/pricing (seq 94, 126) with explicit assumptions like device count and per-device cost caveat. Session findings unavailable. ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/79eb2d51-e6ee-4f49-921b-09fbb223aaa1) · [Read transcript](https://www.ax-check.com/developer.toradex.com/sessions/kimi.json) Final output gives SoM ($30-100+/unit), free Torizon OS, and Torizon Cloud freemium tiers while flagging assumptions ('historically,' 'from general knowledge,' and a caveat that toradex.com pricing page was unreachable so figures should be verified). #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The agent never attempted to obtain or use real Toradex/Torizon Cloud credentials. It only fetched public marketing/docs pages via curl and concluded the product requires physical hardware, then stopped without creating any account, token, or authenticated resource. Event 31: ```text Signing up for a cloud account without any hardware yields an empty dashboard — no meaningful SDK/API workflow to demonstrate. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **Toradex Cloud API requires physical hardware to be useful**: The agent determined via docs review that Torizon Cloud's REST API only becomes meaningful after enrolling a physical Toradex board running the Torizon provisioning agent. This is normal product behavior (hardware-centric IoT platform), not a credential or environment failure, and matches the seed prompt's instruction to stop if there's no actionable hosted workflow. Event 31: ```text Their one hosted product with an API, **Torizon Cloud** (REST API for fleet/device management), only becomes useful after you **enroll a physical device** running the Torizon provisioning agent. There's no sandbox, emulator tier, or trial device pool I can point the API at. ``` - **www.toradex.com pricing page blocked by CloudFront 403**: Direct requests to www.toradex.com/pricing and www.toradex.com/torizon-cloud returned a CloudFront 403 'Request blocked' error, likely due to bot/WAF filtering in the sandbox environment rather than a broken link, preventing the agent from confirming live pricing details. Event 6: ```text

403 ERROR

The request could not be satisfied.

``` Event 29: ```text ERROR: The request could not be satisfied

403 ERROR

The request could ``` #### Suggested Changes - Add a hardware-free sandbox or emulator tier for Torizon Cloud API evaluation: Developers without a physical Toradex SoM currently cannot exercise the Torizon Cloud REST API meaningfully per the agent's docs review; consider a virtual/emulated device enrollment option on the Torizon Cloud Overview page so the API can be evaluated without hardware, and verify by enrolling a virtual device and calling the fleet management API end to end. Event 31: ```text There's no sandbox, emulator tier, or trial device pool I can point the API at. ``` - Unblock www.toradex.com for automated/sandboxed HTTP clients: Requests to www.toradex.com/pricing and www.toradex.com/torizon-cloud return a CloudFront 403 block, preventing pricing confirmation via standard curl requests; check CloudFront WAF rules for this domain and confirm a plain curl GET to those paths returns 200 instead of the blocked-request page. Event 6: ```text Request blocked. We can't connect to the server for this app or website at this time. ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/07b8bc06-a0bb-4444-b4d2-d1730fa5dec1) · [Read transcript](https://www.ax-check.com/developer.toradex.com/sessions/qwen.json) Final output gives a cost figure ('dev kits run roughly a few hundred USD', distributor/volume-tiered) and names basis for Torizon Cloud pricing (free tier vs paid plans scaling by fleet size/features), flagged as general knowledge to verify. #### End-to-end onboarding - End-to-end onboarding not demonstrated: The agent never obtained Toradex/Torizon Cloud credentials and never made an authenticated API call. It only searched local environment variables and package registries, concluded no SDK/account existed, and stopped without attempting self-service signup or any hosted API request. Event 10: ```text GIT_CONFIG_KEY_0=safe.directory ``` Event 16: ```text No SDK/API credentials or accounts exist in this environment (`env` has no Toradex/Torizon keys). ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - No Toradex/Torizon account or API credentials available: The sandbox environment contained no Toradex or Torizon credentials, and the agent had no way to self-register for Torizon Cloud within the session. This is a missing-credentials limitation of the test environment rather than a product defect, since Torizon Cloud requires account signup outside the agent's reach. Event 16: ```text No SDK/API credentials or accounts exist in this environment (`env` has no Toradex/Torizon keys). ``` - Core Toradex workflow requires physical hardware: The agent determined that Toradex's primary product is embedded hardware (Verdin, Colibri, Apalis modules) requiring physical devices to flash and manage, which falls outside a lightweight hosted SDK/API workflow the session was scoped to use. Event 16: ```text Physical hardware — the core workflow is flashing TorizonCore/Yocto onto a real module and deploying to it. There is no device here. ``` - No installable Torizon package found in public registries: The agent checked npm and PyPI for a Torizon-related package to use in place of the CLI, and both lookups failed, reflecting agent-driven investigation rather than a hallucinated or broken product link. Event 14: ```text npm error 404 Not Found - GET https://registry.npmjs.org/torizon-cloud - Not found ``` Event 14: ```text ERROR: No matching distribution found for torizon ``` #### Suggested Changes - Publish a lightweight Torizon Cloud API quickstart usable without hardware: Add documentation or a sandbox/demo mode for the Torizon Cloud REST API that lets a new developer make at least one authenticated call (e.g., listing a demo fleet or device template) without owning physical hardware. Verify by having a fresh account attempt the documented quickstart end-to-end and confirm a successful API response is possible pre-device-provisioning. Event 16: ```text Torizon Cloud (their one hosted product) — has a REST API for fleet/OTA management, but it requires an account, API credentials, and already-provisioned physical devices to act on. None exist here, so there's nothing for an API call to touch. ``` ### Task given to each agent Help me build a simple example using Toradex. 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: D · 35/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 text/markdown Accept header; no Markdown representation served. ``` - Failed — llms.txt provides an actionable documentation index ```text /llms.txt returned the HTML homepage, not a Markdown index of docs. ``` - Failed — llms.txt provides navigation guidance ```text llms.txt body is the HTML homepage, offering no navigational guidance for agents. ``` - Failed — llms.txt mentions offered API, MCP, and skills ```text llms.txt is HTML homepage; it does not mention the offered MCP server or API. ``` - Failed — A compact guide representation exists ```text No site-published Markdown guide: /quickstart.md and /quickstart/6/.md both returned HTML, not Markdown. ``` - Failed — A focused guide is directly retrievable ```text Quickstart pages only say 'Select your product configuration from the menu below' with no concrete first steps. ``` - Failed — The compact guide is independently actionable ```text Quickstart pages only say 'Select your product configuration'; no concrete first steps or commands. ``` - Skipped — Equivalent instructions fit a token budget ```text No site-published compact Markdown guide was retrieved, so token budget cannot be measured. ``` - Skipped — Product-docs links survive format changes ```text Homepage Markdown is unsupported, so link preservation across formats cannot be judged. ``` - Skipped — Install and next-step links resolve ```text Quickstart pages expose no install or next-step links to resolve; only a configuration chooser. ``` ### Onboarding - Failed — Docs lead to a relevant quickstart ```text Quickstart pages only say 'Select your product configuration'; no concrete first steps are shown. ``` - Pass — Installation commands are extractable ```text Install page gives extractable commands: wget setup script, source it, run torizoncore-builder --help. ``` - Pass — Code examples are available without interaction ```text Dockerfile and docker build/run examples shown inline without interaction. ``` - Pass — Prerequisites and auth boundaries are explicit ```text Install page lists prerequisites: Toradex SoM with Torizon, Docker, WSL 2, Bash. ``` ### Pricing - Skipped — Pricing is readable without interaction ```text No pricing page was fetched; homepage shows only hardware and software docs, no prices. ``` - Skipped — Prices are stated, not gated ```text No pricing page was fetched; no prices or gated pricing evidence available. ``` - Skipped — Pricing units and limits are explicit ```text No pricing page was fetched; pricing units and limits cannot be assessed. ``` - Pass — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4 Pro: Final output gives concrete tiered pricing (Maker free/5 devices, Developer $249/mo or $2,500/yr for 50 devices, Enterprise custom, 30-day trial) sourced live from torizon.io/pricing (seq 94, 126) with explicit assumptions like device count and per-device cost caveat. Kimi K3: Final output gives SoM ($30-100+/unit), free Torizon OS, and Torizon Cloud freemium tiers while flagging assumptions ('historically,' 'from general knowledge,' and a caveat that toradex.com pricing page was unreachable so figures should be verified). Qwen 3.8 Max: Final output gives a cost figure ('dev kits run roughly a few hundred USD', distributor/volume-tiered) and names basis for Torizon Cloud pricing (free tier vs paid plans scaling by fleet size/features), flagged as general knowledge to verify. This behavioural item does not affect the fast grade. ``` ### Activation - Pass — An API reference or OpenAPI spec is reachable ```text Toradex docs list a Torizon Cloud API reference page under Torizon Cloud. ``` - Pass — An MCP server is documented and well-formed ```text MCP server documented with remote Streamable HTTP endpoint, tools, and per-client setup. ``` - Pass — A CLI install path is documented ```text Install TorizonCore Builder documents downloading and sourcing the tcb-env-setup script. ``` - Skipped — SDK packages resolve on their registries ```text No Toradex SDK or CLI package registry lookup was supplied in the evidence. ``` - Skipped — Agent skills are published ```text No agent skills documentation for Toradex was fetched. ``` [Full report data](https://www.ax-check.com/developer.toradex.com/report.json)