Private. Paid in sats. Yours alone.
##\ ##\
## | ## |
#######\ ##\ ##\ ######\####\ #######\ ######\ ######\
## __##\ ## | ## |## _## _##\ ## __##\ ## __##\\_## _|
## | ## |## | ## |## / ## / ## |## | ## |## / ## | ## |
## | ## |## | ## |## | ## | ## |## | ## |## | ## | ## |##\
## | ## |\####### |## | ## | ## |####### |\###### | \#### |
\__| \__| \____## |\__| \__| \__|\_______/ \______/ \____/
##\ ## |
\###### |
\______/
An assistant that answers to you and to nobody else
Every question and every answer travels as a gift-wrapped Nostr event, sealed to keys only the two ends hold. Relays carry ciphertext and a single-use sender key — nothing they can correlate.
ML-KEM key encapsulation is combined with the classical exchange rather than replacing it, so an attacker has to break both. Traffic captured today does not become readable later. How the hybrid works.
Move the whole conversation onto a throwaway key and your credits across as blind vouchers Nymbot signs without seeing. It bills a message it cannot attribute to you. The full mechanism.
No subscription, no card, no invoice with your name on it. Buy credits over Lightning and spend them a reply at a time — 10 sats for a standard reply, 100 for a frontier model. Pricing in full.
Claude, GPT, Gemini, Grok, Kimi, Qwen and MiniMax, pinned per conversation — or let Nymbot route each message to whichever model suits the task. Models and routing.
Connect GitHub, GitLab or Gitea and Pro replies read your actual files, search the tree and answer from what is there. Turn writes on and it commits, branches and opens pull requests. Repository mode.
Generate a picture with ?image or a voice clip with ?speak, choosing from nine frontier generators. Send it a photograph and it will tell you what is in it. Making things.
Keep as many separate chats as you like. Each is its own thread with its own context, named after the first thing you asked — and the title is written on your device, never sent. How chats work.
No email, no phone number, no password. A key generated on your device is your identity, your history and your balance. Bring one you already have from any Nostr app. Identity and login.
Five steps, and none of them involve an account
Nymbot is built on Nostr. Messages are events, identities are keypairs, and delivery is a set of relays rather than a server you have to trust — which is why an identity from any other Nostr app works here unchanged.
Kinds 14, 13 and 1059: an unsigned rumor, a seal signed to the recipient, and a wrap under a single-use key.
A relay sees an event from a key that exists for one message only, addressed to a key it cannot connect to anything else.
Kind 27235: a short-lived auth event, signed for one action and one endpoint.
A captured signature cannot be replayed against a different request. Your message never travels as plaintext.
Nothing is fetched, generated or billed until the turn is claimed.
Resend the same message and you collect the answer you already bought, rather than paying for a second one.
The wrap is opened, the seal's signer is checked against the authenticated key, and the thread is rebuilt from the previous wraps.
Classification, routing, web search and repository tool calls all happen here.
Kind 30078: the post-quantum announcement carrying each side's ML-KEM key.
The reply is sealed hybrid — classical and lattice — so capturing it today buys nothing later.
No user table. No password to leak. No transcript anyone can be compelled to hand over.
The whole protocol, written down.
Anything beginning with ? is a command
Games, unit conversion, maths, the Bitcoin price and more — the full reference.
Everything you need to know about Nymbot
A private AI assistant. You talk to it the way you would talk to anyone in a messenger, and it answers using whichever frontier model suits the question.
What is different is underneath: there is no account to make, the messages are end-to-end encrypted, and replies are paid for in Bitcoin a reply at a time rather than by subscription. It can also be told to stop knowing who you are.
Being precise about this is worth more than being reassuring about it. Your messages are end-to-end encrypted, which means nobody in between — relays, networks, anyone holding the traffic — can read them. The Nymbot service does open them, because it has to in order to answer.
So the honest claim is: nobody else can read your conversation, and with anonymous mode on, the service that answers it cannot tell whose conversation it is. Your conversation titles are generated on your device and never sent at all. The full table of what the server sees is in the knowledge base.
The chat is encrypted, but normally the service still knows which public key is talking to it — that key is what the credit balance and the conversation thread hang off. Encryption was never the gap. Attribution was.
Anonymous mode generates a throwaway keypair on your device and moves the entire conversation onto it. Your credits move across as blind vouchers: your app blinds a random secret, the service debits your balance and signs something it cannot read, and the throwaway key later presents the unblinded token with nothing to match it against. The tables record that a voucher was issued and that one was spent, and neither records who.
It does not hide everything, and we say exactly what it does not hide.
Credits, bought over the Lightning Network. Standard credits are 10 sats each and buy an auto-routed reply; Pro credits are 100 sats each and buy a reply from a specific frontier model you have pinned.
An ordinary standard reply is one credit. A Pro reply costs a per-model base and then scales with the length of the answer, up to a per-model cap — the cap is reserved when you send and only the real cost is taken. Nothing is charged for a failed generation, and resending a message replays the answer you already bought rather than buying another. Pricing in detail.
No. Open it and a keypair is generated on your device. That key is the account: it signs your messages, your balance is filed under its public half, and your history is encrypted to it.
Which is why the one thing worth doing on day one is backing up your nsec. Nobody can reissue it — not even us. You can also bring a key you already use in any other Nostr app.
Yes, and it is the same account. Nymchat is a full messenger with Nymbot built into it; this is Nymbot on its own. Sign in to either with the same key and you get the same credits, the same history and the same throwaway key.
Buy credits in one, spend them in the other. Nothing needs migrating, because there is nothing per-service to migrate. How the two relate.
Claude Fable 5, Claude Opus 5, Claude Sonnet 5, Claude Haiku 4.5, GPT-5.6 Sol, GPT-5.4 mini, Gemini 3.1 Pro, Gemini 3.6 Flash, Grok 4.6, Kimi K3, Qwen 3.5 and MiniMax M3 — pinned per conversation with ?model.
Or pin nothing: on the standard tier each message is classified and routed to a model suited to it, so a quick factual answer does not pay for a reasoning model. The picker is generated from a live catalog, so what you see is exactly what the service will charge for. Models and routing.
Yes. ?git connects GitHub, GitLab or Gitea/Forgejo with a scoped access token, a repository and a branch. After that, Pro replies run as a small agent: listing directories, reading files and searching the tree, then answering from what is actually there.
With ?git writes on it can also commit, create branches and open pull or merge requests. The token is stored only on your device, passed with each request, never stored server-side and wiped by a panic wipe. Repository mode.
You lose the account. Your history is encrypted to that key and your balance is filed under it, and there is no recovery path because there is no user table to recover you from — that is the same property that means nobody can hand your conversations to anyone else either.
Back up your nsec the first day you use it, and turn on identity encryption so the copy on your device is unreadable without unlocking.
Yes — the web app, the mobile apps and this site are all in the public repository. Read what the client does with your key rather than taking our word for it.
The hosted model routing is the part you cannot run yourself, which is why the client is written so that everything it can verify locally, it does: signatures, the voucher proofs, and the keys it seals to.
No registration. No subscription. No name on the bill.
A key on your device, and an assistant that answers to it.