A request can hold many
Send 30 labels in one POST and you are charged 30, not one. Batching saves round trips, not quota.
Pricing
Monthly. Cancel anytime.
Loaded live from the API, so these are always the prices in force.
Plan. Choose the one that fits.
How billing works
You are billed per label.
Not per request, not per byte. One ^XA…^XZ block is one label.
Format does not change the price
PDF, PDF-per-label, SVG and PNG all cost the same. Pick whichever fits your pipeline.
Failed requests are free
A 4xx never counts against your monthly labels. Only work the engine actually did is billed.
Checking usage is free
GET /usage is outside the quota, so you can poll it even while you are being throttled.
Limits
Every ceiling, in one table.
Request rate is the same on all three plans on sale today. What grows is the monthly volume.
Rate and volume
5 | requests per second — Free, Personal Normal and Personal Plus |
5k | requests per day — Free and Personal Normal |
10k | requests per day — Personal Plus |
50k | labels per month — Free |
350k | labels per month — Personal Normal |
1M | labels per month — Personal Plus |
Daily counters reset at 00:00 UTC; monthly labels reset on your billing date.
Per request
30 | labels per request — Free |
50 | labels per request — paid plans |
0.5 | MiB of ZPL per request — Free |
1 | MiB of ZPL per request — paid plans |
300 | PNG DPI ceiling — Free and Personal |
600 | PNG DPI ceiling — Business |
Over a limit returns 413 with the measured value and the ceiling in context.
Headers on every response
X-RateLimit-Limit-Second: 5
X-RateLimit-Limit-Day: 5000Sent whether or not you are near the limit, so a client can back off before it is refused.
Before you pick
The usual questions.
Is the free tier a trial?
No. It does not expire and needs no card. 50,000 labels a month, indefinitely.
What happens when I run out?
Conversions return 402 until the month rolls over or you upgrade. Nothing is queued and nothing is charged automatically.
How do I upgrade?
Upgrades are handled manually for now — get in touch. Self-serve billing through Stripe is coming, and card details never touch our servers.
Can I use one key everywhere?
You can, but use one key per environment instead. Revoking a leaked staging key should not take production down with it.
Three plans are open for signup today; the rest are listed so you can see where the range goes. Read the API reference