# AX Check: render.com Checked 2026-09-19. Render's docs, CLI, and pricing are readable without logging in. 19 of 23 checklist items passed: quickstart, CLI install, MCP server, and pricing tables (Hobby $0, Pro $25, Scale $499) are all stated plainly. No llms.txt index exists (404). ## Onboarding needs a login ## Coding sessions Of three independent sessions, one (Kimi K3) completed and reported pricing clearly, listing Free, Starter, Standard, and Postgres tiers with a note to verify current rates on the pricing page. The other two sessions stopped before finishing because the task called for setting up a local project rather than just reading the site. ### DeepSeek V4 Pro [View public run](https://agents.withgauge.com/p/runs/7250fde6-00c8-4e7b-9e9a-51c6c6019c49) · [Read transcript](https://www.ax-check.com/render.com/sessions/deepseek.json) #### End-to-end onboarding - **Onboarding needs a login**: No RENDER_API_KEY was in the sandbox (only PI_GATEWAY_API_KEY/GIT_CONFIG_KEY found), and every live Render API call returned 401 Unauthorized. The agent followed Render's documented onboarding flow, correctly noted auth needs a human (OAuth approval or RENDER_API_KEY), but never obtained a real credential. It only dry-ran a deploy payload locally with a placeholder owner ID, so no authenticated product operation occurred. Event 7: ```text PI_GATEWAY_API_KEY= GIT_CONFIG_KEY_0= ``` Event 80: ```text === https://api.render.com/v1/services === 401 26 {"message":"Unauthorized"} ``` Event 214: ```text "ownerId": "usr-000", ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Render API key available in the sandbox**: The environment scan found no RENDER_API_KEY, and every direct call to the live Render API (owners, services) returned 401 Unauthorized. This is a credentials gap inherent to the test environment (no human present to run OAuth or supply a key), not a product defect — Render's own agent docs require a human to authorize either OAuth or an API key. The agent could only validate its deploy script's JSON payload locally with a placeholder ownerId rather than actually create a service. Event 7: ```text PI_GATEWAY_API_KEY= GIT_CONFIG_KEY_0= ``` Event 80: ```text === https://api.render.com/v1/services === 401 26 {"message":"Unauthorized"} ``` Event 214: ```text "ownerId": "usr-000", ``` #### Suggested Changes None identified in this transcript. ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/739a0728-7aa7-4075-9189-2836f962f252) · [Read transcript](https://www.ax-check.com/render.com/sessions/kimi.json) Final output gives a pricing breakdown (Free/$0, Starter ~$7/mo, Standard ~$25/mo, Postgres ~$6/mo after 90-day trial, bandwidth overage ~$0.10/GB) and flags it as 'ballpark, verify at render.com/pricing', naming plan tiers and trial limits as assumptions. #### End-to-end onboarding - **Onboarding needs a login**: Agent probed for existing credentials and got Unauthorized from Render's hosted API, then explicitly stated it cannot self-serve an API key because signup requires email/GitHub OAuth. It wrote local example files and a deploy script referencing the API but never obtained or used a real API key, so no authenticated operation against the live product occurred. Event 8: ```text {"message":"Unauthorized"} ``` Event 10: ```text it requires an **API key from a Render account**, which I can't create myself (signup needs email/GitHub OAuth). So I can't actually deploy anything. ``` Event 22: ```text To use it: push `render-example/` to a GitHub/GitLab repo, then either connect it in the dashboard (Blueprint) or run `./deploy.sh` with `RENDER_API_KEY` set. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to get a Render API key**: The agent checked the environment and hosted API for existing credentials, found none, and confirmed Render requires account signup (email or GitHub OAuth) to obtain an API key. This is a normal authentication requirement of the product, not a defect — but it fully blocked any live deployment or API call beyond the unauthenticated probe. Event 8: ```text {"message":"Unauthorized"} ``` Event 10: ```text it requires an **API key from a Render account**, which I can't create myself (signup needs email/GitHub OAuth). So I can't actually deploy anything. ``` #### Suggested Changes None identified in this transcript. ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/8a1f5f05-68a5-4003-aa9f-0cc4b5f98830) · [Read transcript](https://www.ax-check.com/render.com/sessions/qwen.json) #### End-to-end onboarding - **Onboarding needs a login**: Agent correctly followed Render's Pi setup contract: installed the render-pi-plugin via `pi install`, which registered MCP in settings.json and added 21 skill folders. But actual OAuth (`/mcp-auth render`) needs a human browser approval, and no RENDER_API_KEY existed in env. Session ends with local-only validation (schema check, node --check, curl to 127.0.0.1) -- no `list_workspaces` or any authenticated Render API call ever occurs, so self-service onboarding was never completed. Event 6: ```text PI_GATEWAY_API_KEY= --- exit --- ``` Event 15: ```text api.render.com -> HTTP 401 ``` Event 76: ```text Only a human can authorize access. State clearly which mode you need. For OAuth, ask the human to approve the browser flow when it opens; do not ask for a token. ``` Event 148: ```text listening on 10000 {"status":"ok","uptimeSeconds":2} ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **Render account auth requires human-in-the-loop approval**: Render's own setup contract states only a human can complete OAuth (browser approval) or supply a RENDER_API_KEY. The sandbox had neither, so the agent could not call any authenticated Render endpoint (e.g. list_workspaces) or deploy the service. This is expected product behavior (a normal login/credential wall), not a product defect; the agent correctly avoided guessing or inventing a key. Event 76: ```text Only a human can authorize access. State clearly which mode you need. For OAuth, ask the human to approve the browser flow when it opens; do not ask for a token. For an API key, ask the human to set `RENDER_API_KEY` in the environment read by the agent process; do not ask them to paste the key into chat. ``` Event 15: ```text api.render.com -> HTTP 401 ``` Event 83: ```text PI_* env: PI_CODING_AGENT PI_GATEWAY_API_KEY PI_MODEL PI_PROVIDER PI_REASONING_LEVEL PI_SESSION_FILE PI_SESSION_ID ``` - **No Git remote configured in sandbox repo**: Render's deploy skill requires a Git-backed repo pushed to GitHub, GitLab, or Bitbucket for both Blueprint and Direct Creation deploy paths. The sandbox repo had no remote, which combined with the auth wall meant only local validation was possible, not a real deploy trigger. Skill/product behavior, not agent error. Event 109: ```text (no remote = empty above) ``` Event 104: ```text If there is no Git remote, stop and ask the user to either: - Create/push a Git remote (can be minimal if only the Blueprint is needed), or - Use the Render Dashboard/API to deploy a prebuilt Docker image (MCP cannot create image-backed services). ``` #### Suggested Changes - **Surface the RENDER_API_KEY fallback earlier in agents/pi.md quick start**: The Quick Start in pi.md leads with OAuth (`/mcp-auth render`) and only documents the API key fallback later under 'MCP and authentication'. For headless/CI sandboxes with no browser or credential store, the API key path is the only viable option. Add a one-line callout inside the numbered Quick Start steps pointing headless agents straight to the API key fallback, then verify by re-running a headless session and confirming the agent reaches that guidance before attempting OAuth. Event 76: ```text There are two authentication modes. Pick one. ``` Event 76: ```text For CI or headless Linux without an unlocked credential store, set `RENDER_API_KEY` before starting Pi instead of using OAuth. ``` ### Task given to each agent Help me build a simple example using Render. 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 · 83/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Failed** — llms.txt provides an actionable documentation index ```text https://render.com/llms.txt returned 404, so no documentation index is published. ``` - **Pass** — Homepage answers Markdown requests ```text Homepage returned text/markdown with 200 when requested with Accept: text/markdown. ``` - **Skipped** — llms.txt provides navigation guidance ```text llms.txt is 404, so its navigation guidance cannot be evaluated. ``` - **Skipped** — llms.txt mentions offered API, MCP, and skills ```text llms.txt is 404, so its mention of API, MCP, and skills cannot be evaluated. ``` - **Pass** — A compact guide representation exists ```text Docs pages serve text/markdown via Accept header and .md suffix, e.g. llm-support and api. ``` - **Pass** — A focused guide is directly retrievable ```text llm-support.md is a focused, directly retrievable agent guide covering skills, MCP, and docs markdown. ``` - **Pass** — Equivalent instructions fit a token budget ```text llm-support guide is 2658 tokens, well under the 8000-token budget. ``` - **Pass** — Product-docs links survive format changes ```text Homepage markdown response retains key docs links like templates, security, and HIPAA. ``` - **Pass** — The compact guide is independently actionable ```text llm-support guide gives install commands, auth setup, skill catalog, and example prompts. ``` - **Pass** — Install and next-step links resolve ```text Fetched install script, skills repo, MCP docs, and API docs all returned 200. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text Docs nav links Framework Quickstarts; llm-support and CLI pages give concrete install and login steps. ``` - **Pass** — Installation commands are extractable ```text CLI page lists Homebrew, WinGet, curl, direct download and build-from-source install commands. ``` - **Pass** — Code examples are available without interaction ```text CLI page shows shell examples for psql, ssh, deploys and GitHub Actions without interaction. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text CLI page documents render login, CLI tokens, and RENDER_API_KEY auth with API key creation link. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page renders full tier and compute tables as static Markdown, no interaction needed. ``` - **Pass** — Prices are stated, not gated ```text Hobby $0, Pro $25, Scale $499, and per-instance compute prices all stated openly. ``` - **Pass** — Pricing units and limits are explicit ```text Tables list RAM, CPU, connection limits, bandwidth and per-GB/per-minute units explicitly. ``` - **Pass** — Agents identify pricing and its assumptions ```text 1 of 3 sessions were judged on pricing; 0 fell short. Kimi K3: Final output gives a pricing breakdown (Free/$0, Starter ~$7/mo, Standard ~$25/mo, Postgres ~$6/mo after 90-day trial, bandwidth overage ~$0.10/GB) and flags it as 'ballpark, verify at render.com/pricing', naming plan tiers and trial limits as assumptions. This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text Render docs describe a public REST API and link an interactive reference plus an OpenAPI 3.0 spec URL. ``` - **Pass** — An MCP server is documented and well-formed ```text Render MCP server documented with hosted URL, transport, OAuth/API-key auth, per-tool setup, and tool catalog. ``` - **Pass** — A CLI install path is documented ```text Render CLI install documented via Homebrew, WinGet, curl script, direct download, and build from source. ``` - **Skipped** — SDK packages resolve on their registries ```text Only an unrelated npm package registry lookup was supplied; no Render SDK or CLI package registry result. ``` - **Pass** — Agent skills are published ```text Render publishes 21 agent skills with install paths via CLI, plugins, and manual copy. ``` [Full report data](https://www.ax-check.com/render.com/report.json)