Chirio
Get Started
Introduction
Quickstart
How Chirio works
Authentication
MCP server
Platforms
Overview
Instagram
Threads
X
LinkedIn
Supa Hub
Guides
Connect accounts
Publish a post
Media requirements
Carousels
First comments
Idempotency and retries
Account lifecycle
Revocation and deletion
The dashboard
Products
Screenshots
Feedback boards
What's new
Inbox
Messages
Site analytics
Page comments
Billing
Plans
Metering
Quotas
Api Reference
Overview
Accounts
Posts
Errors
Changelog
Roadmap
TrademarkTrademark
Ctrl k
Search…
Sign up
Chirio
Get Started
Introduction
Quickstart
How Chirio works
Authentication
MCP server
Platforms
Overview
Instagram
Threads
X
LinkedIn
Supa Hub
Guides
Connect accounts
Publish a post
Media requirements
Carousels
First comments
Idempotency and retries
Account lifecycle
Revocation and deletion
The dashboard
Products
Screenshots
Feedback boards
What's new
Inbox
Messages
Site analytics
Page comments
Billing
Plans
Metering
Quotas
Api Reference
Overview
Accounts
Posts
Errors
Changelog
Roadmap
TrademarkTrademark© Dopler. All rights reserved.
Built with Aveiro

Screenshots

Styled screenshots of public web pages inside a 3D mockup, on the same key and bill as publishing.
Updated 4 days ago
Feedback boards
Chirio takes styled screenshots of public web pages: one PNG of the page inside a mockup, with a background, a camera angle and optional browser chrome. It is the same API key and the same bill as publishing, so a launch post and the image that goes with it come from one place. Every image on these docs was made this way.

Take one

curl https://chirio.dev/api/v1/screenshots \
  -H "Authorization: Bearer chirio_sk_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: launch-hero-1" \
  -d '{ "url": "https://example.com", "theme": "dark", "chrome": "dark" }'
Only url is required, and it must be a public page. The optional fields:
Field
Values
styleIda style from the gallery (below)
themelight or dark
chromenone, light or dark
framing0.4 to 3; below 1 is tighter
, viewport in CSS pixels
1 to 3
capture the whole page, not the viewport
film the page again after it changed
returns at once with
width
height
deviceScaleFactor
fullPage
recapture
wait
false
pending

Done or pending

When the image is ready within about 25 seconds the answer is 200 with status: "done", an imageUrl, width and height. A page Chirio has never filmed before usually takes longer, and the answer is 202 with status: "pending".
Poll GET /api/v1/screenshots/:id every few seconds until status is done or error. Each poll returns a fresh imageUrl; the link is signed and valid for an hour, so copy the image somewhere of your own if you need it longer.
Send an Idempotency-Key header and a retry returns the same screenshot instead of starting another.

Styles

GET /api/v1/screenshot-styles?featured=&limit= lists the gallery, curated styles first: id, name, description and a previewImageUrl for each. limit is 1 to 60, default 24. Pass the id as styleId. A plain capture without a mockup is the style none.

Cost

A finished screenshot costs 3 units, charged once per screenshot id when Chirio first sees it done, on the create call or on a poll. A pending, failed or never-collected screenshot costs nothing, and listing styles or polling is free.
Units come from the month's allowance first, then from prepaid credits. When the two together can't cover one more, the screenshot is refused with 402 quota_exceeded before it renders. See Metering.

From an agent

The MCP server has create_screenshot, get_screenshot and list_screenshot_styles. They call the same routes, so quota and billing are identical.