canonical: https://jentic.com/apis/latchshot.fly.dev/latchshot

# Latchshot Fly Latchshot API

The Latchshot API renders public web pages as PNG or JPEG screenshots and PDF documents. It screens each target against private and special-use networks before rendering, tracks monthly usage per key, and lets you request a higher plan when you outgrow the free tier. Only successful renders count against quota.

## For AI agents

Render any public URL as a PNG, JPEG, or PDF and read your monthly usage. Targets are screened against private networks before rendering.

## Scope

Does not crawl sites, extract page data, or archive web content. Use for rendering public web pages to screenshots and PDFs only.

## Capabilities

- Render a public web page as a PNG or JPEG screenshot
- Produce a PDF document from a rendered web page
- Screen each target URL against private and special-use networks before rendering
- Read current monthly usage against your plan quota
- Create a recurring Free-plan key and request an upgrade to a paid plan

## Use cases

### Agent-driven page capture through Jentic

An AI agent that needs a visual of a web page can render it on demand. Through Jentic the agent finds the render operation by intent, loads its input schema, and submits the target URL, receiving a PNG, JPEG, or PDF back without any manual wiring of the rendering service.

Example prompt: Search Jentic for 'capture a screenshot', then render the target URL as a PNG and confirm the render succeeded.

### Automated PDF snapshots of public pages

Generate archival PDF snapshots of public pages such as invoices, reports, or documentation. Latchshot screens the target against private and special-use networks first, so only reachable public URLs render, and only successful renders consume monthly quota.

Example prompt: Render a public report URL to a PDF, then read your monthly usage to confirm quota remains.

### Thumbnail generation for link previews

Produce screenshot thumbnails of pages to show as link previews in a chat surface or dashboard. Request a JPEG at the viewport you need, and pace requests against your plan by reading current usage.

Example prompt: Capture a JPEG screenshot of a page for a link preview and store the returned image.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/render` | Render a screenshot or PDF |
| GET | `/v1/screenshot` | Render a screenshot |
| POST | `/api/trials` | Create a Free-plan key |
| GET | `/v1/usage` | Read current monthly usage |
| POST | `/v1/upgrade-requests` | Request a higher paid plan |

## Key resources

- **Renders** — Screenshot and PDF render jobs against public URLs
- **Usage** — Current monthly render usage against the plan quota

## Why Jentic

- **Setup:** Wiring Latchshot by hand means sending its bearer key, resolving its host, and handling the render and file-download flow yourself. Through Jentic you install once, import Latchshot from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Latchshot carries the target URL in the request body, so rules bound which operations your agent may call, not which sites. You choose the operations it may call, such as rendering and reading usage, so requesting a plan upgrade is not included unless you add it.
- **Credential handling:** Your Latchshot key 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 'capture a screenshot' or 'render a page to PDF', and Jentic returns the matching Latchshot operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **APIFlash** — Screenshot API for rendering web pages to images
- **Urlbox** — Render URLs to images and PDFs with fine layout control
- **Browserless** — Headless browser automation for scraping and rendering

## FAQ

### What authentication does the Latchshot API use?

The Latchshot API authenticates with an HTTPS bearer token per its OpenAPI spec: send your key in the Authorization header as a Bearer token. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at request time, so your agent never sees the raw key.

### Is there a Latchshot API MCP server?

You don't need an MCP server to give your agent the Latchshot API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it on demand without loading another server's tool definitions into its context.

### Can I render a page as a PDF with the Latchshot API?

Yes. The render operation returns either an image or a PDF document for a given public URL, and the dedicated screenshot operation returns PNG or JPEG images. Targets are screened against private and special-use networks before rendering.

### What are the rate limits for the Latchshot API?

The OpenAPI spec does not state numeric rate limits; it notes that only successful renders consume monthly quota and that automatic overages are disabled. Check the Latchshot documentation at https://latchshot.fly.dev for current plan quotas.

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

Yes. Write a rule that allows only the rendering and usage-read operations, so the agent can capture screenshots and PDFs and check its quota but cannot request plan upgrades on your behalf, and every call it makes is logged.

### How do I capture a screenshot with the Latchshot API through Jentic?

Search Jentic for 'capture a screenshot', load the render operation, and pass the target URL and output format. Jentic injects your bearer token and returns the rendered file. To run it on your own infrastructure, install Jentic One from its GitHub repo.