API keys
One API key works for both MCP and the REST API. A key only acts on your own account and stops working the moment you revoke it.
Creating a key
- Open Waper → Settings → API & MCP and click Create key;
- Copy it — it's shown only once;
- Under "Connect an app" on the same page, pick your client (Claude Code, Cursor, VS Code, Claude Desktop, Codex and more) and copy the ready-made config or command, with your new key already filled in. There are runnable curl examples for the REST API too.
Your email must be verified to create keys.
Authenticating
Authorization: Bearer wpr_<key>
Managing keys
The list refreshes when you reopen settings or return to the Waper window or browser tab. First use is recorded immediately; repeated use within the next hour does not update the timestamp each time.
- The list shows each key's prefix and last use; up to 10 keys per account;
- Revoking is immediate and permanent;
- Use one key per client — losing one doesn't affect the rest;
- When a key uses more than 1,800 credits within an hour, we email the account's address with which key it was and where the credits went. If that was you, there is nothing to do and the key keeps working; if it was not, revoke the key on this page. We send this at most once a day per key, and it is only a heads-up: no request is blocked.
Rate limits
- 60 requests per minute per account (shared across MCP and REST);
- Each key can start at most 10 actions that spend credits a minute (transcribing new audio or video, deep research); beyond that you get 429
RATE_LIMITED and can try again a minute later. There is no daily cap;
- Agent turns charge actual model cost in credits (see Credits);
- Create-style REST calls accept an
Idempotency-Key header (MCP has none) — the same key runs at most once within 24 hours.