How does this skill handle user privacy?

It uses an anonymous identification method by creating a SHA-256 hash of the user's IP address and User-Agent, ensuring that no personally identifiable information (PII) is stored in the database.

What database tools are required for this implementation?

The skill is optimized for Drizzle ORM, though the logic can be adapted for other SQL-based ORMs or direct database queries.

Does it support CORS-enabled APIs?

Yes, the provided implementation patterns include returning the appropriate CORS headers even when a 429 Rate Limit error occurs.

Can I set different limits for different features?

Yes, the skill includes patterns for adding new columns to the usage tracking table to monitor and limit different features independently.

How does the 24-hour reset work?

The logic compares the current timestamp with the 'lastResetAt' field in the database; if more than 24 hours have passed, the counter is automatically reset to zero on the next request.

Rate Limit Setup

Name: Rate Limit Setup
Author: AppleLamps

byAppleLamps

API 开发

Implements database-backed rate limiting and usage tracking for API endpoints to prevent resource abuse.

关于

This skill provides a standardized framework for implementing rate limiting and usage tracking within Next.js applications using Drizzle ORM. It enables developers to protect API endpoints by identifying users through anonymous SHA-256 hashing of IP addresses and User-Agents, enforcing customizable quotas (such as daily limits), and handling 429 'Too Many Requests' responses with automatic reset logic. It is ideal for managing resource-intensive tasks like AI image generation or preventing general API scraping.

主要功能

Automatic 24-hour reset logic for resource quotas
Standardized 429 Too Many Requests status code responses
Anonymous user identification via SHA-256 hashing of IP and User-Agent
0 GitHub stars
Database-backed usage tracking with Drizzle ORM integration
Extensible schema for tracking multiple independent features

使用场景

Throttling public API access to prevent cost overruns and server abuse
Tracking usage metrics across different app features without storing PII
Limiting premium image generation requests to 2 per day for anonymous users

关于

主要功能

Automatic 24-hour reset logic for resource quotas
Standardized 429 Too Many Requests status code responses
Anonymous user identification via SHA-256 hashing of IP and User-Agent
0 GitHub stars
Database-backed usage tracking with Drizzle ORM integration
Extensible schema for tracking multiple independent features

使用场景

Throttling public API access to prevent cost overruns and server abuse
Tracking usage metrics across different app features without storing PII
Limiting premium image generation requests to 2 per day for anonymous users