a6-plugin-limit-count

Configure the Apache APISIX limit-count plugin for rate limiting API requests.

1|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/moonming/a6 --skill a6-plugin-limit-count
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a6-plugin-limit-count
Source: https://github.com/moonming/a6/tree/main/skills/a6-plugin-limit-count
Command: npx skills add https://github.com/moonming/a6 --skill a6-plugin-limit-count

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps manage and control the flow of traffic to your APIs by implementing rate limiting, preventing abuse and ensuring service stability.

Core Features & Use Cases

  • Configurable Rate Limiting: Set specific limits on the number of requests allowed within a given time window.
  • Flexible Keying: Apply limits based on client IP, consumer, or custom variables.
  • Distributed Limiting: Utilize Redis or Redis-cluster for shared rate limiting across multiple APISIX instances.
  • Use Case: Protect your public APIs from being overwhelmed by implementing a limit of 100 requests per minute per client IP address.

Quick Start

Configure a route to allow 100 requests per minute per client IP with a 429 response code.

Frequently Asked Questions about a6-plugin-limit-count

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

FAQPage Schema
How do I configure rate limiting for an API route in APISIX?

To configure rate limiting in APISIX, use the limit-count plugin on a route to set a fixed-window counter for allowed requests. You define the time window, request limit, and rejection response code directly in the route configuration.

Can I apply API traffic control based on client IP or consumer name?

Yes, API traffic control can be applied using flexible keying based on remote client addresses or consumer names. This allows you to enforce granular rate limits per IP or per authenticated consumer on your APISIX gateway.

Does the APISIX limit-count plugin support distributed rate limiting with Redis?

Yes, the APISIX limit-count plugin supports distributed rate limiting by utilizing Redis or Redis-cluster. This shares request counters across multiple APISIX instances to maintain accurate traffic control in a distributed environment.

What is fixed-window rate limiting for API traffic control?

Fixed-window rate limiting restricts the number of API requests allowed within a specific, static time frame. The APISIX limit-count plugin uses this mechanism to reset the request counter at the end of each configured window period.

How do I return a 429 status code when an API exceeds its rate limit?

To return a 429 status code, configure the rejected HTTP response code in your APISIX limit-count plugin settings. When a client exceeds the allowed request count in the time window, the gateway rejects the request with that code.