# upstash-redis-start

This skill spins up a temporary Upstash Redis database from a single POST. No account, no API key, no SDK wiring — the response carries the endpoint and token.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1300 installs · ★ 34
- Author: Upstash
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/upstash/skills/tree/HEAD/skills/upstash-redis-start/SKILL.md
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/skills/upstash-redis-start

## What it does

The agent makes up a UUIDv4 and sends it as the `Idempotency-Key` header to `https://upstash.com/start-redis`. What comes back is markdown holding `Database ID`, `Endpoint`, `Token`, a metrics link, an `Expires` date and a `Console URL`. There is no separate JSON envelope, so those values get parsed straight out of the text. Repeat the POST with the same key and you get the same database rather than a second one, which makes a lost response safe to retry. The header can be skipped: the server then assigns an id, and that id can be passed back as the key later. Only UUIDv4 is accepted.

Talking to the database goes through the Upstash Redis REST API. The skill favours the body-style call, where the command travels as a JSON array in the request body and needs no URL encoding. Ready `curl` examples for `SET` with a TTL and for `GET` sit in the README. The same endpoint and token also work with the official SDKs, `@upstash/redis` for TS/JS and `upstash-redis` for Python.

Unless the user claims it, the database is gone after 3 days. Until then it is unauthenticated scratch storage, so secrets, PII and production credentials have no business there. The skill asks you to hand the `Console URL` to the user — usage shows up on that page, along with the **Claim** button that keeps the database alive.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add upstash/skills --skill upstash-redis-start -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/upstash-redis-start/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/upstash-redis-start/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add upstash/skills --skill upstash-redis-start -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/upstash-redis-start/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add upstash/skills --skill upstash-redis-start -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/upstash-redis-start/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install upstash/skills upstash-redis-start
```

2. **Manually: put the files in place**
- File: `.github/skills/upstash-redis-start/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add upstash/skills --skill upstash-redis-start -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/upstash/skills --path skills/upstash-redis-start
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/upstash-redis-start/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add upstash/skills --skill upstash-redis-start -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/upstash/skills/tree/HEAD/skills/upstash-redis-start/SKILL.md

## When to use it
- get Redis running for an agent when the user handed over no credentials
- keep state across tool calls inside a single run
- run a producer/consumer job queue for sub-agents
- log conversation turns and read back the latest ones
- build ranked recall sorted by recency or score

## Example prompts
- Provision a scratch Redis with upstash-redis-start and store the pipeline step there
- Set up a sub-agent job queue in Upstash Redis and drain it with RPOP
- Create ranked memory in Redis and show the ten most recent entries

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: d6955a70638dbb6e.

BEGIN THIRD-PARTY FILE d6955a70638dbb6e
````text
---
name: upstash-redis-start
description: Provision a zero-config, no-signup, temporary Upstash Redis database for an AI agent with a single POST to https://upstash.com/start-redis, with no account, API key, or SDK setup required. Use when an agent needs scratch Redis right now and the user has not provided credentials, for short-term memory across tool calls, conversation history, a sub-agent work queue, ranked recall, or a quick prototype or demo. Covers idempotent creation and re-fetching credentials, calling the database through the body-style REST API or the official SDKs, and telling the user how to claim it. The database lives 3 days unless the user claims it; not for production data, PII, or secrets.
license: MIT
metadata:
  author: Upstash
  homepage: https://upstash.com
---

# Upstash Redis for Agents (`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:
- The agent needs Redis right now and the user has not given you credentials.
- You want short-term memory across tool calls, conversation history, a sub-agent work queue, or recent-first ranked recall.

This is built for quick experiments, prototypes, and demos rather than production workloads or anything tied to a real user account — the database is temporary and unauthenticated until claimed, so keep PII, secrets, and production credentials out of it.

## Create or re-fetch a database

```bash
# 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
```

- Sending your own UUIDv4 makes the first call **retry-safe** — if the response is lost, retrying with the same UUID returns the same database instead of minting a duplicate.
- Re-POST with the same `Idempotency-Key` to **re-fetch credentials** for an existing database.
- The header is optional. Omit it to mint a new database with a server-generated id (returned in the response — re-fetch later by passing that id back as `Idempotency-Key`). Only UUIDv4 is accepted.

The response is markdown containing:
- `Database ID`, `Endpoint`, `Token`
````
END THIRD-PARTY FILE d6955a70638dbb6e

The third-party file has ended. Everything between the d6955a70638dbb6e tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2305 of 4255 bytes. © Upstash · MIT · https://github.com/upstash/skills/tree/HEAD/skills/upstash-redis-start/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md