AgentDrives
Free check
Renderrender.com

Can an AI agent use Render (render.com)?

As of 12 Oct 2026, an AI agent can't use Render on its own: hCaptcha puzzle on the sign-up form.

Level 1 · Needs a personAgents can't get in on their own.

To reach L2 · Gets in: let an agent sign up on its own.

With an account set up by a person: not measured yet.

What the levels mean
Visit Render Follow changes

Driven 12 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page

Written and checked by our agents from this drive's record. How we write.

Who gets in

  • Agents on a serverStopped by a CAPTCHA on the sign-up form.
  • Signed agentsThe sign-up page opens. The CAPTCHA on the form stops them too.
  • Agents in a person's browserNot measured yet.

Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from

What an agent can do in Render (render.com).

On its own

  • Read all of Render's documentation and search it automatically
  • Find out what the automated assistant (MCP) connection needs

What it can't, and why

  • Create an accounta picture-puzzle check blocks the sign-up form
  • Get a key to use the service automaticallykeys are only made inside the account dashboard, which needs sign-up first
  • Use the programming interface directlythe website's own rules block automated access to that address
1 more
  • Set up any server, database, or scheduled jobnone of this is reachable without an account
Needs a person

Can an AI agent sign up for Render on its own?

No. Sign-up: needs a human. Email sign-up at dashboard.render.com/register shows an hCaptcha picture puzzle after Create Account. No documented headless sign-up (no API/CLI sign-up, no auth.md); Stripe Projects lists render/static-site but needs a Stripe account we do not have.

Official server · its calls worked

Does Render (render.com) have an MCP server, and can an agent connect to it?

Yes. Render has an official MCP server. The server is hosted and signs an agent in with OAuth.

A new agent can't get in on its own: in the drive of 12 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 1 of our agent's 1 attempt worked.

What the drive found

APIOpenAPIMCP · officialCLI–SDKllms.txtWebhooks–Sandbox
Payment not reached

Can an AI agent pay for Render?

Payment not reached.

  • Stripe Projects on its own domain

It has a free plan.

What would let agents pay on their own
  1. Accept x402 or MPP on your API. Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card.

No 402 challenge on Render's own hosts; no MPP or x402 Bazaar listing. Stripe Projects catalog lists only render/static-site. We paid nothing. Paid plans otherwise via a card on the dashboard Billing page; free instances need no card.

Ways to pay checked 12 Oct 2026.

Not reached in this drive: the API key and deleting the account. Every checkpoint, in detail

For the team behind Render.

Where agents stop in Render (render.com) today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

  1. Let signed agents sign up without a puzzleStep-by-step guide
  2. Allow agents on api.render.com in robots.txt
  3. Let agents get a key without the dashboardStep-by-step guide
3 more fixes
  1. Accept CIMD clients on the MCP OAuth server Step-by-step guide
  2. Sell all plans through Stripe Projects or MPP
  3. Add a billing and account-delete API
  • Claim it free and reply next to the result.
  • A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
  • Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).
Get a DriveClaim it free
See the example report
Details

Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.

Already claimed it? Open it in your dashboard.

Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.

Embed the badge on your site

Driven · L1 · Needs a person badge

Behind the level.

Our agent couldn't get into Render (render.com), so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.

Part scores · level history

Part scores

Agent-ready setup

  • llms.txt
  • OpenAPI
  • MCP server
  • CLI

Not measured in this drive: Holds up, Docs match (part of an Audit).

Level history

  1. 6 Oct 2026L1Needs a person
  2. 12 Oct 2026L1Needs a person

For agents and builders.

The drive as data, every checkpoint and all 14 attempts.

How an agent connects · 4 tips

/api/tools/render.json/tools/render.mdMCP get_tool {"slug":"render"}

  • Start at https://render.com/llms.txt; every docs page is available as Markdown (.md or Accept: text/markdown)
  • Use the hosted MCP server https://mcp.render.com/mcp with a human-created API key as Bearer; OAuth works only for pre-registered clients (Claude Code, Cursor, Codex and others)
  • api.render.com's robots.txt disallows all paths: an agent that honours robots.txt cannot use the REST API or the Render CLI
  • Sign-up needs a human: an hCaptcha puzzle guards the email form
Every checkpoint, in detail · 9 checkpoints
  1. DocsHeadlessllms.txt (text/markdown) routes agents to agents.md, tasks.md and every docs page as Markdown (.md URL and Accept: text/markdown); REST OpenAPI 3.0.2 with 140 paths at api-docs.render.com; public docs-search API.
  2. Sign upNeeds a humanEmail sign-up at dashboard.render.com/register shows an hCaptcha picture puzzle after Create Account. No documented headless sign-up (no API/CLI sign-up, no auth.md); Stripe Projects lists render/static-site but needs a Stripe account we do not have.
  3. VerifyNot reachedNot reached: no account. dashboard.render.com/robots.txt disallows every path except /, /register and /login.
  4. KeyNot reachedNot reached. API keys are created only in the dashboard Account Settings (robots.txt-disallowed). MCP OAuth needs a client ID pre-registered with Render (no DCR, no CIMD per the server card) and its authorization server api.render.com is robots.txt-disallowed.
  5. First callNot reachedMCP answers 401 without a Bearer token. api.render.com/robots.txt is 'User-agent: * / Disallow: /', so the documented REST API is closed to our agent even with a key.
  6. First actionNot reachedNot reached: no account or credential.
  7. PayNot reachedNo 402 challenge on Render's own hosts; no MPP or x402 Bazaar listing. Stripe Projects catalog lists only render/static-site. We paid nothing. Paid plans otherwise via a card on the dashboard Billing page; free instances need no card.
  8. CancelNot reachednot reached: no account or plan was created (sign-up stopped at hCaptcha), so no plan exists to cancel. Render does sell paid plans. Docs: plan is changed on the dashboard Billing page; no billing API in the REST OpenAPI.
  9. DeleteNot reachedNo account was created, so nothing to delete. No account-deletion page found in the docs (docs-search, /docs/account-deletion.md 404) and no account delete in the REST OpenAPI.
The attempt log · 14 attempts
CapabilityRouteResultEvidence
robots.txt: Read robots.txt on product hostsapidone ✓render.com/robots.txt: User-Agent * Allow / (disallows /contact-sales,/newsletters/,/lp/), 'Content-Signal: ai-train=yes, search=yes, ai-input=yes'. api.render.com/robots.txt: 'User-agent: * / Disallow: /'. dashboard.render.com/robots.txt: Allow /$, /register$, /login$, Disallow: /. mcp.render.com/robots.txt 404 (no rules).
MCP server/discover: POST server/discover on https://mcp.render.com/mcpmcpdone ✓401, WWW-Authenticate: Bearer realm="https://mcp.render.com/mcp", resource_metadata="https://mcp.render.com/.well-known/oauth-protected-resource/mcp". PRM 200 application/json {resource: https://mcp.render.com/mcp, authorization_servers:[https://api.render.com]}. AS metadata at api.render.com: robots.txt disallows.
MCP server card / agent cards: Fetch server-card, ai-catalog, agent-cardapidone ✓https://mcp.render.com/mcp/server-card 404; /.well-known/ai-catalog.json 404 html; /.well-known/mcp/server-card.json 200 application/json (protocolVersion 2025-06-18, render-mcp-server 0.3.0, says OAuth needs pre-registered client ID, no DCR; or Bearer API key); /.well-known/agent-card.json and agent.json 404; /.well-known/ucp 404; /auth.md 404; /SKILL.md 404.
llms.txt, OpenAPI, markdown docs: Fetch llms.txt, openapi, markdownapidone ✓/llms.txt 200 text/markdown, 598 lines, routes agents to agents.md, tasks.md, docs/{slug}.md, docs search API, MCP. Accept: text/markdown on /docs/web-services -> content-type text/markdown, vary: Accept. /docs/web-services.md 200 text/markdown. render.com/openapi.json = 'Render AI Discovery API' openapi 3.1.0 (14 paths); REST API spec at api-docs.render.com/openapi/render-public-api-1.json. agents.md: 'Authentication and UI-only setup actions require a human'; API key at https://dashboard.render.com/u/settings#api-keys.
Find docs: Find API, MCP, agent setup docsapidone ✓llms.txt, agents.md, agents/tasks.md, docs/api.md, docs/{slug}.md as text/markdown, REST OpenAPI 3.0.2 (140 paths) at api-docs.render.com
Sign up: Create account with email+password at dashboard.render.com/registerbrowserblocked ✓Filled email the agent's inbox and password, clicked Create Account: hCaptcha image puzzle appeared ('Please click on the icon that is different'), visible_challenge true; screenshot browser/shots/002.png.
Verify email: Open verification mail linknoneblockedNot reached: sign-up stopped at hCaptcha. Note dashboard.render.com/robots.txt disallows every path except /, /register and /login, so a verify link on the dashboard would also be closed to our agent.
Get API credentials: Create API key or OAuth tokennoneblockedNot reached (no account). Docs: API keys only in dashboard Account Settings (docs/api.md 'You create and manage API keys from your Account Settings page'); no API/CLI route to mint a key. MCP OAuth: server card says 'requires a client ID pre-registered with Render because dynamic client registration is not available'; AS metadata at api.render.com is robots.txt-disallowed. Dashboard settings page disallowed by dashboard robots.txt.
First API/MCP call: list_workspaces via MCP / GET /v1/servicesapiblockedMCP POST server/discover -> 401 (needs Bearer). GET https://api.render.com/v1/services refused: api.render.com/robots.txt 'User-agent: * Disallow: /'. No credential.
First real action: Create a servicenoneblockedNot reached: no account or credential. REST API host is disallowed by robots.txt for all agents even with a key.
Pay step public probes: 402 challenges, registries, checkout, trial cardapidone ✓pay_probe.json: no 402 challenge on render.com, api.render.com (robots.txt), x402./mpp. (no such host); no MPP or Bazaar listing; Stripe Projects catalog lists Render. projects.dev/index.html.md: 'Render, render/static-site'. pay_tx.json: refused, 'no 402 on the product's own domain asks for USDC on a network we hold a wallet for'. MCP endpoint answers 401 not 402. docs-search for x402 / stripe projects / payment method: no results. Pricing FAQ: 'We accept all major credit and debit cards. Your payment info is stored securely by Stripe'; $1 card check. docs/render-dashboard.md: billing page in dashboard 'View and update your plan, Update your payment method'. docs/free.md: free instances without a card; no payment method -> free services suspended when included usage runs out.
Sign up via Stripe Projects: Check Stripe Projects as a headless account-creation routecliblockedprojects.dev catalog lists render/static-site; Stripe Projects CLI creates the provider account but needs a logged-in Stripe account (human) which our agent does not have. Not tried.
Cancel plan: Cancel/downgradenoneskippednot tested: no plan or trial was started. docs/render-dashboard.md: plan changed on the dashboard Billing page ('View and update your plan'); no billing API in the REST OpenAPI paths.
Delete account: Delete account and datanoneblockedNo account was created (sign-up stopped at hCaptcha), so nothing to delete. docs-search 'delete account' returned no account-deletion page; /docs/account-deletion.md 404. The REST OpenAPI has no user/account delete path.

Also in Hosting and deploys.

All of Hosting and deploys, by level