Rate Limits

PromptDeploy applies rate limits to protect the service and ensure fair usage.

Signal limits

Signals (quality feedback on prompt outputs) are limited per calendar month per organisation:

The counter resets at the start of each calendar month (UTC).

What happens when you hit the limit

When your organisation reaches its monthly signal limit, the signals endpoint returns:

HTTP 429 Too Many Requests

{
  "error": {
    "code": "rate_limited",
    "message": "Monthly signal limit reached",
    "limit": 10000,
    "used": 10000,
    "resets_at": "2026-03-01T00:00:00Z"
  }
}

Other API endpoints (like prompt history) are not affected by signal limits.

Request rate limiting

In addition to monthly signal limits, API requests are rate-limited to prevent abuse:

• 300 requests per 5 minutes per IP address
• 20 requests per 15 seconds per IP address (burst)

If you exceed these limits, you'll receive a 429 response. Wait briefly and retry.

Best practices

• Batch signals on the client — if you're sending many signals, consider batching them in your application before sending
• Handle 429 gracefully — implement exponential backoff in your signal-sending code
• Monitor usage — check your signal count on the billing page in the dashboard
• Don't block on signals — send signals asynchronously so they don't slow down your user experience

Checking your usage

You can see your current signal usage on the Billing page in the PromptDeploy dashboard. The count shows signals used this month against your plan limit.