Generated banner for Upstash Redis Start
Generated logo for Upstash Redis Start

Upstash Redis Start

UpstashOfficialCreated by Upstash

  • Skill
  • Workflow
  • Data and AI
  • MIT
  • Low risk

From the author

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.
— the description by Upstash

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The upstash-redis-start skill enables AI agents to instantly provision temporary Redis databases for scratch storage. By making a single HTTP request, agents receive an endpoint and token, allowing for immediate use of Redis for short-term memory, conversation logs, or task queues. This service is designed for rapid prototyping and ephemeral agent tasks, with databases expiring after three days unless claimed by the user. It supports both a body-style REST API and official SDKs, providing a seamless way to handle state without manual infrastructure configuration.

What it does

  • Provisions temporary Redis databases via a single HTTP POST request.
  • Supports idempotent creation using UUIDv4 keys to ensure retry safety.
  • Provides endpoint and authentication tokens for immediate database access.
  • Enables interaction via body-style REST API or official language-specific SDKs.
  • Generates a console URL for users to monitor usage and claim the database.
  • Facilitates common agent patterns like work queues, ranked memory, and conversation logging.

When to use it

  • When an agent requires immediate scratch storage without existing user credentials.
  • For managing short-term memory across multiple tool calls in a single session.
  • When building prototypes or demos that require a temporary data store.
  • For implementing sub-agent work queues or turn-by-turn conversation logs.
  • When you need to perform ranked recall or recent-first memory operations.

Advantages

  • Zero-config setup with no signup or API key management required.
  • Idempotent creation prevents duplicate database generation during retries.
  • Flexible interaction via simple REST API or standard SDKs.
  • Clear lifecycle management with a 3-day expiration period.
  • Easy transition path for users to claim and persist temporary databases.

Usage examples

“I need a temporary Redis instance to store my agent's current conversation history.”
The agent calls the start-redis endpoint, receives the connection details, and begins using LPUSH and LRANGE commands to manage the chat log.
“Set up a work queue for my sub-agents to process tasks.”
The agent provisions a new Redis database and uses LPUSH to add jobs to the queue and RPOP to retrieve them for processing.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/upstash/upstash-redis-start/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip upstash-redis-start.zip -d .agents/skills

Documentation by Upstash

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

# 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

  • Metrics URL (JSON: uptime, commands, keys, throughput, memory, bandwidth)

  • Expires date

  • Console URL to share with the user (where they view usage and click Claim to keep the database)

  • An inline quickstart for the body-style REST API

Parse these out of the markdown response and use them directly — there is no separate JSON envelope.

Calling the database (body-style REST)

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).

Common agent patterns

NeedCommands
Short-term memory across tool calls in one runSET key value EX <ttl> / GET key
Conversation / turn-by-turn logLPUSH 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

Tell the user

After provisioning, surface the console URL from the response to the user. Make clear that:

  • The database expires in 3 days.

  • They can view usage at the console URL and click Claim to keep it.

  • This is unauthenticated scratch storage — don't put secrets or PII in it.

Reference

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs network access

Security

What our scanner noticed· Low risk

  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Upstash
Publisher
Upstash (Official)
Source
upstash/skills · skills/upstash-redis-start · commit 9f9e3e5
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Upstash or Upstash.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download upstash-redis-start.zip