
upstash-ratelimit-js
✓ Official★ 12by upstash · part of upstash/skills
Lightweight guidance for using the Upstash Redis RateLimit TypeScript/JavaScript SDK, including setup steps, basic usage, and pointers to advanced algorithm,…
Lightweight guidance for using the Upstash Redis RateLimit TypeScript/JavaScript SDK, including setup steps, basic usage, and pointers to advanced algorithm,…
Inspect the full instructions your agent will receiveExpandCollapse
This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.
by upstash
Lightweight guidance for using the Upstash Redis RateLimit TypeScript/JavaScript SDK, including setup steps, basic usage, and pointers to advanced algorithm,…
npx skills add https://github.com/upstash/skills --skill upstash-ratelimit-js
Download ZIPGitHub12
Rate Limit TS SDK
Other Skill Files
-
algorithms.md: Describes all available rate‑limiting algorithms and how they behave.
-
pricing-cost.md: Explains pricing, Redis cost implications, and operational considerations.
-
features.md: Lists SDK features such as prefixes, custom keys, and behavioral options.
-
methods-getting-started.md: Full method reference for the SDK's API and getting started guide.
-
traffic-protection.md: Guidance on applying rate limiting for traffic shaping, abuse prevention, and protection patterns.
npx skills add https://github.com/upstash/skills --skill upstash-ratelimit-jsRun this in your project — your agent picks the skill up automatically.
Quick Start
-
Install the SDK and connect to Redis.
-
Create a rate limiter and apply it to incoming operations.
Example:
import { Ratelimit } from "@upstash/ratelimit";
import { Redis } from "@upstash/redis";
const redis = new Redis({ url: " ", token: " " });
const limiter = new Ratelimit({ redis, limiter: Ratelimit.slidingWindow(5, "10s") });
const { success } = await limiter.limit("user-id");
if (!success) {
// throttled
}
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.