Generated banner for Upstash Redis JS
Generated logo for Upstash Redis JS

Upstash Redis JS

UpstashOfficialCreated by Upstash

  • Skill
  • Tool integration
  • Software development
  • MIT
  • No issues found

From the author

Work with the @upstash/redis TypeScript/JavaScript SDK, a serverless HTTP-based Redis client for Next.js, Vercel, Cloudflare Workers, edge runtimes, and Node.js. Use when adding a cache (cache-aside, write-through, TTL and expiration strategies), session storage and user sessions, a key-value store, leaderboards and rankings with sorted sets, counters, distributed locks, queues with lists, streams and consumer groups, sparse index-addressed arrays and ring buffers (ARSET, ARINSERT, ARRING, ARGREP, AROP), embeddings and nearest-neighbour vector search stored inside Redis (VECTOR commands via redis.vector, separate from @upstash/vector), JSON documents, pipelines and MULTI/EXEC transactions, Lua scripting, read replicas, or full-text search, typo-tolerant search, facets, aggregations, and search over Redis stream entries with Upstash Redis Search (different from regular FT.SEARCH; also available for TCP clients via @upstash/search-redis and @upstash/search-ioredis). Also use when migrating from ioredis or
— the description by Upstash

AutoGineer summary

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

This skill provides a complete reference for the @upstash/redis SDK, an HTTP-based Redis client designed for serverless environments like Vercel, Cloudflare Workers, and edge runtimes. It covers core data structures, advanced features like pipelines and Lua scripting, common architectural patterns such as caching and session management, and migration paths from traditional Redis clients. The SDK features automatic serialization of JavaScript types, simplifying data handling for developers.

What it does

  • Provides methods for interacting with Redis data structures including strings, hashes, lists, sets, sorted sets, and JSON.
  • Supports advanced Redis features like pipelines, MULTI/EXEC transactions, and Lua scripting.
  • Includes patterns for implementing caching, rate limiting, distributed locks, and session management.
  • Enables vector search and full-text search capabilities within Redis.
  • Handles automatic serialization and deserialization of native JavaScript types.
  • Offers migration guidance for developers moving from ioredis or node-redis.

When to use it

  • When building serverless applications that require a Redis-compatible key-value store.
  • When implementing caching, session storage, or leaderboards in edge runtimes.
  • When you need to perform atomic operations or complex server-side logic via Lua scripts.
  • When migrating existing Node.js applications to a serverless architecture.
  • When integrating AI agent memory or RAG tools using Redis.

Advantages

  • Serverless-friendly HTTP-based architecture eliminates connection pooling issues.
  • Automatic serialization removes the need for manual JSON parsing.
  • Comprehensive support for modern Redis features including JSON and vector search.
  • Well-defined patterns for common use cases like rate limiting and distributed locks.
  • Seamless integration with popular frameworks like Next.js and Vercel.

Usage examples

“How do I store a user object in Redis using the Upstash SDK?”
The agent will demonstrate using redis.set('user:1', { name: 'Alice' }), highlighting that the SDK automatically handles JSON serialization.
“Show me how to implement a simple counter in Redis.”
The agent will provide code using redis.incr('counter') and explain that the SDK returns the incremented number directly without manual parsing.
“How can I perform multiple operations atomically?”
The agent will explain the use of redis.multi() or pipelines to batch commands and ensure atomic execution.

Install

  1. Download the skill as a ZIP:

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

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

Documentation by Upstash

Upstash Redis SDK - Complete Skills Guide

This directory contains comprehensive guides for using the @upstash/redis SDK. These skill files are designed to help developers and AI assistants understand and use the SDK effectively.

Bundled docs and source

Before writing or debugging SDK code, check node_modules/@upstash/redis/docs/ for bundled docs and node_modules/@upstash/redis/src/ for readable TypeScript source. Read and search the relevant files when present; otherwise use the references in this skill.

Installation

npm install @upstash/redis

Quick Start

Basic Initialization
import { Redis } from "@upstash/redis";

// Initialize with explicit credentials
const redis = new Redis({
  url: "UPSTASH_REDIS_REST_URL",
  token: "UPSTASH_REDIS_REST_TOKEN",
});

// Or initialize from environment variables
const redis = Redis.fromEnv();
Environment Variables

Set these in your .env file:

UPSTASH_REDIS_REST_URL=https://your-redis.upstash.io
UPSTASH_REDIS_REST_TOKEN=your-token-here

No credentials yet? If you're an agent that needs scratch Redis and the user hasn't provided a database, you can mint a temporary one with a single POST to https://upstash.com/start-redis (3-day TTL, no signup).

Skill Files Overview

Data Structures (data-structures/)

Redis data types with auto-serialization examples:

  • strings.md - GET, SET, INCR, DECR, APPEND with automatic type handling

  • hashes.md - HSET, HGET, HMGET with object serialization

  • lists.md - LPUSH, RPUSH, LRANGE with array handling

  • sets.md - SADD, SMEMBERS, set operations

  • sorted-sets.md - ZADD, ZRANGE, ZRANK, leaderboard patterns

  • json.md - JSON.SET, JSON.GET, JSONPath queries for nested objects

  • streams.md - XADD, XREAD, XGROUP, consumer groups

  • arrays.md - ARSET, ARINSERT, ARSCAN, ARGREP, AROP, ring buffers with ARRING on sparse index-addressed arrays

  • vector-indexes.md - VECTOR.CREATE, VECTOR.ADD, VECTOR.QUERY nearest-neighbour search inside Redis via redis.vector

Advanced Features (advanced-features/)

Complex operations and optimizations:

  • auto-pipeline.md - Automatic request batching, performance optimization

  • pipeline-and-transactions.md - Manual pipelines, MULTI/EXEC for atomic operations

  • scripting.md - Lua scripts, EVAL, EVALSHA for server-side logic

Patterns (patterns/)

Common use cases and architectural patterns:

  • caching.md - Cache-aside, write-through, TTL strategies

  • rate-limiting.md - Integration with @upstash/ratelimit package

  • session-management.md - Session storage and user state management

  • distributed-locks.md - Lock implementations, deadlock prevention

  • leaderboard.md - Sorted set leaderboards, real-time rankings

Performance (performance/)

Optimization techniques and best practices:

  • batching-operations.md - MGET, MSET, batch operations

  • pipeline-optimization.md - When to use pipelines, performance tips

  • ttl-expiration.md - Key expiration strategies, memory management

  • data-serialization.md - Deep dive into auto serialization, custom serializers, edge cases

  • error-handling.md - Error types, retry strategies, timeout handling, debugging tips

  • redis-replicas.md - Global database setup, read replicas, read-your-writes consistency

Full-text search, filtering, and aggregation extension for Redis:

  • overview.md - Schema definition, field types, pitfalls, package overview

  • commands/querying.md - Query and count with filters, pagination, sorting, highlighting

  • commands/aggregating.md - Metric aggregations ($avg, $sum, $stats), bucket aggregations ($terms, $range, $histogram, $facet)

  • commands/index-management.md - Create, describe, drop indexes (including stream indexes over XADD entries), waitIndexing

  • commands/aliases.md - Index aliases for zero-downtime reindexing

  • adapters.md - Using search with node-redis and ioredis via @upstash/search-redis and @upstash/search-ioredis

Migrations (migrations/)

Migration guides from other libraries:

  • from-ioredis.md - Migration from ioredis, key differences, serialization changes

  • from-redis-node.md - Migration from node-redis, API differences

Common Mistakes (Especially for LLMs)

❌ Mistake 1: Treating Everything as Strings
// ❌ WRONG - Don't do this with @upstash/redis
await redis.set("count", "42"); // Stored as string "42"
const count = await redis.get("count");
const incremented = parseInt(count) + 1; // Manual parsing needed

// ✅ CORRECT - Let the SDK handle it
await redis.set("count", 42); // Stored as number
const count = await redis.get("count");
const incremented = count + 1; // Just use it
❌ Mistake 2: Manual JSON Serialization
// ❌ WRONG - Unnecessary with @upstash/redis
await redis.set("user", JSON.stringify({ name: "Alice" }));
const user = JSON.parse(await redis.get("user"));

// ✅ CORRECT - Automatic handling
await redis.set("user", { name: "Alice" });
const user = await redis.get("user");

Quick Command Reference

// Strings
await redis.set("key", "value");
await redis.get("key");
await redis.incr("counter");
await redis.decr("counter");

// Hashes
await redis.hset("user:1", { name: "Alice", age: 30 });
await redis.hget("user:1", "name");
await redis.hgetall("user:1");

// Lists
await redis.lpush("tasks", "task1", "task2");
await redis.rpush("tasks", "task3");
await redis.lrange("tasks", 0, -1);

// Sets
await redis.sadd("tags", "javascript", "redis");
await redis.smembers("tags");

// Sorted Sets
await redis.zadd("leaderboard", { score: 100, member: "player1" });
await redis.zrange("leaderboard", 0, -1);

// JSON
await redis.json.set("user:1", "$", { name: "Alice", address: { city: "NYC" } });
await redis.json.get("user:1");

// Expiration
await redis.setex("session", 3600, { userId: "123" });
await redis.expire("key", 60);
await redis.ttl("key");

Best Practices

  1. Use environment variables for credentials, never hardcode

  2. Leverage auto-serialization - pass native JavaScript types

  3. Use TypeScript types for better type safety

  4. Set appropriate TTLs to manage memory

  5. Use pipelines for multiple operations

  6. Namespace your keys (e.g., user:123, session:abc)

AI agents: use AgentKit

For agent state on Redis — memory, chat history, RAG search tools, tool caching, rate limiting, chat persistence, resumable streams, locks — use Upstash AgentKit instead of hand-rolling it on @upstash/redis. Pick the adapter for the framework and follow its docs page:

FrameworkPackageDocs
Vercel AI SDK@upstash/agentkit-ai-sdkhttps://upstash.com/docs/redis/sdks/agentkit/ai-sdk
TanStack AI@upstash/agentkit-tanstack-aihttps://upstash.com/docs/redis/sdks/agentkit/tanstack-ai
Vercel Eve@upstash/agentkit-eve, @upstash/agentkit-eve-extensionhttps://upstash.com/docs/redis/sdks/agentkit/eve

Resources

Getting Help

For detailed information on specific topics, refer to the individual skill files in the skills/ directory. Each file contains comprehensive examples, use cases, and best practices for its topic.

Files

search/overview.md

Overview

Redis Search is a full-text search and secondary indexing extension for Upstash Redis. It provides powerful APIs for querying, filtering, and aggregating data stored in Redis keys. Built on Tantivy, it supports text search with stemming, fuzzy matching, faceted navigation, and complex aggregations.

Good For

  • Full-text search over Redis data (strings, JSON, hashes)

  • Filtering and sorting with type-safe queries

  • Aggregations and analytics (averages, histograms, facets)

  • Autocomplete and typo-tolerant search

  • Faceted navigation (e-commerce categories, filters)

Packages

  • @upstash/redis - The primary SDK. Access search via redis.search (works over HTTP)

  • @upstash/search-redis - Adapter for the redis (node-redis) TCP client

  • @upstash/search-ioredis - Adapter for the ioredis TCP client

All three packages expose the same search API. See adapters.md for TCP client setup.

Schema

Schemas define which fields are indexed and how. Use the s schema builder for type-safe definitions:

import { Redis, s } from "@upstash/redis";

const redis = Redis.fromEnv();

const index = await redis.search.createIndex({
  name: "products",
  prefix: "product:",
  dataType: "json",
  schema: s.object({
    name: s.string(), // TEXT - full-text searchable
    description: s.string().noStem(), // TEXT without stemming
    sku: s.string().noTokenize(), // TEXT stored as-is (no splitting)
    price: s.number("F64"), // floating point number
    stock: s.number("U64"), // unsigned 64-bit integer
    inStock: s.boolean(), // boolean
    createdAt: s.date(), // date
    category: s.keyword(), // exact-match keyword
    brand: s.facet(), // facet for aggregations
  }),
});
Field Types
BuilderRedis TypeTypeScriptUse Case
s.string()TEXTstringFull-text searchable text
s.number()F64/U64/I64numberNumeric values, ranges
s.boolean()BOOLbooleanTrue/false filtering
s.date()DATEstringDate range queries
s.keyword()KEYWORDstringExact match, lexicographic range
s.facet()FACETstringFaceted aggregations
s.object({})(nested)objectNested field groups
Field Options
  • .noTokenize() - (TEXT only) Don't split on whitespace/punctuation. Use for SKUs, URLs, emails

  • .noStem() - (TEXT only) Don't reduce words to stems. Use for brand names, proper nouns

  • .fast() - (BOOL, DATE) Enable fast filtering

  • .from("fieldName") - Map index field to a different field name in the stored data

Data Types
  • "json" - Index JSON documents stored with redis.json.set() or redis.set(). Supports nested schemas with s.object()

  • "string" - Index JSON strings stored with redis.set(). Supports nested schemas

  • "hash" - Index Redis hashes stored with redis.hset(). Flat schemas only (no nesting)

  • "stream" - Index entries added with redis.xadd(). Flat schemas only; use stream for the exact stream key instead of prefix

Commands

For detailed usage of each command category, see:

Pitfalls

There is no index.upsert() or index.add() method. You store data using standard Redis commands (set, json.set, hset, or xadd for stream indexes), and the search index automatically picks up keys matching its prefix (or entries of its stream).

// Create the index
const index = await redis.search.createIndex({
  name: "users",
  prefix: "user:",
  dataType: "json",
  schema: s.object({ name: s.string(), age: s.number("U64") }),
});

// Upsert data with regular Redis commands
await redis.json.set("user:1", "$", { name: "Alice", age: 30 });
await redis.json.set("user:2", "$", { name: "Bob", age: 25 });

// Wait for the index to process the new data
await index.waitIndexing();

// Now you can query
const results = await index.query({
  filter: { name: { $eq: "Alice" } },
});
Always call waitIndexing after data changes

Index updates are batched. After upserting or deleting data, the index may not immediately reflect the changes. Call waitIndexing() to block until all pending documents are processed.

// Batch upsert many documents
for (const product of products) {
  await redis.json.set(`product:${product.id}`, "$", product);
}

// Call waitIndexing ONCE after all upserts (not after each one)
await index.waitIndexing();

// Now queries will return up-to-date results
const results = await index.query({ filter: { category: { $eq: "electronics" } } });
Tokenization splits text at word boundaries

TEXT fields are tokenized by default: "hello-world" becomes ["hello", "world"]. An $eq filter for "hello-world" matches because it finds the substring. But if you need exact matching of the full string (e.g., SKUs, URLs), use .noTokenize().

Stemming reduces words to roots

By default, TEXT fields apply language-specific stemming: "running" is stored as "run". This means $regex patterns won't match the original form. Disable with .noStem() for brand names or when you need exact word forms.

$mustNot cannot be used alone

$mustNot filters only exclude documents. Using $mustNot alone returns no results. Always combine it with $must or $should:

// Won't work - returns nothing
{ $mustNot: [{ status: { $eq: "archived" } }] }

// Correct - exclude within a broader match
{ $must: [{ category: { $eq: "electronics" } }], $mustNot: [{ status: { $eq: "archived" } }] }
SCOREFUNC and ORDERBY are mutually exclusive

You cannot use scoreFunc and orderBy in the same query. Use orderBy for deterministic sorting, scoreFunc for relevance-based ranking.

Resources

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 Node.js

Security

No issues found by our static scan· No issues found

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-js · 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.

Download ZIP

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