Render API
Browse all Render APIsOfficial vendor OpenAPI document · agent-readyCloud InfrastructureComputebearer13 EndpointsREST
For Agents
Programmatically create service, list services. Covers 13 operations with bearer authentication.
Use for: I need to service, I want to services, Search for service, Find all service
Not supported: Does not handle payments, communications, or crm - use for cloud infrastructure only.
Render cloud hosting API. The API exposes 13 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Render API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Render API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frender.com%2Frender-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frender.com%2Frender-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Render API.
Create service
List services
Get service
Update service
Delete service
Trigger deploy
Use Cases
Patterns agents use Render API for, with concrete tasks.
★ Cloud Infrastructure Operations
Use the Render API to perform cloud infrastructure operations programmatically. The API provides 13 endpoints covering core functionality including create service, list services, get service.
Call POST /services to create service
Automated Deploys Management
Automate deploys operations by combining multiple Render API endpoints. Agents can list services and then get service in a single workflow.
Call GET /services to list services, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Render API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'create service', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
13 endpoints — render cloud hosting api.
METHOD
PATH
DESCRIPTION
POST
/services
Create service
GET
/services
List services
GET
/services/{serviceId}
Get service
PATCH
/services/{serviceId}
Update service
DELETE
/services/{serviceId}
Delete service
POST
/services/{serviceId}/deploys
Trigger deploy
GET
/services/{serviceId}/deploys
List deploys
GET
/services/{serviceId}/deploys/{deployId}
Get deploy
POST
/services
Create service
GET
/services
List services
GET
/services/{serviceId}
Get service
PATCH
/services/{serviceId}
Update service
DELETE
/services/{serviceId}
Delete service
POST
/services/{serviceId}/deploys
Trigger deploy
GET
/services/{serviceId}/deploys
List deploys
GET
/services/{serviceId}/deploys/{deployId}
Get deploy
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Render API by hand means handling its bearer token auth against api.render.com and mapping its service and deploy endpoints yourself. Through Jentic you install once, import the Render API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Render puts the service id in the URL path (/services/{serviceId}), so a rule can pin your agent to reading one service and its deploys. You choose the operations it may call, so deleting a service is not included unless you add it.
Credential isolation
Your Render token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a service' or 'list deploys', and Jentic returns the matching Render operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Render API through Jentic.
What authentication does the Render API use?
The Render API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create service with the Render API?
Yes. Use the POST /services endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Render API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create service through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create service'. Jentic returns the matching Render API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Render API have?
The Render API exposes 13 endpoints covering deploys, domains, environment operations.
Can I limit what my agent is allowed to do with the Render API?
Yes. Because you run Jentic One yourself, your own rules decide which Render operations and credentials the agent may use. Since Render puts the service id in the URL path (/services/{serviceId}), you can pin the agent to reading a single service and its deploys with GET /services/{serviceId} and GET /services/{serviceId}/deploys, while leaving write operations out. You choose the operations it may call, so destructive actions like DELETE /services/{serviceId} or POST /services/{serviceId}/deploys are excluded unless you explicitly add them.
GET STARTED