rate-limiting

Implement Redis-backed and per-endpoint rate limiting policies for ASP.NET Core.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill rate-limiting-agibuild
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rate-limiting
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/rate-limiting
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill rate-limiting-agibuild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill protects your ASP.NET Core applications from abuse and ensures fair resource usage by implementing various rate-limiting strategies.

Core Features & Use Cases

  • Algorithm Variety: Supports fixed window, sliding window, token bucket, and concurrency limiting.
  • Distributed Limiting: Integrates with Redis for scalable, multi-server rate limiting.
  • User/Client Identification: Handles rate limiting based on IP, user identity, API keys, and proxy configurations.
  • Use Case: Protect your public API endpoints from being overwhelmed by implementing a fixed window rate limit of 100 requests per minute per IP address, while applying a stricter limit for login attempts.

Quick Start

Configure rate limiting in your ASP.NET Core application by adding the AddRateLimiter service and UseRateLimiter middleware to your Program.cs file.

Frequently Asked Questions about rate-limiting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement rate limiting in ASP.NET Core to protect my API?

Implement rate limiting in ASP.NET Core by configuring the `AddRateLimiter` service and applying the `UseRateLimiter` middleware in your `Program.cs` file. This protects API endpoints from abuse and ensures fair resource usage.

What rate limiting algorithms are available for ASP.NET Core APIs?

Available rate limiting algorithms include fixed window, sliding window, token bucket, and concurrency limiting. These algorithms prevent service degradation by controlling request throughput across your ASP.NET Core API endpoints.

Can I use Redis for distributed rate limiting in an ASP.NET Core application?

Yes, you can integrate Redis to enable distributed rate limiting for scalable, multi-server ASP.NET Core environments. Redis handles distributed state to ensure accurate throttling across multiple server instances.

How do I apply different rate limiting policies per endpoint in ASP.NET Core?

Apply per-endpoint rate limiting policies by defining specific rules within the ASP.NET Core middleware configuration. You can set a fixed window of 100 requests per minute per IP for general APIs and stricter limits for login attempts.

What client identification methods are supported for API throttling?

API throttling supports client identification based on IP address, user identity, API keys, and proxy configurations. This ensures accurate rate limit enforcement across various client types and network topologies.