From upstash
Provision a zero-config, no-signup Upstash Redis database for an AI agent via a single POST to `https://upstash.com/start-redis`. Use when an agent needs scratch Redis for short-term memory, conversation history, sub-agent work queues, or ranked recall and the user has not provided credentials. The database lives 3 days unless the user claims it.
npx claudepluginhub upstash/skills --plugin upstashThis skill uses the workspace's default tool permissions.
A zero-config Redis database for AI agents — **no signup, no UI, no SDK setup**. One HTTP request returns a working endpoint + token. Databases live for **3 days** unless the user claims them.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
start-redis)A zero-config Redis database for AI agents — no signup, no UI, no SDK setup. One HTTP request returns a working endpoint + token. Databases live for 3 days unless the user claims them.
Use this when:
Do not use this for: production workloads, anything tied to a user account, or anything storing PII / secrets / production credentials. The database is temporary and unauthenticated until claimed.
# Generate a fresh UUIDv4 yourself, then POST it as the Idempotency-Key.
# The UUIDv4 you send becomes the database id.
curl -X POST -H "Idempotency-Key: <uuidv4>" https://upstash.com/start-redis
Idempotency-Key to re-fetch credentials for an existing database.Idempotency-Key). Only UUIDv4 is accepted.The response is markdown containing:
Database ID, Endpoint, TokenMetrics URL (JSON: uptime, commands, keys, throughput, memory, bandwidth)Expires dateConsole URL to share with the user (where they view usage and click Claim to keep the database)Parse these out of the markdown response and use them directly — there is no separate JSON envelope.
The returned endpoint speaks the Upstash Redis REST API. Prefer the body-style form: POST a JSON array as the body so you don't have to URL-encode the command.
# SET with TTL
curl https://<endpoint> \
-H "Authorization: Bearer <token>" \
-d '["SET","session:abc","{\"step\":2}","EX","3600"]'
# GET
curl https://<endpoint> \
-H "Authorization: Bearer <token>" \
-d '["GET","session:abc"]'
You can also use the official SDKs against the same endpoint + token (@upstash/redis for TS/JS, upstash-redis for Python).
| Need | Commands |
|---|---|
| Short-term memory across tool calls in one run | SET key value EX <ttl> / GET key |
| Conversation / turn-by-turn log | LPUSH chat:<user> <json> / LRANGE chat:<user> 0 20 |
| Sub-agent work queue (producer/consumer) | LPUSH jobs <json> / RPOP jobs |
| Ranked memory (recent-first or score-first) | ZADD memories <score> <member> / ZREVRANGE memories 0 9 |
After provisioning, surface the console URL from the response to the user. Make clear that:
GET doc): https://upstash.com/start-redis