A leaked signing key lets anyone send requests that look like they came from QStash; keep both keys secret. [3]
Guides · other · Everyday developer services
Upstash QStash
Open QStash in the Upstash Console, pick a region, and copy the QStash token and the current and next signing keys.
Researched · not yet run liveLast researched 25 October 2026 · Upstash · provider site
Have ready
- An Upstash account (same account as upstash/redis).
Steps
Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.
Create or sign in to an Upstash account
The person signs up or logs in at the Upstash Console. verapli never creates the account.
Where: https://console.upstash.com/
Copy the QStash token and signing keys
Open the QStash tab, choose the region, and copy QSTASH_TOKEN from the Quickstart section plus QSTASH_CURRENT_SIGNING_KEY and QSTASH_NEXT_SIGNING_KEY.
verapli captures
QSTASH_TOKENhere by plain code: encrypted in your browser, never shown to AI.Where: https://console.upstash.com/qstash
Terms and gotchas
Plain-English summary, not legal advice. Each card links its source.
What you end up with
| Env var | Secret | Format | What it is |
|---|---|---|---|
QSTASH_TOKEN | secret | Token for publishing messages to QStash. | |
QSTASH_CURRENT_SIGNING_KEY | secret | Current key for verifying that requests came from QStash. | |
QSTASH_NEXT_SIGNING_KEY | secret | Next signing key, used during key rotation. |
For agents
The same entry as JSON: /api/v1/entries/upstash/qstash · requirements /api/v1/requirements/upstash/qstash · terms /api/v1/terms/upstash/qstash.
claude mcp add --transport http verapli https://verapli.com/mcp
> "What do I need for Upstash QStash, and how long will it take?"
→ tools/call requirements { "provider_id": "upstash/qstash" }Sources
- QStash getting started QStash tab in the Upstash Console, choose a region, copy QSTASH_TOKEN from the Quickstart section. · accessed 25 October 2026 · official
- QStash Vercel and Next.js quickstart Env vars QSTASH_TOKEN, QSTASH_CURRENT_SIGNING_KEY and QSTASH_NEXT_SIGNING_KEY, all copied from the QStash dashboard. · accessed 25 October 2026 · official
- Verify signatures Receiver takes currentSigningKey and nextSigningKey; keep signing keys secure since leaks allow forged requests; pass the raw body when verifying. · accessed 25 October 2026 · official
- QStash pricing Free plan 1,000 messages per day; pay as you go $1 per 100K messages. · accessed 25 October 2026 · official
- Stripe Projects provider catalogue Upstash is listed in the Stripe Projects catalogue as upstash/redis with Messaging among its categories; QStash is not broken out as a separate catalogue service. · accessed 25 October 2026 · official
Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Upstash is not affiliated with verapli.