assets.dev docs

assets.dev docs

Turn a URL into a brand, then render branded stills and videos from 12 templates.

Point assets.dev at a website. It extracts a brand — colors, fonts, logo, voice — and stores it as an editable document. Pick a template, pass your copy, and render on-brand images and videos in the formats you need. Work in the app, connect an agent over MCP, or call the REST API directly.

The assets.dev wall: a grid of branded template cards — a feature announcement, a proof stat, a browser mockup, and a phone showcase — filtered to Templates.
The wall — every template and rendered asset for a brand in one place.

Pick a path

Use the app

The full workflow: extract a brand from a URL, confirm it, pick a template, and render.

Connect via MCP

Add assets.dev to Claude, Cursor, or ChatGPT and drive renders from your agent.

Call the REST API

Contract-backed OpenAPI 3.1: brands, templates, renders, credits, and webhooks.

For agents

Self-serve from zero: register, get a key, and render — with no-auth discovery endpoints.

Also here

Brands

How brand documents, tokens, and versions work.

Credits

What a render costs and how refunds work.

Webhooks

render.completed and render.failed event contracts.

Skills

The generated agent skill served by the API.

How the app works

From a website URL to on-brand assets in five steps. The same flow runs in the app, over MCP, or through the REST API — the API calls below are shown for reference.

On this page

Pick a pathAlso here