> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kealinks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# kealink API

> Permanent short links and dynamic QR codes. A code we issue never stops resolving.

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.

<Card title="A code we issue never stops resolving" icon="infinity">
  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.
</Card>

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](/permanence) for how
that is enforced.

## Two ways in

<CardGroup cols={2}>
  <Card title="With an account" icon="key" href="/quickstart">
    Sign in, get an API key, create links against your quota. Three permanent
    links free, forever. Both paid plans add custom domains, analytics and
    teammates: Starter allows 100 new links each billing cycle, Unlimited has no
    per-cycle cap and grows its allowance every cycle.
  </Card>

  <Card title="With a payment" icon="robot" href="/agent-payments">
    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.
  </Card>
</CardGroup>

## Base URL

```
https://api.kealinks.com
```

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:

```bash theme={null}
curl https://api.kealinks.com/api/openapi.json
```

If you are an agent, that endpoint plus [`/api/pricing`](/agent-payments) is
everything you need. You do not have to read the rest of this site.