API terms

Short version: build what you like with it, including a product you charge for. Keep the Box Blanks line on files you pass on — or ask us and we will usually say yes. It is free during beta and we will give you 30 days’ notice before that ever changes.

Last updated 2026-09-03

1. Your key

Keys are issued by hand to a named organisation. Your key is confidential: keep it server-side, keep it out of your repository and out of anything a browser can read, and do not share it outside your organisation or resell access to it.

Tell us at [email protected] if you think it has leaked and we will replace it, no questions and no blame. That is a far better outcome for both of us than a key quietly doing the rounds.

One key per organisation. Do not use several keys to get around a limit — if a limit is wrong for what you are building, ask, because we would rather know.

2. What you may build with it

Anything, including a product you charge for. Specifically, you may:

• call the API from your own backend, on your own schedule
• show generated dielines to your customers, in a configurator or anywhere else
• store the files with your quotations, orders and job records, for as long as you need them
• send them to a converter or die maker, and cut real tooling from them
• modify the geometry, and combine it with your own artwork and layout

You do not owe us a licence fee for the output, and we make no claim over the boxes you sell.

3. The attribution line

Every file the API returns carries our name. In an SVG it is a metadata element and a small line of text in the bottom-left margin; in a DXF it is a header field; in a PDF it is the document properties.

Please leave it there on any file you publish, display or hand to a customer. Do not remove, obscure, crop or alter it, and do not present the output as having been generated by your own software, unless we have agreed otherwise in writing.

Production is exempt, and that is deliberate. The credit is its own layer precisely so a die maker can drop it before cutting — a cutting table would otherwise read the text as geometry and cut it into the forme. Removing it to make a die, or because your converter asks you to, is expected and fine. This clause is about files that go out with your name on them, not about the workshop.

If you need it off the files you publish as well, talk to us rather than assuming. We would far rather agree something than have you strip it and wonder whether that was allowed.

If you held a key before 2026-09-03, this section does not apply to your existing integration until we have written to you and given you 30 days. You were told no attribution was required, and we are not going to change that on you overnight. In practice that notice will arrive with the pricing notice in section 4 — one email, 30 days, both changes.

4. Beta, and what that costs

The API is in beta and free to use, including inside a product you charge for.

We make one commitment about that, and we intend to keep it: you will get at least 30 days’ notice by email before any charge applies to you, and your key will keep working throughout the notice period. If the price does not suit you, stop calling it and nothing is owed.

Limits, tiers and prices are not settled and will change. Being in beta first does not entitle you to a permanently better rate, and we would rather say that plainly now than imply otherwise.

5. Limits and fair use

Current limits are published on the API page and are enforced per key. They exist to stop a runaway loop, and we will raise them for a real workload — say what it is doing and we will usually just do it.

Output is deterministic: the same code and the same dimensions give you a byte-identical file. Please cache accordingly rather than asking us the same question repeatedly.

Do not use the API to bulk-download the catalogue in order to run a competing service, and do not run it in a way that degrades it for other callers.

6. Availability

There is no uptime guarantee and no support contract. This is a small service run by a small team, and the API may change, break compatibility, or be withdrawn.

Do not put it on a path where your business stops if it is unavailable. Cache what you can, and fail gracefully when you cannot reach us.

7. What we record

Against your key we record the calls you make: the endpoint, the time, the cost in rate-limit units and the response status. It is how we decide what to build and what the limits should be, and you can read your own figures at any time from GET /api/v1/usage.

When a request fails, we also log the parameters you sent and the error we returned, so we can answer you when you ask what went wrong. Your API key is never written to those logs. Neither is any email address you give us on a fault report.

We do not see, store or claim anything about the boxes you design beyond the parameters of the call itself.

8. Suspension

We may suspend or revoke a key that is being used in breach of these terms, that is degrading the service for others, or that appears to have been compromised. Where the situation allows it we will email you first, because an integration that stops without warning is a bad day for somebody who has done nothing wrong.

You can stop using the API whenever you like. There is nothing to cancel.

9. Liability

Section 5 of the website terms applies, with one difference: in place of the £1 cap set out there, our total liability to you under these API terms is limited to the greater of the fees you have paid us in the twelve months before the claim, or £100.

Tooling, production, material, recall and lost-profit losses are excluded, as they are there. Nothing here excludes liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be excluded.

You are using this in the course of a business, so please satisfy yourself about every dieline before you or your customers spend money on tooling. That obligation does not move to us because a machine drew the file.

10. Changes to these terms

These terms may be updated, and the date at the top shows when they last changed. If a change materially reduces what you are allowed to do, we will email the address the key was issued to and give you 30 days’ notice before it applies to you.

11. Governing law

These terms are governed by the law of England and Wales.

Anything here that does not fit what you are building, say so — during a beta with a handful of integrators, a term that is wrong for you is a thing we can change.