FAQ
Frequently asked questions.
Everything you need to know about creating with assets.dev.
FAQ
All questions.
Create on-brand images and videos from built-in templates. Supported formats and motion options depend on the template.
Paste a public website URL and assets.dev detects colors, typography, and available logo signals, then turns them into editable brand data you can review and apply to renders.
One credit covers one image or one second of rendered video. Optional high-resolution image or video renders cost 2× the normal credits.
Free includes 100 credits per month. Pro includes 1,000 credits per month.
It renders at 2× pixel scale for a larger output and doubles that render's credit cost.
Failed render jobs are automatically refunded to your credit balance.
Yes. You can edit the schema-defined content of built-in templates, choose supported formats, create image or video variants, and apply a saved brand.
Yes. After authentication, an agent can use MCP to inspect templates and brands, generate template-shaped content, submit and check renders, and read the credit balance. Account-scoped REST endpoints are also available for integrations.
Each built-in template publishes its supported formats and whether it can render images, video, or both. Check the template gallery for the current catalog.
Yes. The MCP endpoint works with Claude, ChatGPT, Cursor, VS Code, and any MCP client, and agents without an account can self-serve an API key through the device flow.
See:MCP setup·For agents
Yes. A REST API with a live OpenAPI 3.1 document exposes everything the app does, so any integration can render, list templates, and read credits over HTTP.
See:API reference·OpenAPI
The agent registers with an email, a human approves the emailed link once, and the agent polls for the key — the device flow needs no pre-existing account.
Full docs cover the app workflow, the MCP server, the REST API reference, and webhooks.
See:docs.assets.dev