Sign in with your wallet
Your wallet owns your keys and holds the balance they spend from. Signing in costs nothing, sends nothing, and authorises no transaction — you are signing a sentence, not a transfer.
—
You do not need this
A key on its own works, bills and receives deposits exactly as it always has. Mint one and skip this page entirely.
Nothing here is required to call the API. The key is the account, and it stays that way whether or not a wallet is ever attached to it.
What it adds
Several keys against one balance. One per machine, or one per project, all spending from the same funds rather than from balances you have to top up separately.
A new key when you lose one. The old key cannot be recovered by anyone, but a wallet that already owns it can mint a replacement and disable it.
A session can mint a key, and a key can spend
So it lasts 24 hours, you can sign out of it, and every action it takes is written to an audit log you can read.
What it can never do is show you a key you already have. Keys are stored as hashes, so signing in proves the wallet owns them without giving anyone a way to print them again.
What you are actually signing
A sentence, in your wallet's own prompt. No transaction is built, nothing leaves the wallet, and no permission to spend from it is granted.
There is no password and no email, because there is no account to attach them to.
Signed in
This session lasts 24 hours. It can mint a key and list the ones this wallet owns — it cannot show you one that already exists.
Here is your key
Your keys
| Key | Label | Status |
|---|
This session
Minting does not move money
A new key starts at zero and spends from this wallet's balance. Disabling an old one stops it billing; it does not refund what it already spent.