AgentsReady
Verified deep dive · Devtools

Render

Run the agent liveReport a change
6 minTime to key
NoNo-human path
2Human gates
7/10Onboarding score
Card before first callEmail verification

Fastest path to a key

  1. human signs up at dashboard.render.com/register (GitHub/GitLab/Google/email)
  2. Email verification
    if email signup: verify email
  3. API key: dashboard.render.com/u/settings#api-keys > create key (account-wide, non-expiring), set RENDER_API_KEY. Or `render login`: browser 'Authorize CLI' generates an expiring CLI token
  4. MCP: Render plugin for Claude Code/Codex/Cursor (OAuth), or `claude mcp add --transport http render https://mcp.render.com/mcp --header "Authorization: Bearer $RENDER_API_KEY"`
  5. set the active workspace (MCP/CLI prompt)
  6. Working API key

Biggest gap

Unscoped, non-expiring, account-wide API keys created only in the dashboard, plus no DCR, mean a human must copy a god-mode key for any non-blessed agent

Worth copying

agents.md tells the agent to keep working while waiting for the human ('Do not stop working while you wait'), references secrets only by env-var name, and explains the OAuth-expiry vs API-key trade-off

Sources (9) · checked 2026-10-11
91Readiness score / 100
L4 Agent-nativeBeats 98% of 1,846 companies
Access20/20
Context20/20
Interfaces32/32
Onboarding13/19
Trust6/9
llms.txt · root
MCP · https://mcp.render.com/mcp
OpenAPI · https://render.com/openapi.json

Biggest gains

  1. +6 Agents can self-register OAuth clients. Support dynamic client registration (RFC 7591) or client ID metadata documents so MCP clients connect in one click.
  2. +3 Public status page. Link a status page so agents can tell outages from bugs.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • PASSllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • PASSMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • FAILAgents can self-register OAuth clients6
  • PASSSelf-serve API keys5
  • PASSFree tier or test mode3
  • PASSAgent manifests4
  • PASSsecurity.txt2
  • FAILPublic status page3

Your fix pack: 3 changes, up to +9 points

Each change is ready to paste, filled in for render.com, with a command to check it worked. Or hand the whole list to your coding agent.

Without client self-registration, every new agent needs a human to create an OAuth app before it can connect. This is the biggest one-click blocker we see.

Where: Your authorization server
Support one of:
1. Client ID metadata documents (CIMD, preferred by the current MCP auth spec): accept a client_id that is an
   https URL, fetch its JSON metadata, and validate redirect_uris against it.
2. Dynamic client registration (RFC 7591): POST /oauth/register returns a client_id for any MCP client.

Don't want to build it? WorkOS AuthKit, Stytch Connected Apps, Clerk and Auth0 all ship MCP-ready OAuth with DCR/CIMD.
Require PKCE (S256), short-lived tokens, and show the user a consent screen with the scopes.

Add the badge to your README

AgentsReady badge for render.com
[![AgentsReady](https://agentsready.dev/badge/render.com)](https://agentsready.dev/c/render.com)