[mockuuups] Which mockup should I use? Searches all ~5300 Mockuuups scenes by device, scene and style.

query is free text and understands everyday device words — "tablet", "laptop", "poster", "smartwatch" — as well as exact placement slugs like "ipad-air". Combine it with family (iPhone, iPad, MacBook, TV, Paper, Apple Watch, Samsung, Google, iMac, ...) or kind to narrow.

tag is the strongest way to get one consistent look across several devices: scenes shot together share a tag, so filtering by a tag returned on a mockup you like gives you the rest of that shoot. Pass the returned id to create_mockups.

[mockuuups] Put one design into one or more mockups and render them.

Give exactly one source:

• screenshot_url — Mockuuups screenshots the live page itself. Best for websites; costs one extra credit per render.

• image_url — any publicly reachable image.

• image_base64 — raw image bytes for a design that only exists locally. Mockuuups can only render from a URL, so the image is staged on this server under a short-lived unguessable link for the render to fetch.

Pass several mockup_ids to render the same design across devices in one call; they run concurrently. Renders that outrun the wait budget come back as pending with a render_id for get_renders — the CDN links are already valid and will fill in once the render lands.

Each render costs a credit, +1 for a screenshot, so check account_status before a large batch.

[mockuuups] Did those renders finish? Poll renders create_mockups returned as pending. With wait_seconds it long-polls until they settle or the budget runs out; with 0 it checks once and returns immediately.

[mockuuups] How many credits are left, and what can this plan do? Reports the credit balance plus which features are actually available — hi-res, website screenshots, and whether CDN links expire. Worth checking before a batch: a plain render costs 1 credit and a screenshot costs 2.