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

# Render APIs

Render is a cloud application hosting platform. Its APIs let you manage the full lifecycle of hosted services: creating and updating services, triggering and inspecting deploys, managing custom domains and persistent disks, defining infrastructure with blueprints, and administering workspaces, members, and audit logs. The Render Public API covers 196 operations across the platform, while the smaller Render API focuses on core service and deploy management. Both are secured with bearer tokens against api.render.com.

## For AI agents

An agent can create, update, and delete Render services, trigger and check deploys, attach persistent disks, manage custom domains, validate and sync infrastructure blueprints, and administer workspace members and audit logs across Render's two hosting APIs.

## Scope

Use for: Managing Render cloud hosting: services, deploys, blueprints, custom domains, disks, and workspace administration through Render's APIs.

Not supported:
- payment processing
- email or messaging
- CRM records
- on-prem deployment
- real-time log streaming

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Render Public API | media | 196 | Programmatically list blueprints, validate blueprint. |
| Render API | cloud-infrastructure | 13 | Programmatically create service, list services. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Create, update, or delete a hosted service and trigger a deploy | render-api | The Render API is the compact surface for core service lifecycle and deploy operations. |
| Manage blueprints, custom domains, disks, workspace members, or audit logs | main | The Render Public API exposes the full 196-operation platform, including blueprint validation, infrastructure-as-code, and workspace administration. |
| List services or inspect deploys | render-api | Service and deploy read operations live on the focused Render API; use it when you only need core hosting actions. |

## Cross-API use cases

### Define infrastructure then operate the services

Validate and sync a blueprint with the Render Public API to define resources, then create and deploy the resulting services through the Render API in one workflow.

Example prompt: Call POST /blueprints/validate on the Render Public API, sync the blueprint, then POST /services and trigger a deploy on the Render API

### Provision a service with a custom domain

Create a service and trigger its first deploy with the Render API, then attach a custom domain to it using the Render Public API.

Example prompt: Call POST /services on the Render API, deploy it, then use the Render Public API to associate a custom domain with the new service

### Deploy and audit a workspace

List and update services and deploys with the Render API while reviewing workspace audit logs and member roles through the Render Public API for governance.

Example prompt: Call GET /services on the Render API to inventory deploys, then read audit logs and member roles via the Render Public API

## Why Jentic

- **Setup:** Wiring Render by hand means handling bearer token auth against api.render.com and mapping its service, deploy, blueprint, and workspace endpoints across two APIs yourself. With Jentic One installed, your agent finds and adds the Render APIs from the Jentic directory and stores the token once.
- **Permission scoping:** Render puts resource ids in the URL path, such as /services/{serviceId} and /blueprints/{blueprintId}, so your own rules can pin an agent to reading and deploying one service while excluding deletes or member removals unless you add them.
- **Credential handling:** Your Render bearer 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 the Jentic directory by intent such as 'create a service' or 'validate a blueprint', and Jentic returns the matching Render operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related vendors

- **DigitalOcean** — Alternative cloud hosting platform with app deployment and compute APIs.
- **Heroku** — Platform-as-a-service with a comparable app deploy and service model.
- **Vercel** — Deployment platform for web apps with a deploy-focused API.
- **Amazon Web Services** — Broader cloud infrastructure alternative for compute and hosting.

## FAQ

### What can an AI agent do across Render's APIs?

An agent can manage the whole hosting lifecycle: create, update, and delete services, trigger and inspect deploys, attach persistent disks, manage custom domains, validate and sync infrastructure blueprints, and administer workspace members and audit logs.

### How are the two Render APIs different?

The Render API is a compact surface of 13 operations focused on core service and deploy management. The Render Public API is the full platform with 196 operations, adding blueprints, custom domains, disks, workspace administration, and audit logs.

### Do both APIs share the same authentication?

Yes. Both use a single Render bearer token in the Authorization header against api.render.com, so one credential works across every operation on both APIs.

### Can an agent combine both APIs in one workflow?

Yes. A common pattern is defining resources with a blueprint on the Render Public API, then creating and deploying the resulting services through the Render API, all with the same token.

### Can I limit which Render operations an agent may call?

Yes. With Jentic One, your own rules decide which operations and credentials the agent may use, so destructive actions like deleting a service or removing a workspace member are excluded unless you add them.

### Does Render handle things outside cloud hosting?

No. These APIs are scoped to hosting and workspace management. Payments, messaging, and CRM are not covered, so pair Render with dedicated APIs for those needs.