##\ ##\
## | ## |
#######\ ##\ ##\ ######\####\ #######\ ######\ ######\
## __##\ ## | ## |## _## _##\ ## __##\ ## __##\\_## _|
## | ## |## | ## |## / ## / ## |## | ## |## / ## | ## |
## | ## |## | ## |## | ## | ## |## | ## |## | ## | ## |##\
## | ## |\####### |## | ## | ## |####### |\###### | \#### |
\__| \__| \____## |\__| \__| \__|\_______/ \______/ \____/
##\ ## |
\###### |
\______/
A private AI assistant. There is no account to make — a key on this device is the whole of it.
What your messages are signed with. It stays private: it syncs between your devices encrypted, and is never published or sent to the model.
Your key is still made on this device and stays yours. Google only keeps a copy of it, encrypted with a PIN you choose, and cannot read it without that PIN. It sits in a hidden app folder of your Google Drive that only Nymbot and Nymchat can see, and never reaches our servers.
Your key is still made on this device and stays yours. Apple only keeps a copy of it in your iCloud, encrypted with a PIN you choose, and cannot read it without that PIN. The same backup opens in the Nymbot iPhone app and in any browser, and never reaches our servers.
No PIN to remember: your passkey protects your key. An encrypted copy is kept on Nostr relays under a separate key that is not linked to your account, and only your passkey can find and open it.
The same key you use in Nymchat, or any other Nostr app. It stays on this device.
Paste the bunker:// link from your signer app, or show a code for the app to scan. Your key stays in the signer, which is asked each time Nymbot signs or decrypts.
Scan this with your signer app, or paste the link into it. Nymbot waits up to five minutes.
By continuing you agree to the Terms and Privacy Policy.
##\ ##\
## | ## |
#######\ ##\ ##\ ######\####\ #######\ ######\ ######\
## __##\ ## | ## |## _## _##\ ## __##\ ## __##\\_## _|
## | ## |## | ## |## / ## / ## |## | ## |## / ## | ## |
## | ## |## | ## |## | ## | ## |## | ## |## | ## | ## |##\
## | ## |\####### |## | ## | ## |####### |\###### | \#### |
\__| \__| \____## |\__| \__| \__|\_______/ \______/ \____/
##\ ## |
\###### |
\______/
Your Nymbot identity is encrypted on this device. Enter your passphrase to unlock it.
Unlocking…
You can change this anytime in Settings.
Nobody can reissue either of these — not even us. Without them, this identity, its history and any credits on it are gone.
The second one seeds the key that makes your messages quantum-resistant. Paste it into another device to link it to this account.
Before you start, here is what Nymbot sends to answer you and who receives it.
What is sent: your messages and the earlier messages of that chat, the files, images and voice recordings you add, and the persona, instructions, memories and workspace files you use with it. When you connect a repository or a connector, Nymbot also receives its access token, and the files and tool results it reads go to the AI model.
Who receives it: the Nymbot service run by 21 Million LLC, which processes it on our servers. If you pick a Pro model or an image or video generator, it also goes to that model's maker, such as OpenAI, Anthropic, Google, xAI, Moonshot AI, Alibaba or MiniMax. Repositories and connectors you add are contacted on your behalf.
You can turn this off at any time in Settings → Privacy & Security.
An estimate for one reply at the rates shown: the low end is a short answer, the high end a long one. Whatever the model has to read pushes it up — web results, repository files, attachments, and a long chat behind you — and a task that takes several passes costs more again. You pay for the tokens actually used, never a flat price per message. A full breakdown of every model and what it costs is in the pricing knowledge base.
Email us and say what you were doing when it went wrong. We cannot read your chats — they are encrypted to keys we do not hold — so the more you can tell us, the more we can help.
Private AI chat with no account, end-to-end encrypted, and paid per reply in Bitcoin over Lightning.
Send feedback, a question or a bug report. It goes to the Nymbot developer as an end-to-end encrypted private message from your own key, never from a throwaway one.
Call Nymbot's models from your own code with an OpenAI-compatible API. Requests spend the same balances as the app: Nymbot Auto uses the standard balance, any other model the Pro balance. Unlike chats in the app, API requests are not end-to-end encrypted.
API calls need credits. You can make keys now, but every call is refused until you buy some.
Copy this key now. You will not see it again: Nymbot keeps only a hash of it.
Connect a Nostr Wallet Connect wallet and Nymbot pays an invoice from it whenever a balance drops below the threshold. The connection is stored encrypted on the server.
A prompt Nymbot sends for you on a schedule. Normally it runs while the app is open, and a run that came due while it was shut runs once when you come back rather than catching up on all of them. Turn on server schedules in Settings and each one can notify you when it is due, or run on Nymbot's server while the app is closed. Each run costs a reply, like any other.
A bot is a way of answering: a name, standing instructions, a model and a few openers. Share one as a link or publish it under your npub. A shared bot carries none of your repositories, tokens or files — only how it answers.
Paste a bot link or an address published on Nostr.
A workspace is standing context: instructions, reference files and repositories that every chat in it starts with. The files stay on this device, and the parts that bear on what you ask travel inside each message of a chat that uses them.
The same prompt goes to two models on separate threads, so neither sees the other's answer. Keep the one you prefer and the chat carries on from it. Two replies means two charges.
Connect as many repositories as you like and tick the ones this chat can see. Pro replies read their code and, with writes on, commit, branch and open pull requests. Access tokens are sent to the Nymbot worker per request and never stored server-side or published to relays. With sync on they travel to your other devices sealed to your own key, and disconnecting one on any device disconnects it everywhere.
A NIP-34 announcement says where a repository is cloned from and which branch is current. Paste one and the fields below fill in; the access token is still the git host’s, because that is where the code is.
Off commits straight to the working branch, one task at a time.
Connect outside tools over MCP and tick the ones this chat can use, up to three at a time. Pro replies can call their tools; every tool asks you before it runs unless you choose to always allow it, and a tool the server marks as able to delete always asks. The URL and any token or header are sent to the Nymbot worker with the messages that use them and never stored server-side or published to relays. With sync on they travel to your other devices sealed to your own key.
A persona is a standing instruction sent with every message of a chat. It never leaves your device except as part of those messages.
Sent with every message of this chat, on top of any persona.
Saved instructions. Run one on a message by typing / and its name, attach one to a chat so it applies to every message, or start a new chat with it. A skill’s text is sent with the message, so it counts toward what the message costs.
A reply that produces a whole file — a page, a script, a document — opens it here beside the chat, where you can read it, edit it and keep the versions.
Every file a reply has produced, across all your chats, newest first.
Standing facts Nymbot carries between chats, kept one at a time so each can be read, corrected or thrown away on its own. They live on this device; the few that bear on a question travel inside that message, encrypted like everything else you send. A ghost chat neither reads them nor adds to them.
Comma separated. Tags show in the chat list and are searchable.
The code runs in a fresh container that is thrown away afterwards. It can download packages and nothing else, and it never sees your keys or this chat. You pay for the time it runs, never more than the price shown.
A fresh headless browser opens the public address you give and reports console errors, failed requests, load times, web app checks and a quick accessibility scan, with desktop and phone screenshots. Private, local and Nymbot addresses are refused. You pay for the browser time, never more than the price shown.
A lead model splits the task among workers that run at the same time, then checks and combines what they bring back.
The lead can use this chat's connectors and server runs, and the workers cannot. Each call the lead wants waits for you to allow it.
Limits for this chat, in sats, whichever tier answers. Replies are counted at each tier’s price per credit. A bot’s own caps apply too, and the stricter one wins.
No steps recorded yet.
What this chat may do without asking you first.
Anything that deletes, pushes or could cost more than the reply holds always asks.
Notices about new models and other news, pinned to the top of the chat. Each one can be dismissed.
Leave Nymbot while it works and get a notification when the reply is ready. This sends your browser’s push address, held only until that reply, and never your chat titles.
Anonymous chats only get notifications from this device while Nymbot is open in a tab. They never register with the push server, so nothing reaches you once the tab is closed.
A repo task can stop mid-way when it has used its allowance of model calls. Carrying on buys it another allowance from the same balance, one leg at a time, and every leg says what it cost. Stop cancels the rest.
Off unless you turn it on. When a task runs out of room, Nymbot's server carries it on by itself instead of waiting for this device. To do that it keeps what the next step needs, sealed with a key the server holds, for at most 6 hours: the task's saved progress and its settings, including the tokens for the repositories and connectors it uses. It spends no more than the budget above and deletes it all when the task ends. Never for anonymous chats or the free allowance.
Off unless you turn it on. Each scheduled prompt can then choose to notify you when it is due, or to run on Nymbot's server. Turning this off deletes every schedule the server holds at once.
Notifications in this app go through your browser's push service (Google's, in Chrome). What they carry is encrypted, so the push service cannot read it.
How many requests can run at the same time across your chats. Each running request holds its credits until it finishes.
A repository task with its own branch does this when it finishes. Each repository can choose differently when you edit it.
A watched pull request posts to its chat when CI fails, a reviewer comments, or it is merged or closed, even while the app is closed. Nymbot's server keeps the repository token for it sealed for up to 7 days and only reads from the forge. Each repository can choose differently when you edit it.
A fix run works on the pull request's branch with your plan setting, at most 3 times per pull request. What the forge reported is passed to it as data, never as instructions.
With a plan first, Nymbot shows you what it will do and changes nothing until you approve.
Anything that deletes, pushes or could cost more than the reply holds always asks.
What is sent: your messages and the earlier messages of that chat, the files, images and voice recordings you add, and the persona, instructions, memories and workspace files you use with it. When you connect a repository or a connector, Nymbot also receives its access token, and the files and tool results it reads go to the AI model.
Who receives it: the Nymbot service run by 21 Million LLC, which processes it on our servers. If you pick a Pro model or an image or video generator, it also goes to that model's maker, such as OpenAI, Anthropic, Google, xAI, Moonshot AI, Alibaba or MiniMax. Repositories and connectors you add are contacted on your behalf.
Your settings, library and conversations are sealed to your own key and kept where any device signing in with it can read them back. The server stores a blob it cannot open, under a name that is a hash. Ghost chats are never included. Repository and connector tokens are, sealed the same way, so a chat that uses them works on every device; disconnecting one anywhere disconnects it everywhere.
Swept when the app opens. Pinned chats are never swept.
Deletes your account: your key, conversations and settings on this device, and your account data on our servers, including your credits and purchase records. Other devices signed in to it are wiped too. Anything already on public relays stays there. Any remaining Nymbot credits will be lost. This cannot be undone.
Your chat is already end-to-end encrypted, but Nymbot still sees which pubkey is talking to it. Turn this on and every message, and every reply, travels under a throwaway key generated on this device. Credits move across as blind vouchers Nymbot signs without seeing, so its own records cannot link the two.
Turn it on to fund the throwaway key, by hand or automatically.
When the throwaway key runs low, move credits across without asking. Same blind vouchers, same unlinkability — it just saves doing it by hand before every chat.
Spends that many credits from your nym and mints the same value onto the throwaway key. Nymbot signs the vouchers blind, so it cannot match what it spent to what it later accepts.
Standard picks a model for you, per question. Pro answers with the one frontier model you choose. Separate balances, and neither converts into the other.
Your nym never touches the payment. Spend them from an anonymous chat.
Choose how many of your credits to give. You get a link, a code and a QR code, and whoever uses it first adds the credits to their own balance.
Anyone with the link or the code can claim it, so send it only to the person it is for.
Paste the gift link or code someone sent you. The credits go onto this key's balance.
Shown on your messages and here instead of the generated name. Only you see it: it syncs between your devices end-to-end encrypted, and is never published or sent to the model. Anonymous chats always show Anon.
Both are the same key in two spellings, and both are safe to share — they are how somebody addresses you.
Your private key stays in your signer, so there is no nsec to back up here. Keep it backed up in the signer itself.
Keep a copy of your private key and your post-quantum recovery code in a hidden app folder of your Google Drive, encrypted with a PIN you choose. Google stores only that encrypted copy and cannot read it without the PIN, and it never reaches our servers. On another device, “Continue with Google” and the PIN bring both back. Back up again after linking a new recovery code.
Keep a copy of your private key and your post-quantum recovery code in your iCloud, encrypted with a PIN you choose. Apple stores only that encrypted copy and cannot read it without the PIN, and it never reaches our servers. On another device or in the Nymbot iPhone app, “Continue with Apple” and the PIN bring both back. Back up again after linking a new recovery code.
Back up your private key and your post-quantum recovery code with a new passkey. There is no PIN: the passkey protects it. Both are encrypted on this device, and the encrypted copy is kept on Nostr relays under a separate key that is not linked to your account. On another device, “Continue with a passkey” brings them back.
Nobody can recover this PIN, not even us. Write it down somewhere safe. Anyone who has both your Google account and this PIN can open your key.
Apple's sign-in opens in a new window. Your Apple Account password goes only to Apple, and this app is told only an ID for your iCloud, never your email or name.