All use cases
Events and ticketing
Print the badge in the time it takes to say a name.
Door queues are made of hardware that was configured the night before. Point a laptop or a phone at the API instead: the check-in request prints the badge, and adding a second desk is pairing a second printer, not rebuilding the setup.
What comes out
ADMIT ONE
DEVCONF 2026
Hall B
Row 12
Doors
18:30
SEAT 12F
An attendee is checked in.
POST /v1/printers/{id}/jobs
Content-Type: text/html
<h1>ADMIT ONE</h1>
<h2>DEVCONF 2026</h2>
<p>Hall B · Row 12 · Doors 18:30</p>
<p><b>SEAT 12F</b></p>
201 Created · printed in 1.4s
Another desk is another printer
Pair it, get an id, send to it. Nothing about the first desk changes.
Know the desk is ready before doors
Live printer status tells you a desk is reachable while you can still do something about it.
Under 1.5 seconds at median
Fast enough that the badge is the thing people wait for, not the queue behind them.