Rate Limiting Guide

Learn how to work within rate limits and optimize your API usage.

Understanding Rate Limits

Each API call counts as one request:

Batch operations may count as multiple requests.

When you hit rate limits, you'll receive:

Error 429: Too Many Requests
Retry-After: 60 seconds

BlokMCP automatically handles rate limiting:

For large operations, pace your requests:

For 500 stories to publish:
- Process in batches of 50
- Wait 60 seconds between batches
- Should take ~10 minutes total

Instead of:

For each of 100 stories:
  - Get story
  - Update story
  - Publish story
= 300 requests

Do this:

- Get all 100 stories (1 request with pagination)
- Update all in batch
- Publish all in batch
= ~10 requests

Cache frequently accessed data:

Only fetch what you need:

# Good: Fetch specific fields
"Get title and slug for all blog posts"

# Bad: Fetch everything
"Get all data for all stories"

Show me my current API usage:
- Requests this minute
- Requests today
- Requests this month
- Percentage of monthly limit used

Set up alerts in dashboard:

Consider upgrading if you:

Hitting rate limits? Ask Claude to help optimize your API usage!