Skip to content
Scalekit Docs
Talk to an Engineer Dashboard

Connect AI agents to Render

Scalekit connector
Open markdown

The Render connector lets your AI agent act in each user's Render account. Each user connects their own Render access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 205 tools.

Tools
205
What they doRead · write · destructive
100 · 72 · 33100 read72 write33 destructive
Users sign in with

Setup

  1. Install the SDK

    Terminal window
    npm install @scalekit-sdk/node dotenv
  2. Set your credentials

    Add your Scalekit credentials to your .env file. Find values in app.scalekit.com > Developers > API Credentials.

    .env
    SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
    SCALEKIT_CLIENT_ID=<your-client-id>
    SCALEKIT_CLIENT_SECRET=<your-client-secret>
  3. Create the Render connection

    In AgentKit > Connections, create a Render connection. The name you give it is the connection_name your code passes. See Configure connections.

    Console steps with screenshots

    Create a Render API key so Scalekit can manage your services, deployments, and environment variables on your behalf.

    1. Open API Keys in Render account settings

      • Log in to your Render dashboard.

      • Click your workspace name, then Account Settings.

      • Select API Keys from the settings sidebar.

        Render Account settings showing the API Keys panel with existing keys and a Create API Key button

    2. Create a new API key

      • Click Create API Key.
      • Give it a descriptive name (for example, Scalekit) so you can identify it later.
      • Copy the key immediately — Render shows the full value only once.
    3. Add the API key in Scalekit

      • In the Scalekit dashboard, go to AgentKit > Connections > Create Connection. Find Render and click Create.
      • Paste the API key you copied and click Save.
  4. Authorize a user and make your first call

    quickstart.mts
    import { ScalekitClient } from '@scalekit-sdk/node'
    import 'dotenv/config'
    import { createInterface } from 'node:readline/promises'
    const scalekit = new ScalekitClient(
    process.env.SCALEKIT_ENVIRONMENT_URL,
    process.env.SCALEKIT_CLIENT_ID,
    process.env.SCALEKIT_CLIENT_SECRET,
    )
    const actions = scalekit.actions
    const connector = 'render'
    const identifier = 'user_123'
    // Generate an authorization link for the user
    const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
    console.log('Authorize Render:', link)
    const rl = createInterface({ input: process.stdin, output: process.stdout })
    await rl.question('Press Enter after authorizing...')
    rl.close()
    // Make your first call
    const result = await actions.executeTool({
    connector,
    identifier,
    toolName: 'render_blueprints_list',
    toolInput: {},
    })
    console.log(result)
    Terminal window
    npx tsx quickstart.mts

    Each user opens the link once and enters their Render credentials there. If your app already has a user's credentials, add the account from your backend instead, as the console steps above show. See Authorize a user for the full flow and statuses.

Tools

Pass the exact name to execute_tool
Try in PlaygroundRequest a tool
  • render_blueprint_getRetrieve full details for one Blueprint by its ID.Read-only

    Retrieve Blueprint

    Retrieve full details for one Blueprint by its ID. Returns the Blueprint's name, sync status, auto-sync setting, connected repo, branch, render.yaml file path, last sync time, and the list of resources (services, databases, etc.) it manages. Use render_blueprint_get when you already have a Blueprint ID. Use render_blueprints_list to find a Blueprint ID by browsing or filtering.

    Inputs

    blueprint_idstringrequired
    The ID of the Blueprint to retrieve. Render Blueprint IDs use the `exs-` prefix, e.g. exs-cph1rs3idesc73a2b2mg.
  • render_blueprint_syncs_listList the sync runs (deploy history) for a specific Blueprint.Read-only

    List Blueprint Syncs

    List the sync runs (deploy history) for a specific Blueprint. Returns an array of sync records paired with a pagination cursor, each with the sync id, triggering commit id, start/completion times, and state (created, pending, running, error, or success). Use render_blueprint_syncs_list to review a Blueprint's sync history. Use render_blueprint_get for the Blueprint's current overall status.

    Inputs

    blueprint_idstringrequired
    The ID of the Blueprint whose syncs should be listed. Render Blueprint IDs use the `exs-` prefix, e.g. exs-cph1rs3idesc73a2b2mg.
    cursorstring
    Pagination cursor from a previous response. Each returned sync is paired with a cursor value; pass the last one back here to fetch the next page. Omit for the first page.
    limitinteger
    Maximum number of syncs to return in this page of results. Between 1 and 100; defaults to 20.default 20
  • render_blueprints_listList Blueprints connected to your Render workspaces, optionally filtered by owner (workspace) ID.Read-only

    List Blueprints

    List Blueprints connected to your Render workspaces, optionally filtered by owner (workspace) ID. Returns an array of Blueprint records paired with a pagination cursor, each with the Blueprint id, name, sync status, auto-sync setting, repo, branch, render.yaml path, last sync time, and the resources it manages. Use render_blueprints_list to browse or filter across all Blueprints. Use render_blueprint_get to fetch full details for one specific Blueprint by ID.

    Inputs

    cursorstring
    Pagination cursor from a previous response. Each returned Blueprint is paired with a cursor value; pass the last one back here to fetch the next page. Omit for the first page.
    limitinteger
    Maximum number of Blueprints to return in this page of results. Between 1 and 100; defaults to 20.default 20
    owner_idarray
    Filter to Blueprints belonging to one of these Render workspace (owner) IDs. Provide an array of workspace ID strings. If omitted, returns all Blueprints the API key has access to.
  • render_custom_domain_getRetrieve a single custom domain configured on a Render service, identified by its ID or its exact name.Read-only

    Retrieve Custom Domain

    Retrieve a single custom domain configured on a Render service, identified by its ID or its exact name. Returns the domain id, name, domain type (apex or subdomain), public suffix, verification status, and creation time. Use render_custom_domain_get to fetch full details for one specific domain. Use render_custom_domains_list to browse or filter all domains on a service.

    Inputs

    custom_domain_id_or_namestringrequired
    The ID or the exact name of the custom domain to retrieve. Custom domain IDs use the `cdm-` prefix; alternatively, pass the domain's exact name (e.g. www.example.com).
    service_idstringrequired
    The ID of the Render service the custom domain belongs to. Render service IDs use the `srv-` prefix, e.g. srv-abc123def456.
  • render_custom_domains_listList the custom domains configured on a Render service, optionally filtered by name, domain type, verification status, or creation time window.Read-only

    List Custom Domains

    List the custom domains configured on a Render service, optionally filtered by name, domain type, verification status, or creation time window. Returns an array of custom domain records paired with a pagination cursor, each with the domain id, name, domain type (apex or subdomain), public suffix, verification status, and creation time. Use render_custom_domains_list to browse or filter domains on a service. Use render_custom_domain_get to fetch full details for one specific domain by ID or name.

    Inputs

    service_idstringrequired
    The ID of the Render service whose custom domains to list. Render service IDs use the `srv-` prefix, e.g. srv-abc123def456.
    created_afterstring
    Only return custom domains created after this timestamp. Provide an ISO 8601 datetime, e.g. 2021-02-17T08:15:30Z.
    created_beforestring
    Only return custom domains created before this timestamp. Provide an ISO 8601 datetime, e.g. 2021-06-17T08:15:30Z.
    cursorstring
    Pagination cursor from a previous response. Each returned domain is paired with a cursor value; pass the last one back here to fetch the next page. Omit for the first page.
    domain_typestring
    Filter to custom domains of a specific type. Valid values: apex (e.g. example.com), subdomain (e.g. www.example.com).one of apexsubdomain
    limitinteger
    Maximum number of custom domains to return in this page of results. Between 1 and 100; defaults to 20.default 20
    namearray
    Filter to custom domains whose name matches one of these values. Provide an array of exact domain names.
    verification_statusstring
    Filter to custom domains with a specific DNS verification status. Valid values: verified, unverified.one of verifiedunverified
  • render_dedicated_ip_getRetrieve a single dedicated IP set by its ID.Read-only

    Retrieve Dedicated IP Set

    Retrieve a single dedicated IP set by its ID. Returns the dedicated IP set's id, name, description, owner (workspace) ID, region, scoped environment IDs, assigned IPv4 addresses, provisioning status, and creation/update timestamps. Use render_dedicated_ip_get to check a specific set's details, such as polling after render_dedicated_ip_create until status becomes RUNNING and ips is populated. Use render_dedicated_ips_list to browse all sets in a workspace instead.

    Inputs

    dedicated_ip_idstringrequired
    The ID of the dedicated IP set to retrieve, as returned by render_dedicated_ips_list or render_dedicated_ip_create.
  • render_dedicated_ips_listList dedicated IP sets for a Render workspace, optionally filtered to a single environment.Read-only

    List Dedicated IPs

    List dedicated IP sets for a Render workspace, optionally filtered to a single environment. Returns an array of dedicated IP set records, each with its id, name, description, owner (workspace) ID, region, scoped environment IDs, assigned IPv4 addresses, provisioning status, and creation/update timestamps. Use render_dedicated_ips_list to browse all dedicated IP sets in a workspace. Use render_dedicated_ip_get to fetch one specific set by ID.

    Inputs

    owner_idstringrequired
    ID of the Render workspace (team/owner) to list dedicated IP sets for. Find it in your Render workspace settings or via a workspace/owners list endpoint. Example: tea-cjnxpkdhshc73d12t9i0.
    environment_idstring
    Restrict results to the dedicated IP set (if any) scoped to this specific Render environment ID. Excludes workspace-wide dedicated IP sets from the results. Omit to list all dedicated IP sets for the workspace, both workspace-wide and environment-scoped.
  • render_deploy_getRetrieve full details for one deploy of a Render service by its deploy ID.Read-only

    Retrieve Deploy

    Retrieve full details for one deploy of a Render service by its deploy ID. Returns the deploy id, commit or image info, status, trigger, and start/finish timestamps. Use render_deploy_get when you already have a specific deploy ID. Use render_deploys_list to browse or search deploy history first.

    Inputs

    deploy_idstringrequired
    ID of the deploy to retrieve. Example: dep-cq3e6ttumphs73fk1nn0.
    service_idstringrequired
    ID of the Render service the deploy belongs to. Example: srv-c7ff2gp8fa8c73a1lj7g.