Skip to content
In development

Put the gate inside your own order flow

The same checks the web app runs, callable from your shop software. Orders arrive, artwork is checked before anyone touches it, and only the problem files reach a human.

What it is for

What it will look like

Shapes are indicative and will change before release.

request

POST /v1/checks
Authorization: Bearer sk_live_…
Content-Type: application/json

{
  "file_url": "https://your-shop.example/orders/8412/artwork.png",
  "target_width_cm": 28,
  "reference": "order-8412"
}

response

{
  "id": "chk_9f2a…",
  "reference": "order-8412",
  "outcome": "print_smaller",
  "safe_width_cm": 22.4,
  "effective_dpi": 197,
  "findings": ["low_resolution", "soft_edges"],
  "customer_message": "…",
  "artifacts": { "repaired_png": null }
}

Not open yet — and we are not going to pretend otherwise

The endpoints exist and run the product itself, but they are session-based and there are no public API keys. Publishing a key page today would be selling something that does not exist. When keys open, this page changes first.

Want it early?

Use the product first. The shops already checking files are the ones who will shape the API, and they get access before it is announced.