canonical: https://jentic.com/apis/urlbox.io/urlbox

# Urlbox API

Urlbox is a website screenshot and rendering API. It allows you to capture screenshots, generate PDFs, and render web pages in various formats including PNG, JPEG, WebP, AVIF, SVG, PDF, HTML, MP4, WebM, and Markdown. The API exposes 1 endpoints secured with bearer authentication.

## For AI agents

Programmatically render a url as an image or video. Covers 1 operations with bearer authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Render a URL as an image or video
- Manage communications data programmatically
- Integrate Urlbox API into automated workflows
- Query and filter Urlbox API records by parameters
- Monitor Urlbox API operational status and events

## Use cases

### Communications Operations

Use the Urlbox API to perform communications operations programmatically. The API provides 1 endpoints covering core functionality including render a url as an image or video.

Example prompt: Call POST /v1/render/sync to render a url as an image or video

### Data Retrieval and Monitoring

Query Urlbox API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Urlbox API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Urlbox 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 'render a url as an image or video', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/render/sync | Render a URL as an image or video |

## Key resources

- **Render** — Operations for render

## Why Jentic

- **Setup:** Wiring the Urlbox API by hand means attaching its bearer token and building the synchronous render payload for each screenshot or capture yourself. Through Jentic you install once, import Urlbox from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Urlbox drives its render through the request body rather than the URL path, so limit the agent to the operations it needs, such as a synchronous render. You choose that operation set, so nothing beyond what you list runs.
- **Credential handling:** Your Urlbox 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 'render a URL as an image or video', and Jentic returns the matching Urlbox operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Urlbox API use?

The Urlbox 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 render a url as an image or video with the Urlbox API?

Yes. Use the POST /v1/render/sync endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Urlbox 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 render a url as an image or video through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'render a url as an image or video'. Jentic returns the matching Urlbox API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Urlbox API have?

The Urlbox API exposes 1 endpoints covering render operations.

### Can I limit what my agent is allowed to do with the Urlbox API?

Yes. Because you run Jentic One yourself, your own rules decide which Urlbox operations and credentials the agent can use, and it can only call the operations you list. Urlbox drives its render through the request body rather than the URL path, so you can restrict the agent to just the synchronous render at POST /v1/render/sync and nothing beyond that set will run. Your Urlbox bearer token is stored once, encrypted, by your instance and injected only at execution time.