# AX Check: rwx.com Checked 2026-11-02. RWX docs and pricing are clear, but agents don't always report price. 21 of 23 checklist items pass, including static, gated-free pricing. Yet only 1 of 2 completed sessions actually surfaced the rates to the user. ## Onboarding needs a login ## Coding sessions Of three independent sessions, one did not finish. Of the two that did, one (Kimi K3) read the pricing page and quoted per-vCPU-second rates, an hourly example, the one-minute minimum, and free credit; the other (Qwen 3.8 Max) explicitly declined to state any price or plan detail. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/128430c7-c829-4e52-b69b-2779167b115f) · [Read transcript](https://www.ax-check.com/rwx.com/sessions/deepseek.json) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The transcript provided contains only the run_meta initialization event (seq 0) with configuration details about the model, sandbox, and execution environment. No subsequent agent actions, tool calls, credential acquisition, or product operations are present in the supplied data to evaluate onboarding. Event 0: ```text Help me build a simple example using RWX. 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 initial run_meta configuration event was supplied in the transcript. There are no subsequent events showing the agent's actual actions, tool calls, responses, or outcomes regarding the RWX product task. This appears to be a data/environment limitation rather than a product or agent issue. Event 0: ```text "promptId":"cmvzscprv00sf0iqzk4tdrof7" ``` #### Suggested Changes None identified in this transcript. ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/3c61825f-89ad-453c-9e5d-a8a7cd22313b) · [Read transcript](https://www.ax-check.com/rwx.com/sessions/kimi.json) Quoted per-vCPU-second rates for each tier, a 16-vCPU General Purpose example (~$4/hr), the 1-minute minimum, free allowances and the $100 new-account credit, all taken from the pricing doc it pulled. (seq 65, seq 52, seq 83) #### End-to-end onboarding - **Onboarding needs a login**: The agent installed the RWX CLI and built a valid example workflow, but never obtained real RWX Cloud credentials. No signup or token-creation flow was performed (it requires an interactive browser step at cloud.rwx.com), so the one attempt to execute the hosted run failed with a 403 Forbidden. No authenticated operation was ever demonstrated. Event 81: ```text Error: Failed to initiate run: Unable to call RWX API - 403 Forbidden ``` Event 83: ```text there's no RWX account or `RWX_ACCESS_TOKEN` in this environment — signup at cloud.rwx.com is an interactive browser flow ``` Event 80: ```text timeout 20 ~/.local/bin/rwx run .rwx/example.yml 2>&1 | head -10 ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No RWX Cloud account or access token available**: Running the example workflow against RWX's hosted runners requires a logged-in CLI session (rwx login) tied to an organization access token. The sandbox had no account or RWX_ACCESS_TOKEN, and creating one requires an interactive browser signup flow the agent could not complete on its own. This is a normal login/credential requirement, not a product defect. Event 81: ```text Error: Failed to initiate run: Unable to call RWX API - 403 Forbidden ``` Event 83: ```text If you provide an access token (export `RWX_ACCESS_TOKEN=...`), I'll launch the example run immediately and report the results URL. ``` - **Docs CLI path argument needs a leading slash**: The first two attempts to pull documentation articles by topic name ('pricing', 'getting-started') failed because the CLI concatenated the base URL and topic without a separator, producing a malformed hostname lookup. The agent self-corrected by prefixing a slash, which is agent usage error rather than a documented bug, but it did cost two failed calls. Event 60: ```text Error: unable to fetch article: Get "https://www.rwx.comgetting-started": dial tcp: lookup www.rwx.comgetting-started on [2606:4700:4700::1111]:53: no such host ``` Event 61: ```text Error: unable to fetch article: Get "https://www.rwx.compricing": dial tcp: lookup www.rwx.compricing on [2606:4700:4700::1111]:53: no such host ``` #### Suggested Changes - **Clarify rwx docs pull argument format in --help output**: The `rwx docs pull
` command silently requires a leading slash (e.g. /pricing) and fails with a confusing DNS-style error when omitted ('www.rwx.compricing'). Add an example with the slash to `rwx docs pull --help` or accept both forms, then verify by running `rwx docs pull pricing` and confirming it resolves instead of erroring. Event 60: ```text Error: unable to fetch article: Get "https://www.rwx.comgetting-started": dial tcp: lookup www.rwx.comgetting-started on [2606:4700:4700::1111]:53: no such host ``` Event 64: ```text ~/.local/bin/rwx docs pull /pricing 2>&1 | head -80 ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/bc5d6fd3-b0c7-43bd-b296-4ca08ed6b03d) · [Read transcript](https://www.ax-check.com/rwx.com/sessions/qwen.json) Gave no pricing figure or plan details. It explicitly declined to report pricing, so it named no cost and no assumptions (seq 21, seq 35) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The agent never located a real RWX product, SDK, or API to authenticate against, so no credential acquisition or authenticated operation occurred. It only checked npm/PyPI package registries and DNS/HTTP reachability of guessed domains, found no live docs/API, and confirmed no RWX-related environment variables existed. It then stopped per instructions rather than attempting onboarding. Event 6: ```text PI_GATEWAY_API_KEY= GIT_CONFIG_KEY_0= ``` Event 21: ```text Credentials**: no RWX-related API key or token is set in this environment (only unrelated `PI_GATEWAY_*` vars). ``` Event 35: ```text No RWX credentials exist in this environment, and you're not providing any. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No discoverable RWX product, SDK, or API**: The agent searched npm, PyPI, and several guessed domains (rwx.dev, api.rwx.dev, docs.rwx.com, api.rwx.com) and found only an empty placeholder npm package, a name-squatted PyPI stub, unresolved DNS for dev/docs/api subdomains, and a 502 on www.rwx.dev. The only resolving domain, rwx.com, is a marketing site with no visible API or SDK. This is an environment/discovery limitation rather than a demonstrated product defect, since the agent could not confirm what 'RWX' the user meant or find any real hosted product tied to that name. Event 12: ```text rwx@0.0.0-alpha.0 | ISC | deps: none | versions: 1 ``` Event 19: ```text curl: (6) Could not resolve host: rwx.dev 000 502 ``` Event 28: ```text https://docs.rwx.com -> curl: (6) Could not resolve host: docs.rwx.com 000 https://api.rwx.com -> curl: (6) Could not resolve host: api.rwx.com 000 ``` Event 33: ```text final:https://www.rwx.com/ code:200 ``` - **No credentials available to attempt authenticated access**: The sandbox environment contained no RWX-related API keys or tokens, only an unrelated PI_GATEWAY_API_KEY. Since the user prompt explicitly said to report if blocked rather than self-serve around this, the agent correctly treated the missing credentials plus unreachable API surface as a stopping point rather than attempting a workaround. Event 6: ```text PI_GATEWAY_API_KEY= GIT_CONFIG_KEY_0= ``` Event 21: ```text no RWX-related API key or token is set in this environment ``` #### Suggested Changes - **Publish a resolvable docs/API subdomain for RWX**: docs.rwx.com and api.rwx.com failed to resolve via DNS, and www.rwx.dev / api.rwx.dev returned 502, while only the bare rwx.com marketing site loaded. If RWX has a real developer product, point a docs or api subdomain to a live endpoint and verify by running the same curl checks the agent did (curl -sS -o /dev/null -w code against the docs/api subdomain) and confirming a 200 with actual content instead of a DNS failure or 502. Event 28: ```text https://docs.rwx.com -> curl: (6) Could not resolve host: docs.rwx.com 000 https://api.rwx.com -> curl: (6) Could not resolve host: api.rwx.com 000 ``` Event 19: ```text curl: (6) Could not resolve host: rwx.dev 000 502 ``` - **Claim or remove the placeholder rwx packages on npm and PyPI**: The npm package 'rwx' is a 225-byte empty placeholder (version 0.0.0-alpha.0) and the PyPI package 'rwx' is a stub described only as 'Read Write eXecute' (version 0.0.1), neither tied to any real product. If RWX is an actual SDK, publish real package content under the 'rwx' name or a clearly branded alternative so a developer running 'npm view rwx' or 'pip index versions rwx' finds working code instead of an empty stub. Event 12: ```text rwx@0.0.0-alpha.0 | ISC | deps: none | versions: 1 ``` Event 19: ```text rwx (0.0.1) Available versions: 0.0.1 ``` ### Task given to each agent Help me build a simple example using RWX. 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 200 for the Markdown Accept header. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt links docs, getting started, CLI reference, CI guide, and AGENTS.md. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt groups links under Documentation, Products, and Company headings. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt lists CLI reference and agent instructions; API, MCP, skills documented elsewhere. ``` - **Pass** — A compact guide representation exists ```text Getting-started page served as Markdown at /docs/getting-started.md and via content negotiation. ``` - **Pass** — A focused guide is directly retrievable ```text Getting-started guide is directly retrievable as Markdown with install, login, and run steps. ``` - **Pass** — Equivalent instructions fit a token budget ```text Markdown guide is 703 tokens, well under the 8000-token budget. ``` - **Pass** — Product-docs links survive format changes ```text Markdown guide retains docs links to CLI, GitHub, and CI workflow pages. ``` - **Pass** — The compact guide is independently actionable ```text Getting-started guide gives concrete steps: brew install, rwx login, tasks.yml, rwx run. ``` - **Pass** — Install and next-step links resolve ```text Install and next-step links (CLI install, GitHub, CI guide) resolve in fetched docs. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text Getting-started page gives concrete steps: install CLI, login, define tasks.yml, run rwx run. ``` - **Pass** — Installation commands are extractable ```text Install commands extractable: brew install rwx-cloud/tap/rwx and Linux curl install shown. ``` - **Pass** — Code examples are available without interaction ```text Code examples shown inline: tasks.yml YAML, rwx run, rwx login, rwx skill install. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text Prerequisites explicit: create RWX Cloud account, rwx login, personal access tokens, organization needed. ``` ### Pricing - **Failed** — Agents identify pricing and its assumptions ```text 2 of 3 sessions were judged on pricing; 1 fell short. Kimi K3: Quoted per-vCPU-second rates for each tier, a 16-vCPU General Purpose example (~$4/hr), the 1-minute minimum, free allowances and the $100 new-account credit, all taken from the pricing doc it pulled. (seq 65, seq 52, seq 83) Qwen 3.8 Max: Gave no pricing figure or plan details. It explicitly declined to report pricing, so it named no cost and no assumptions (seq 21, seq 35) This behavioural item does not affect the fast grade. ``` - **Pass** — Pricing is readable without interaction ```text Pricing page renders full plan and per-second rates as static HTML, no interaction needed. ``` - **Pass** — Prices are stated, not gated ```text Pro $0.00007/vCPU-second, Captain $10 per million results, Enterprise custom all stated. ``` - **Pass** — Pricing units and limits are explicit ```text Docs detail per-vCPU-second tiers, 1-minute minimum, disk, cache, transfer units. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text RWX API reference pages document Dispatches and Vaults endpoints with auth and examples. ``` - **Pass** — An MCP server is documented and well-formed ```text MCP server documented: install via CLI, `rwx mcp serve`, Claude/Cursor/VS Code config. ``` - **Pass** — A CLI install path is documented ```text CLI install documented via Homebrew and Linux binary download with auth steps. ``` - **Skipped** — SDK packages resolve on their registries ```text No registry lookup result for an RWX SDK or packaged CLI package was supplied. ``` - **Pass** — Agent skills are published ```text RWX skill published; installable via `rwx skill install`, Claude marketplace, or npx skills. ``` [Full report data](https://www.ax-check.com/rwx.com/report.json)