Skip to content

Start building

Integration · Cloud and hosting

AI agents for Render

See Render services, deploys, events and logs, and trigger, roll back or cancel deploys, restart, suspend, resume and scale services, with a Render API key.

Actions
14
Read
7
Write
7

Actions

What your agents can do in Render

14 actions. Each one is a tool your agents can call and a step your workflows can run.

Read 7

Look things up. Nothing changes.

  • List workspaces

    Lists the Render workspaces (owners) the API key can reach, as result.

  • List services

    Lists services (web services, private services, background workers, cron jobs and static sites), filtered by name, type, region, workspace or suspended state.

  • Get a service

    Reads one service by ID (srv-…): name, type, repo, branch, auto-deploy setting, whether it is suspended and why (suspenders), dashboard address, workspace, and serviceDetails.

  • List deploys

    Lists a service's deploys, newest first, optionally only those in one status.

  • Get a deploy

    Reads one deploy of a service: its status, trigger, commit (ID, message, time), image, and when it was created, started and finished.

  • List service events

    Lists a service's recent events, newest first: builds and deploys starting and ending, server failures, restarts, autoscaling, suspensions and more, optionally in a time range.

  • Search logs

    Reads log lines for one or more services (all in the same workspace and region), newest first by default, over the last hour unless a time range is given, filtered by text, level or type.

Write 7

Create, change or send.

  • Trigger a deploy

    Starts a deploy of a service: the latest commit of its branch, or a given commit, optionally clearing the build cache.

  • Roll back to a deploy

    Rolls a service back to an earlier deploy (from "List deploys"): Render skips the build and redeploys that version at once.

  • Cancel a deploy

    Cancels a deploy that is still in progress (not for cron jobs).

  • Restart a service

    Restarts a service's running instances without a new build (not for cron jobs).

  • Suspend a service

    Suspends a service: it stops running and serving traffic (and stops billing for compute) until it is resumed.

  • Resume a service

    Resumes a suspended service, which starts a deploy of its last version.

  • Scale a service

    Sets how many instances a service runs.

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your Render account.

What you enter

  • API key

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Render data

    Ask a question in plain words. The agent can list workspaces, list services or get a service in Render, then answers with what it found.

  • 02

    Let an agent update Render

    Have the agent trigger a deploy or roll back to a deploy in Render as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent Render and Slack: it can list workspaces in Render and post a summary to a Slack channel in the same run.

FAQ

Render and MyDeepAgents

Can MyDeepAgents connect to Render?

Yes. The Render connector has 14 actions: 7 read and 7 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Render?

Paste an API key from your Render account. You'll need: API key. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Render without asking?

Only if you let it. Each of the 7 actions that change data can be set to wait for a person's approval before it runs.

Can I use Render in workflows as well as agents?

Yes. Every Render action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Render to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.