Render Public API
Browse all Render APIs✓ Official Vendor SpecMediaVideo Processingbearer196 EndpointsREST
For Agents
Programmatically list blueprints, validate blueprint. Covers 196 operations with bearer authentication.
Use for: I need to blueprints, I want to validate blueprint, Search for workspace member role, Find all remove workspace member
Not supported: Does not handle payments, communications, or crm - use for media and content only.
Manage everything about your Render services. The API exposes 196 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Render Public API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Render Public 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-public-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-public-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 Public API.
List Blueprints
Validate Blueprint
Update workspace member role
Remove workspace member
Retrieve Blueprint
Disconnect Blueprint
Use Cases
Patterns agents use Render Public API for, with concrete tasks.
★ Media and Content Operations
Use the Render Public API to perform media operations programmatically. The API provides 196 endpoints covering core functionality including list blueprints, validate blueprint, update workspace member role.
Call GET /blueprints to list blueprints
Automated Audit Logs Management
Automate audit logs operations by combining multiple Render Public API endpoints. Agents can validate blueprint and then update workspace member role in a single workflow.
Call POST /blueprints/validate to validate blueprint, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Render Public 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 'list blueprints', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
196 endpoints — manage everything about your render services.
METHOD
PATH
DESCRIPTION
GET
/blueprints
List Blueprints
POST
/blueprints/validate
Validate Blueprint
PATCH
/owners/{ownerId}/members/{userId}
Update workspace member role
DELETE
/owners/{ownerId}/members/{userId}
Remove workspace member
GET
/blueprints/{blueprintId}
Retrieve Blueprint
PATCH
/blueprints/{blueprintId}
Update Blueprint
DELETE
/blueprints/{blueprintId}
Disconnect Blueprint
GET
/blueprints/{blueprintId}/syncs
List Blueprint syncs
GET
/blueprints
List Blueprints
POST
/blueprints/validate
Validate Blueprint
PATCH
/owners/{ownerId}/members/{userId}
Update workspace member role
DELETE
/owners/{ownerId}/members/{userId}
Remove workspace member
GET
/blueprints/{blueprintId}
Retrieve Blueprint
PATCH
/blueprints/{blueprintId}
Update Blueprint
DELETE
/blueprints/{blueprintId}
Disconnect Blueprint
GET
/blueprints/{blueprintId}/syncs
List Blueprint syncs
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Render Public API by hand means handling its bearer token auth against api.render.com and mapping its owner, member, and blueprint endpoints yourself. Through Jentic you install once, import the Render Public API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Render puts the blueprint id in the URL path (/blueprints/{blueprintId}), so a rule can pin your agent to reading and syncing one blueprint. You choose the operations it may call, so deleting a blueprint or removing an owner member is not included unless you add them.
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 'list blueprints' or 'check a blueprint sync', 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 Public API through Jentic.
What authentication does the Render Public API use?
The Render Public 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 list blueprints with the Render Public API?
Yes. Use the GET /blueprints endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Render Public 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 list blueprints through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list blueprints'. Jentic returns the matching Render Public API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Render Public API have?
The Render Public API exposes 196 endpoints covering audit logs, blueprints, custom domains operations.
Can I limit what my agent is allowed to do with the Render Public 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 blueprint id in the URL path (GET /blueprints/{blueprintId} and its syncs), you can pin the agent to reading and syncing a single blueprint. You choose the exact operations it may call, so destructive actions like disconnecting a blueprint (DELETE /blueprints/{blueprintId}) or removing a workspace member are excluded unless you explicitly add them.
GET STARTED