Developer tools
Render for AI agents.
Managed auth, ready-made tools.
Check services, review deploys, trigger new deploys and restart services in Render on behalf of each of your users.
About Render
With the Render connector, your agent works in each user’s own Render workspace. It can list services, check their deploys, trigger a new deploy, restart a service or suspend one, using only the tools your project allows.
Render is a cloud platform for hosting web services, static sites, databases and background workers.
Tools
What your agent can do in Render.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Render connection.
-
List services
Readrender_list_servicesList the services in the user's workspace.
-
Get a service
Readrender_get_serviceGet a service's settings and status.
-
List deploys
Readrender_list_deploysList recent deploys of a service and their status.
-
Trigger a deploy
Writerender_trigger_deployStart a new deploy of a service.
-
Restart a service
Writerender_restart_serviceRestart a running service.
-
Suspend a service
Writerender_suspend_serviceSuspend a service so it stops running.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Render, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read services and trigger deploys, and switch off
render_suspend_serviceso it can never stop a service. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example deploys but not service restarts. A call outside them is refused.
Get started
Connect Render
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Render
Each end user authorizes their own Render account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Render account, once. const connection = await agent200 .user("user_123") .connect("render"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Render tools
Name the user, the model and the tools. The model decides which Render tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Did the last deploy of the API service succeed", tools: ["render"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, by connecting their own Render account. Each connection is their own.
-
What access is requested
The connection acts with that user's access to their Render workspace, such as reading services, triggering deploys or restarting a service. Users can revoke the connection later from their Render account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Render connector and how to use it.
Connector: Render, through Agent200. In code: "render". What it does: Check services, review deploys, trigger new deploys and restart services in Render on behalf of each of your users. Page: https://www.agent200.com/connectors/render/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Render's own page, through the authorization link Agent200 returns. Never ask a user for a Render password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: render_list_services, render_get_service, render_list_deploys. Write tools: render_trigger_deploy, render_restart_service, render_suspend_service. Name "render" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/render/framework/claude/ https://www.agent200.com/connectors/render/framework/chatgpt/ https://www.agent200.com/connectors/render/framework/claude-code/ https://www.agent200.com/connectors/render/framework/muse/ https://www.agent200.com/connectors/render/framework/grok-bot/ https://www.agent200.com/connectors/render/framework/openai-dots/ https://www.agent200.com/connectors/render/framework/claude-duet/ https://www.agent200.com/connectors/render/framework/hermes-agent/ https://www.agent200.com/connectors/render/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/render.md
Guides
Use Render with the AI you build on.
Step-by-step setup for Render with a specific model, assistant or agent framework.
-
Render + Claude
How to connect Render to Claude
-
Render + ChatGPT
How to connect Render to ChatGPT
-
Render + Claude Code
How to connect Render to Claude Code
-
Render + Muse
How to connect Render to Muse
-
Render + Grok Bot
How to connect Render to Grok Bot
-
Render + OpenAI Dots
How to connect Render to OpenAI Dots
-
Render + Claude Duet
How to connect Render to Claude Duet
-
Render + Hermes Agent
How to connect Render to Hermes Agent
-
Render + OpenClaw
How to connect Render to OpenClaw
FAQ
Render and Agent200, answered.
Who handles the Render OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Render.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Render connection, never another user's. It cannot reach anything the user or Render has not authorized.
Can I limit what my agent can do in Render?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.