Barycenters / Mint an API key
Namespace API keys · self-serve

Mint an API key. Scoped to your namespace.

Reserve a namespace and you hold its claim token (it's in your checkout success URL). That token proves ownership — so you can mint, list, and revoke keys yourself, right here. A minted key is shown once; then you call /v1/admit with Authorization: Bearer <key>. Every request below goes straight to the live service over HTTPS — the token and keys never touch us.

Mint · list · revoke

Your namespace

Enter the namespace you reserved and its claim token, then mint or list keys.

Don't have one? Reserve a namespace → — the token comes back in your success URL.

● Your token and keys go only to barycenters-admit.fly.dev over HTTPS — never to us, never to a third party, and nothing is stored in this browser. authority_effect = 0: a key lets you ask /admit; it never grants authority.

Result

Nothing yet Mint a key to see it once (copy it immediately), or list the keys already minted for your namespace.

How a key works

01

Ownership is proven, not asserted

The claim token from your checkout is what proves the namespace is yours. No token, or the wrong one, and the mint is refused (403) — nobody mints against a namespace they don't hold.

verify_claim(namespace, token) · fail-closed
02

The key is yours alone, shown once

A bary_ key is returned in plaintext exactly once — the service keeps only its SHA-256 fingerprint, never the key. Lose it and you mint a new one; you never retrieve the old.

stored: fingerprint only · never the secret
03

Use it, revoke it, anytime

Call /v1/admit with Authorization: Bearer <key>. Revoke any key here the moment you want it dead. A key identifies who asked — it never widens what's allowed.

authority_effect = 0 · a key asks, it never grants