Skip to main content

Documentation Index

Fetch the complete documentation index at: https://promptwatch.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

The Promptwatch API enforces two layers of rate limiting to keep the platform stable and fair across customers.

​
Per-IP Limit

All HTTP requests are rate-limited to 1,000 requests per minute per IP address. This limit applies uniformly to every endpoint and is independent of authentication.

​
Per-Plan Hourly Quota

Authenticated requests (REST /api/v1, REST /api/v2, and the MCP server at /mcp) share a per-organization hourly quota sized by your subscription plan. Every API key tied to your organization draws from the same hourly bucket — there is no separate counter per key, and the MCP and REST surfaces share the bucket as well.
PlanRequests / hour
Explore100
Solo500
Startup2,000
Business10,000
Enterprise50,000
The window is a fixed UTC hour: the counter resets at the top of every hour (HH:00:00 UTC). If you need a higher limit, contact us.

​
Rate Limit Headers

Every authenticated API response includes the per-organization quota state:
HeaderDescription
X-RateLimit-LimitMaximum requests allowed in the current hourly window
X-RateLimit-RemainingRequests remaining in the current window
X-RateLimit-ResetUnix timestamp (seconds) when the current window resets
Retry-AfterSeconds to wait before retrying (only set on 429 responses)

​
429 Response

When you exceed either limit you receive a 429 Too Many Requests response. The per-IP limiter returns: 
{
  "code": "RATE_LIMITED",
  "message": "Too many requests, please slow down",
  "statusCode": 429
}
The per-organization hourly limiter returns: 
{
  "error": "Too Many Requests",
  "message": "You've hit your hourly API request limit of 500 requests. Try again in 30 minutes, or upgrade your plan to increase your limit.",
  "retryAfter": 1800,
  "limit": 500,
  "remaining": 0
}
Use Retry-After (or X-RateLimit-Reset) to decide when to retry rather than backing off arbitrarily.

​
Best Practices

​
Cache Responses

Cache static or rarely-changing data:
  • Models: Cache for 24 hours
  • Monitors: Cache for 1 hour
  • Analytics: Cache based on date range

​
Spread Traffic

Because the hourly quota is shared across MCP and REST and across all API keys in your organization, large bursts that exhaust the bucket in the first minute will cause 429s for the rest of the hour. Pace recurring jobs (analytics syncs, backfills) across the window when possible.

​
Fair Use Policy

Please use the API responsibly:
  • Don’t make unnecessary requests
  • Implement caching where appropriate
  • Use batch operations when available
  • Respect rate limit headers
Abuse of the API may result in temporary or permanent suspension of access.

​
Increasing Limits

Need higher limits for your use case?

Contact Us

Contact our team to discuss custom rate limits for enterprise needs

​
Need Help?