Skip to main content
You give us a destination. We give you a short link and a QR code. You print the code on a menu, a business card, a shipping label, a piece of machinery — and later, when the destination moves, you change where it points without reprinting anything. The part that matters is what happens after that.

A code we issue never stops resolving

Not when the destination changes. Not when you archive the link. Not when your subscription lapses. Not when you cancel outright and never speak to us again. Codes get printed on physical objects, and a dead redirect is a reprint bill.
That promise is not a policy we intend to keep. It is built into the shape of the system: the code path that resolves a link cannot read your billing status, because that data is not present on it. See Permanence for how that is enforced.

​
Two ways in

With an account

Sign in, get an API key, create links against your quota. Three permanent links free, forever. The paid plan adds custom domains, analytics, teammates, and an allowance that grows each billing cycle.

With a payment

No account, no sign-up, no human. POST /api/links with no credentials returns a 402 quoting a price. Pay it over MPP or x402, retry, and the link is yours. Built for agents.

​
Base URL

Every response is JSON except QR artwork, which is SVG, PNG or EPS.

​
The spec is generated from the code

The document powering the API reference on this site is built from the worker’s own request and response schemas — the same objects that validate live traffic. The running deployment also serves it:
If you are an agent, that endpoint plus /api/pricing is everything you need. You do not have to read the rest of this site.