Images · Updated 2026-10-12
Self-host images, or let you serve them?
Either works on a paid plan, and both cost one credit per image. The simplest: mint signed URLs once with renew enabled and the longest TTL (7 days), store one URL per vehicle and view, and put it in your pages. Loading is free, the URL is publicly cacheable within its lifetime, and a week in which someone opens it costs one more credit, so a page nobody visits costs nothing and you never run storage. Rendering improvements reach your pages on their own.
The other: fetch each image once with your key, store the file, and serve it from your own CDN like any other asset, re-checking with the ETag for free. Choose this when you need the exact pixels to stay fixed, offline access, or files inside documents. Both are covered by the license, and what you hold keeps it after the plan ends. Never put an API key in a page or app; only signed URLs reach browsers.
Sources and full details
The published terms and your written agreement govern. For a question about your account, contact support.