How to Get an API Key for ReplyRight
ReplyRight asks for one thing before it can draft anything: a model key you own. Here is how to get one, including the option that costs nothing.
Last updated 18 November 2026.
This page exists because the setup is the part where people give up, and most of that is avoidable. The extension is bring-your-own-key by design, not as a paywall: there is no ReplyRight account, and no ReplyRight server receives your email. The draft is generated by the provider you choose, using your key, going straight from your browser to them. The tradeoff is one setup step, and this page is that step.
Pick a provider first
All five speak the same OpenAI-compatible protocol, so the extension only needs to know the base URL and the model name — and it fills both in for you when you pick a provider from the menu. The only real decision is how much friction you want to trade for cost.
| Provider | What it costs | What you need first | Model name |
|---|---|---|---|
| Zhipu GLM-4-Flash | Free tier | Phone number and real-name verification | glm-4-flash |
| DeepSeek | Prepaid, from ¥10 | Alipay | deepseek-flash |
| Qwen (DashScope) | Free quota, then paid | Alibaba Cloud account | qwen-plus |
| Kimi (Moonshot) | Prepaid | Alipay | moonshot-v1-8k |
| OpenAI | Pay as you go | A payment method that works outside mainland China | gpt-4o-mini |
The free one is not the fastest one. GLM-4-Flash costs nothing but needs real-name verification, which is paperwork on someone else's schedule. DeepSeek takes about five minutes and ¥10, and that ¥10 covers a very large number of short email drafts — each reply is a few hundred tokens, not a few thousand. If you want the extension working tonight, take DeepSeek. If you want it to cost exactly nothing, take GLM-4-Flash and accept the wait.
Model names have to match exactly. This is the single most common
failure. deepseek-flash is not the same string as deepseek-chat,
and a wrong name comes back as an error that sounds like a broken key.
The four steps, same everywhere
- Create an account on the provider's site.
- Find the API keys page in their console. It is usually under account settings or a sidebar item called API Keys, not on the dashboard home.
- Create a new key and copy it immediately. Providers show the full string once. If you close the dialog without copying, delete the key and make another — do not hunt for it.
- Paste it into the extension. Click the ReplyRight icon in your browser toolbar, choose the provider from the Provider menu (this fills in Model and API base URL for you), paste the key into API key, and press Save. You should see Saved. under the button.
Then open Gmail, hit Compose, and click ReplyRight. The setup only has to happen once per browser profile.
When it does not work
- “Could not draft a reply” with an authentication error — the key is wrong, or a space came along with the paste. Copy it again rather than typing it.
- A 404 or “not found” — the base URL is wrong. If you chose a provider
from the menu, this should not happen. Only the Custom option asks you to type a
URL, and some providers need a
/v1suffix while others do not. - Free limit reached — that is ReplyRight's own counter, five drafts a month. There is a Reset monthly counter button in the extension menu, and it also resets on the 1st. It counts drafts, not tokens.
- It works once and then stalls — usually a provider-side concurrency limit on the free tier. GLM-4-Flash is the most likely to hit this.
What “free” means here
Be clear about which free is which, because both get called free and they are different things:
- ReplyRight's five replies a month are free in the sense that we do not charge you and do not take a cut. It is a counter stored in your own browser.
- The model usage is billed by your provider, not by us. On GLM-4-Flash that bill is zero. On DeepSeek it is small. On OpenAI it is small and requires a payment method.
Which means the honest summary of the whole thing: you are paying the model directly instead of paying a markup to a middleman, and the cost of that arrangement is one setup step.
Where the key is stored
The key lives in this browser profile's local extension storage
(chrome.storage.local) and is sent to the API host shown in the
API base URL field — the provider you selected, not to us. It is not synced, not
backed up to an account, and not visible to any ReplyRight server, because there is no
ReplyRight server holding it. If you switch machines you paste it again.
One consequence worth knowing: if you reset or remove the extension, you lose the stored key and paste it again. Revoking a key is done on the provider's side, not here.
ReplyRight drafts replies and flags what a message is really asking for. It is not legal, HR, or financial advice, and it will not invent a date, a price, or a promise you did not make.
If you want the writing part rather than the setup part, the rude email templates are the other half of this problem.