canonical: https://jentic.com/apis/render.com/render-api

# Render API

Render cloud hosting API. The API exposes 13 endpoints secured with bearer authentication.

## For AI agents

Programmatically create service, list services. Covers 13 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for cloud infrastructure only.

## Capabilities

- Create service
- List services
- Get service
- Update service
- Delete service
- Trigger deploy

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create service', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Deploys** — Operations related to Deploys
- **Domains** — Operations related to Domains
- **Environment** — Operations related to Environment
- **Headers** — Operations related to Headers
- **Owners** — Operations related to Owners

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### 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.