# Rate Limits — BrewLogica MCP API

Last Updated: March 2026

BrewLogica enforces rate limits to ensure fair access for all users. Standard data operations have generous limits; AI-powered features have separate monthly quotas.

## API Rate Limits by Plan

| Limit Type                                  | Free Plan           | Pro Plan       |
| -------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| Requests per minute                         | N/A (no MCP access) | 60 req/min     |
| Requests per day                            | N/A                 | 5,000 req/day  |
| Concurrent connections                      | N/A                 | 5 simultaneous |
| Active API tokens                           | 0                   | Multiple tokens |
| AI parse calls/month (parse_brew_text)      | N/A                 | 200/month      |
| AI suggestion calls/month (get_suggestions) | N/A                 | 100/month      |

MCP API access requires a Pro subscription ($49.99/year). Monthly AI quotas reset on the 1st of each calendar month.

## How to Check Your Current Usage

Use the `get_limits` tool (no parameters required):

Prompt: "How many AI requests do I have left this month?"

Example response:

```
AI parse calls:    147 / 200 used this month (53 remaining)
AI suggestions:     61 / 100 used this month (39 remaining)
API requests today: 234 / 5000 used today
Rate limit:        60 req/min
```

## Rate Limit Headers

Every API response includes these headers:

| Header                | Description                                          |
| ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| X-RateLimit-Limit     | Maximum requests allowed per minute                  |
| X-RateLimit-Remaining | Requests remaining in the current minute window      |
| X-RateLimit-Reset     | Unix timestamp when the current window resets        |
| Retry-After           | Seconds to wait before retrying (429 responses only) |

## What Happens When You Hit a Limit?

**Per-minute limit exceeded (429 Too Many Requests)**
The API returns a 429 status with a Retry-After header. Most MCP clients handle this automatically by waiting and retrying.

**Daily limit exceeded**
Standard data operations stop until midnight UTC. Read operations (list, get) continue at a reduced rate of 10 req/min.

**Monthly AI quota exhausted**
`parse_brew_text` and `get_suggestions` return an error until the 1st of the next month. All other MCP tools continue working normally.

## Tips to Stay Within Limits

* Use batch prompts — "Log these 5 brews" works in one call rather than five separate requests

* Use `list_brews` with filters before calling `get_brew` individually

* Check `get_limits` at the start of long AI sessions to see remaining quota

* Revoke unused tokens to reduce credential exposure and keep client access organized

## Related Documentation

* Security & Privacy: [https://brewlogica.app/docs/security](https://brewlogica.app/docs/security)

* MCP Tools Reference: [https://brewlogica.app/docs/tools](https://brewlogica.app/docs/tools)

* MCP Quickstart: [https://brewlogica.app/docs/mcp-quickstart](https://brewlogica.app/docs/mcp-quickstart)