# AX Check: mx.com Checked 2026-10-23. MX docs are solid, but pricing is nowhere to be found Connect Widget and API docs are clear and directly usable in Markdown, but no pricing page was ever fetched or reviewed, so costs remain unknown. ## End-to-end onboarding not demonstrated ## Coding sessions All three independent sessions (DeepSeek V4.1 Flash, Kimi K3, Qwen 3.8 Max) ended without producing any output, so none reached a pricing figure, assumptions, or a working setup to report back. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/d67fee1b-1303-4fb2-9c97-b306817985e3) · [Read transcript](https://www.ax-check.com/mx.com/sessions/deepseek.json) The trace contains no agent messages, so no pricing figure or assumptions were stated. (seq 0) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The transcript supplied contains only a single run_meta initialization event (seq 0) with configuration and sandbox metadata. No actual agent actions, tool calls, credential acquisition, or product operations are present in the data to evaluate. Event 0: ```text Help me build a simple example using MX. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No session activity available to analyze**: Only the run initialization metadata event was provided in the transcript. There are no subsequent agent messages, tool invocations, or results showing what happened when the agent attempted the task, so no concrete obstacles, product behavior, or agent errors can be identified from this data. Event 0: ```text Help me build a simple example using MX. 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. ``` #### Suggested Changes None identified in this transcript. ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/2bb51e90-f81e-42b0-a5c2-2cf4d862b13a) · [Read transcript](https://www.ax-check.com/mx.com/sessions/kimi.json) The agent sent no output, so there's no pricing statement or assumptions to grade. (seq 0) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The transcript provided contains only a single run_meta event describing the session configuration (model, harness, sandbox, pricing). No actual agent actions, tool calls, API requests, or conversation turns are present, so there is no evidence of credential acquisition or any authenticated operation against a real product. Event 0: ```text "type":"run_meta" ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No session activity captured beyond run setup**: The only event in the transcript is the initial run_meta record containing configuration data (model, harness, sandbox digests, pricing). There are no subsequent events showing the agent attempting the MX example, researching pricing, or encountering any product behavior, so no concrete obstacle can be identified from this data. This appears to be a test environment / data capture limitation rather than a product or agent issue. Event 0: ```text "seedPrompt":"Help me build a simple example using MX. 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." ``` #### Suggested Changes None identified in this transcript. ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/caef4e1f-3e04-4ac7-affe-5420b5f191c4) · [Read transcript](https://www.ax-check.com/mx.com/sessions/qwen.json) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The transcript provided contains only the run metadata (model, sandbox, and configuration info) from session initialization. No actual agent actions, tool calls, credential retrieval, or product operations are present in the supplied data to evaluate onboarding. Event 0: ```text Help me build a simple example using MX. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers None identified in this transcript. #### Suggested Changes None identified in this transcript. ### Task given to each agent Help me build a simple example using MX. 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 · 81/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 links product pillars, use cases, developer portal, and docs index. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt organizes content into labeled sections with descriptive links for navigation. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt lists Developer Portal with API docs, SDKs, and integration guides. ``` - **Pass** — A compact guide representation exists ```text docs.mx.com serves Markdown pages, e.g. connect.md and API overview .md, with an llms.txt index. ``` - **Pass** — A focused guide is directly retrievable ```text Connect Widget guide and Platform API introduction are directly retrievable as Markdown. ``` - **Pass** — Equivalent instructions fit a token budget ```text Connect guide is 4026 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 Connect Widget guide gives concrete integration steps, SDK options, session timeouts and use-case setup. ``` - **Pass** — Install and next-step links resolve ```text Fetched docs.mx.com/connect and API reference pages returned 200 with usable content. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text llms.txt links Developer Portal; docs.mx.com/connect is a Connect Widget integration guide with next steps. ``` - **Skipped** — Installation commands are extractable ```text No installation or CLI setup commands appear in the fetched Connect Widget docs. ``` - **Pass** — Code examples are available without interaction ```text Connect docs show inline JSON sample responses for accounts, transactions, account numbers, owners. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text Docs state OAuth registration required before real institutions; widget URL and use_cases prerequisites explained. ``` ### Pricing - **Skipped** — Pricing is readable without interaction ```text Only the homepage was fetched; no pricing page content is available to read. ``` - **Skipped** — Prices are stated, not gated ```text No pricing page was fetched, so no stated or gated prices can be judged. ``` - **Skipped** — Pricing units and limits are explicit ```text No pricing page was fetched, so units and limits cannot be assessed. ``` - **Skipped** — Agents identify pricing and its assumptions ```text No coding session completed with a pricing verdict, so this behavioural item was not measured. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text Platform API reference fetched with environments, auth, and curl request examples. ``` - **Skipped** — An MCP server is documented and well-formed ```text No MCP server documentation found in the fetched MX documents. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path documented in the fetched MX developer pages. ``` - **Skipped** — SDK packages resolve on their registries ```text No SDK package registry lookup result supplied for MX packages. ``` - **Skipped** — Agent skills are published ```text No agent skills published or referenced in the fetched MX documents. ``` [Full report data](https://www.ax-check.com/mx.com/report.json)