> ## Documentation Index > Fetch the complete documentation index at: https://docs.iotools.cloud/llms.txt > Use this file to discover all available pages before exploring further. # Rate Limit Calculator > Convert an API rate limit into requests/second, /minute, /hour and /day, plan multi-worker throughput with staggered start offsets, budget a daily request quota, and turn a 429 Retry-After response into an exponential backoff schedule. [Try Rate Limit Calculator in your browser →](https://iotools.cloud/tool/rate-limit-calc/) ## OpenAPI ````yaml https://api.iotools.cloud/v1/openapi post /v1/tool/rate-limit-calc openapi: 3.1.0 info: title: iotools.cloud API version: 1.0.0 description: >- Run any iotools.cloud tool over HTTP. Authenticate with `Authorization: Bearer iot_live_…`. **Only `POST /v1/tool/{slug}` costs credits.** Every GET here — the catalog, a tool's schema, your balance — is free. A tool call is charged its own weight or your plan's per-call minimum, whichever is larger; `x-iotools-credit-cost` on each operation is quoted at the free-tier minimum, and `GET /v1/tools/list` returns the exact figure for your key. `GET /v1/me/credits` reports what you have left, and `GET /v1/me/usage` reports what it went on. Failures are RFC 9457 problem documents — branch on `code`. servers: - url: https://api.iotools.cloud description: Production security: - bearerAuth: [] tags: - name: Catalog description: Find a tool and read its contract. Free. - name: Converters description: >- Convert between formats, encodings, and units — Base64, CSV and JSON, timestamps, and more. Fast, free, and processed right in your browser. - name: Formatters description: >- Format, beautify, minify, and validate code and data — JSON, HTML, CSS, SQL, and regex. Clean up messy input in one click, with nothing to upload. - name: Generators description: >- Generate exactly what you need and on demand — passwords, UUIDs, QR codes, hashes, random numbers, and more. Secure, instant, and free. - name: Calculators description: >- Crunch the numbers fast — from everyday math to specialized conversions and unit work. Free online calculators that run entirely in your browser. - name: Editors description: >- Edit and transform text, code, and images with quick, focused editors that run entirely in your browser — nothing to install, and no sign-up needed. - name: Utilities description: >- Everyday developer and web utilities — DNS and IP lookups, redirect and certificate checkers, and other quick diagnostics. Free and privacy-friendly. - name: Account description: Your key's allowance, limits and usage history. paths: /v1/tool/rate-limit-calc: post: tags: - Calculators summary: Rate Limit Calculator description: >- Convert an API rate limit into requests/second, /minute, /hour and /day, plan multi-worker throughput with staggered start offsets, budget a daily request quota, and turn a 429 Retry-After response into an exponential backoff schedule. [Try Rate Limit Calculator in your browser →](https://iotools.cloud/tool/rate-limit-calc/) operationId: run_rate_limit_calc requestBody: required: false content: application/json: schema: type: object properties: rateLimit: type: number description: Rate limit minimum: 0 maximum: 100000000 timeUnit: enum: - second - minute - hour - day description: Per workers: type: number description: Number of workers minimum: 1 maximum: 1000 dailyLimit: type: number description: Daily request limit minimum: 0 maximum: 100000000 activeHours: type: number description: Active hours per day minimum: 1 maximum: 24 retryAfter: type: number description: Retry-After (seconds) minimum: 0 maximum: 86400 requestCount: type: number description: Requests sent before 429 minimum: 0 maximum: 100000000 timeWindow: type: number description: Time window (seconds) minimum: 0 maximum: 86400 required: [] examples: 5_000_requests_hour_1_worker_100k_day_quota_429_after_100_req_60s: summary: >- 5,000 requests/hour, 1 worker, 100k/day quota, 429 after 100 req/60s value: rateLimit: '5000' timeUnit: hour workers: '1' dailyLimit: '100000' activeHours: '24' retryAfter: '60' requestCount: '100' timeWindow: '60' stripe_style_100_req_sec_across_3_workers_quota_backoff_skipped: summary: >- Stripe-style 100 req/sec across 3 workers (quota/backoff skipped) value: rateLimit: '100' timeUnit: second workers: '3' dailyLimit: '0' activeHours: '24' retryAfter: '0' requestCount: '0' timeWindow: '0' 429_backoff_only_250_requests_in_60s_retry_after_30s_rate_quota_skipped: summary: >- 429 backoff only: 250 requests in 60s, Retry-After 30s (rate/quota skipped) value: rateLimit: '0' timeUnit: minute workers: '1' dailyLimit: '0' activeHours: '24' retryAfter: '30' requestCount: '250' timeWindow: '60' responses: '200': description: Tool output content: application/json: examples: 5_000_requests_hour_1_worker_100k_day_quota_429_after_100_req_60s: summary: >- 5,000 requests/hour, 1 worker, 100k/day quota, 429 after 100 req/60s value: tool: rate-limit-calc tool_version: 1.0.1 outputs: rateOutput: - metric: Input value: 5,000 requests per hour - metric: Requests Per Second (RPS) value: '1.39' - metric: Requests Per Minute value: '83.33' - metric: Requests Per Hour value: 5,000 - metric: Requests Per Day value: 120,000 - metric: Min Delay Between Requests value: 720 ms - metric: Recommended Delay (10% buffer) value: 792 ms - metric: Burst Capacity value: >- Up to 5,000 requests at the start of each hour, then pace at 1 request every 792 ms for the rest of the hour. workerOutput: - metric: Workers value: '1' - metric: Per-Worker Rate Limit value: 1.39 RPS - metric: Per-Worker Delay value: 720 ms - metric: Total Throughput Per Second value: '1.39' - metric: Total Throughput Per Minute value: '83.33' - metric: Total Throughput Per Hour value: 5,000 quotaOutput: - metric: Daily Limit value: 100,000 requests over 24 active hour(s) - metric: Requests Per Hour value: 4,166.67 - metric: Requests Per Minute value: '69.44' - metric: Requests Per Second value: '1.16' - metric: Safe Delay Between Requests value: 950.4 ms - metric: Burst Allowance value: >- ~416 requests (10% of hourly) at the start of each hour, then pace the remaining 3,751 over 54 minutes (1.16 req/sec). backoffOutput: - metric: Scenario value: Got 429 after 100 requests in 60s - metric: Actual Rate You Were Sending value: 1.67 req/sec - metric: Estimated Rate Limit value: ~100 req / 60s - metric: Recommended New Delay value: 900 ms - metric: Backoff Attempt 1 value: 60 seconds - metric: Backoff Attempt 2 value: 120 seconds - metric: Backoff Attempt 3 value: 240 seconds - metric: Backoff Attempt 4 value: 480 seconds - metric: Backoff Attempt 5 value: 960 seconds - metric: Backoff Attempt 6 value: 1,920 seconds - metric: Jittered Attempt 1 value: 60 - 90 seconds - metric: Jittered Attempt 2 value: 120 - 180 seconds - metric: Jittered Attempt 3 value: 240 - 360 seconds - metric: Jittered Attempt 4 value: 480 - 720 seconds - metric: Jittered Attempt 5 value: 960 - 1,440 seconds - metric: Jittered Attempt 6 value: 1,920 - 2,880 seconds credits_used: 3 credits_remaining: null stripe_style_100_req_sec_across_3_workers_quota_backoff_skipped: summary: >- Stripe-style 100 req/sec across 3 workers (quota/backoff skipped) value: tool: rate-limit-calc tool_version: 1.0.1 outputs: rateOutput: - metric: Input value: 100 requests per second - metric: Requests Per Second (RPS) value: '100' - metric: Requests Per Minute value: 6,000 - metric: Requests Per Hour value: 360,000 - metric: Requests Per Day value: 8,640,000 - metric: Min Delay Between Requests value: 10 ms - metric: Recommended Delay (10% buffer) value: 11 ms workerOutput: - metric: Workers value: '3' - metric: Per-Worker Rate Limit value: 33.33 RPS - metric: Per-Worker Delay value: 30 ms - metric: Total Throughput Per Second value: '100' - metric: Total Throughput Per Minute value: 6,000 - metric: Total Throughput Per Hour value: 360,000 - metric: Worker 1 Start Offset value: +0 ms - metric: Worker 2 Start Offset value: +3.33 ms - metric: Worker 3 Start Offset value: +6.67 ms quotaOutput: - metric: Status value: Enter a daily limit above to see the quota plan backoffOutput: - metric: Status value: >- Enter retry-after, request count, and time window to see backoff calculations credits_used: 3 credits_remaining: null 429_backoff_only_250_requests_in_60s_retry_after_30s_rate_quota_skipped: summary: >- 429 backoff only: 250 requests in 60s, Retry-After 30s (rate/quota skipped) value: tool: rate-limit-calc tool_version: 1.0.1 outputs: rateOutput: - metric: Status value: Enter a rate limit above to see calculations workerOutput: - metric: Status value: Enter a rate limit above to see calculations quotaOutput: - metric: Status value: Enter a daily limit above to see the quota plan backoffOutput: - metric: Scenario value: Got 429 after 250 requests in 60s - metric: Actual Rate You Were Sending value: 4.17 req/sec - metric: Estimated Rate Limit value: ~125 req / 30s - metric: Recommended New Delay value: 360 ms - metric: Backoff Attempt 1 value: 30 seconds - metric: Backoff Attempt 2 value: 60 seconds - metric: Backoff Attempt 3 value: 120 seconds - metric: Backoff Attempt 4 value: 240 seconds - metric: Backoff Attempt 5 value: 480 seconds - metric: Backoff Attempt 6 value: 960 seconds - metric: Backoff Attempt 7 value: 1,920 seconds - metric: Jittered Attempt 1 value: 30 - 45 seconds - metric: Jittered Attempt 2 value: 60 - 90 seconds - metric: Jittered Attempt 3 value: 120 - 180 seconds - metric: Jittered Attempt 4 value: 240 - 360 seconds - metric: Jittered Attempt 5 value: 480 - 720 seconds - metric: Jittered Attempt 6 value: 960 - 1,440 seconds - metric: Jittered Attempt 7 value: 1,920 - 2,880 seconds credits_used: 3 credits_remaining: null schema: type: object required: - tool - tool_version - outputs - credits_used - credits_remaining properties: outputs: type: object properties: rateOutput: type: array description: Core Rate Calculations items: type: object properties: metric: type: string description: Metric value: type: string description: Value x-iotools-columns: - metric - value workerOutput: type: array description: Multi-Worker Throughput items: type: object properties: metric: type: string description: Metric value: type: string description: Value x-iotools-columns: - metric - value quotaOutput: type: array description: Daily Quota Plan items: type: object properties: metric: type: string description: Metric value: type: string description: Value x-iotools-columns: - metric - value backoffOutput: type: array description: Retry-After / Backoff Schedule items: type: object properties: metric: type: string description: Metric value: type: string description: Value x-iotools-columns: - metric - value tool: type: string description: The tool's slug, echoing the {slug} in the request path. tool_version: type: string description: Output-contract version for this tool. credits_used: type: integer description: >- Credits this call consumed, after any settlement refund. 0 when metering is disabled. credits_remaining: type: - integer - 'null' description: >- Credits left in the current monthly allowance, or null when metering is disabled. request_id: type: string description: Correlation id, also sent as x-request-id. '400': $ref: '#/components/responses/ValidationError' '401': $ref: '#/components/responses/Unauthorized' '402': $ref: '#/components/responses/InsufficientCredits' '403': $ref: '#/components/responses/ToolNotAllowed' '404': $ref: '#/components/responses/ToolNotFound' '413': $ref: '#/components/responses/PayloadTooLarge' '429': $ref: '#/components/responses/RateLimited' '500': $ref: '#/components/responses/ToolFailed' '503': $ref: '#/components/responses/ToolDisabled' security: - bearerAuth: [] components: responses: ValidationError: description: Invalid request. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/validation_error title: type: string description: Short human-readable summary of the failure. examples: - Invalid request status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - validation_error detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. fields: type: - object - string additionalProperties: type: string description: >- What failed: a map of field name → message. Absent when the body itself is malformed; a single string when the failure isn't tied to one field. example: type: https://iotools.cloud/docs/errors/validation_error title: Invalid request status: 400 code: validation_error detail: One or more inputs are invalid — see `fields`. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 fields: inputString: Required Unauthorized: description: Missing or invalid API key. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/invalid_api_key title: type: string description: Short human-readable summary of the failure. examples: - Invalid API key status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - invalid_api_key detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. example: type: https://iotools.cloud/docs/errors/invalid_api_key title: Invalid API key status: 401 code: invalid_api_key detail: 'Provide ''Authorization: Bearer ''.' request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 InsufficientCredits: description: Monthly credit allowance exhausted. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/insufficient_credits title: type: string description: Short human-readable summary of the failure. examples: - Insufficient credits status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - insufficient_credits detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. credits_used: type: integer description: Always 0 — a refused call charges nothing. credits_remaining: type: integer description: Credits left in the allowance — fewer than this call costs. example: type: https://iotools.cloud/docs/errors/insufficient_credits title: Insufficient credits status: 402 code: insufficient_credits detail: This call costs 1 credit and 0 remain in this month's allowance. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 credits_used: 0 credits_remaining: 0 ToolNotAllowed: description: Tool exists but has no API surface. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/tool_not_allowed title: type: string description: Short human-readable summary of the failure. examples: - Tool not available over the API status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - tool_not_allowed detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. example: type: https://iotools.cloud/docs/errors/tool_not_allowed title: Tool not available over the API status: 403 code: tool_not_allowed detail: >- "Background Remover" is available on iotools.cloud but has no API endpoint. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 ToolNotFound: description: No such tool. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/tool_not_found title: type: string description: Short human-readable summary of the failure. examples: - Tool not found status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - tool_not_found detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. example: type: https://iotools.cloud/docs/errors/tool_not_found title: Tool not found status: 404 code: tool_not_found detail: No tool with that slug. See GET /v1/tools/list. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 PayloadTooLarge: description: Body too large. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/payload_too_large title: type: string description: Short human-readable summary of the failure. examples: - Payload too large status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - payload_too_large detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. example: type: https://iotools.cloud/docs/errors/payload_too_large title: Payload too large status: 413 code: payload_too_large detail: Request body exceeds this tool's size limit. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 RateLimited: description: Per-minute rate limit exceeded. headers: Retry-After: description: Seconds to wait before retrying (RFC 9110 delta-seconds). schema: type: integer content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/rate_limited title: type: string description: Short human-readable summary of the failure. examples: - Rate limit exceeded status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - rate_limited detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. retry_after: type: integer description: >- Seconds until the window resets — the same value as the `Retry-After` header. example: type: https://iotools.cloud/docs/errors/rate_limited title: Rate limit exceeded status: 429 code: rate_limited detail: Too many requests. Retry in 30s. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 retry_after: 30 ToolFailed: description: Tool failed to run. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/processing_error - https://iotools.cloud/docs/errors/internal_error title: type: string description: Short human-readable summary of the failure. examples: - Tool failed to run - Internal error status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - processing_error - internal_error detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. credits_used: type: integer description: >- Always 0 on `processing_error` — a failed run is refunded, floor included. credits_remaining: type: integer description: >- Credits left after the refund. Absent when metering is disabled. example: type: https://iotools.cloud/docs/errors/processing_error title: Tool failed to run status: 500 code: processing_error detail: The tool failed to run. Please try again. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 credits_used: 0 ToolDisabled: description: Tool temporarily disabled. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/tool_disabled - https://iotools.cloud/docs/errors/api_unconfigured title: type: string description: Short human-readable summary of the failure. examples: - Tool temporarily disabled - API not configured status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - tool_disabled - api_unconfigured detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. example: type: https://iotools.cloud/docs/errors/tool_disabled title: Tool temporarily disabled status: 503 code: tool_disabled detail: This tool is temporarily unavailable. Try again shortly. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: iot_live_… ````