Skip to content
cccskills
Official · UpstashFreePublished on GitHub

upstash-redis-start

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 English summary is being prepared. Showing the original description.

upstash/skills
Works withRedis
See how to install

Files included (1)

  • SKILL.md4.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

upstash

Official · UpstashFree

Work with any Upstash product, SDK, or tool, including serverless Redis (caching, sessions, leaderboards, key-value storage), Ratelimit (rate limiting and throttling), QStash (message queue, cron schedules, background jobs), Workflow (durable long-running functions), Vector (vector database for embeddings, semantic search, and RAG), Search (full-text and semantic search), Box (sandboxed cloud containers for AI agents, TypeScript/JavaScript and Python), Blob (serverless S3-compatible file storage with direct browser uploads), the Upstash CLI, and no-signup scratch Redis for agents. Use when the user mentions Upstash or needs any of these capabilities in a serverless, edge, or Node.js app.

The English summary is being prepared. Showing the original description.

upstash/skills33Updated Oct 23, 2026

upstash-blob-js

Official · UpstashFree

Work with the @upstash/blob TypeScript/JavaScript SDK for S3-compatible object storage with direct browser uploads, presigned URLs, multipart, and signed reads. Use when storing files or blobs, uploading avatars, images, videos, attachments or user documents, letting a browser upload straight to storage without proxying bytes through a server, generating public or time-limited signed URLs, serving private files, streaming large files with pause and resume, setting cache headers on stored objects, or reaching an S3-compatible bucket from the AWS SDK.

The English summary is being prepared. Showing the original description.

upstash/skills33Updated Oct 23, 2026

upstash-box-cli

Official · UpstashFree

Drive an Upstash Box (a remote sandboxed workspace) from the terminal with the `box` CLI. Use when asked to run commands, edit files, clone repos, run builds or tests, publish a public URL, browse or screenshot a page, open a pull request or issue with a screenshot attached, schedule recurring work, run an AI agent, or do any work inside a box rather than on this machine.

The English summary is being prepared. Showing the original description.

upstash/skills33Updated Oct 23, 2026

upstash-box-js

Official · UpstashFree

Work with the @upstash/box TypeScript/JavaScript SDK for sandboxed cloud containers with AI agents, shell, filesystem, git, cron schedules, snapshots, and a headless browser. Use when building with Upstash Box, creating a sandbox or isolated environment to run untrusted or agent-generated code, running AI coding agents in containers, giving an agent a cloud dev environment with a shell and repository, browser automation from a box, scheduling recurring jobs inside a box, saving and restoring snapshots, or orchestrating parallel boxes.

The English summary is being prepared. Showing the original description.

upstash/skills33Updated Oct 23, 2026

upstash-box-py

Official · UpstashFree

Work with the upstash-box Python SDK for sandboxed cloud containers with AI agents, shell, filesystem, git, cron schedules, snapshots, and a headless browser. Use when building with Upstash Box in Python, creating a sandbox or isolated environment to run untrusted or agent-generated code, running AI coding agents in containers, giving an agent a cloud dev environment with a shell and repository, browser automation from a box, scheduling recurring jobs inside a box, saving and restoring snapshots, or orchestrating parallel boxes.

The English summary is being prepared. Showing the original description.

upstash/skills33Updated Oct 23, 2026

upstash-box-remote-work

Official · UpstashFree

Do work in an Upstash Box, a sandboxed cloud container driven through the remote Upstash MCP server (mcp.upstash.com), instead of on the local machine. Use when the user asks to run, build, test, clone, or edit something remotely, in a sandbox, in the cloud, or in a box, when the deliverable is a pull request, a public preview URL, or a screenshot of a running app, when the local machine cannot deliver (no GitHub login for gh, no way to expose a port, a dirty or slow local checkout), when several independent tasks should run in parallel on separate machines, a code factory that turns a list of tasks into a list of pull requests, or when the deliverable is a video, screen recording, demo or timelapse of a browser, web app, terminal program or agent run. Applies whenever the session has the box_* and blob_* MCP tools, even when Upstash is not named.

The English summary is being prepared. Showing the original description.

upstash/skills33Updated Oct 23, 2026

See all skills by upstash

Report a problem with this skill