Freeplay · Rate Limits

Freeplay Rate Limits

Freeplay's HTTP API is authenticated per-account with a Bearer API key and scoped to projects. Freeplay does not publish specific numeric rate-limit values (RPM/TPM/quotas) in its public API reference; limits are governed by account plan and deployment. Clients should expect standard HTTP 429 throttling and apply backoff. Specific limits are not reconciled here.

Freeplay Rate Limits is the machine-readable rate-limit profile for Freeplay on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests and completions.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI, LLM, Evaluation, Observability, and Prompt Management.

3 Limits Throttle: 429
AILLMEvaluationObservabilityPrompt ManagementRate LimitingQuotasThrottling

Limits

Requests Per Minute (RPM) account
requests
see provider documentation
Not publicly published; governed by plan and instance.
Recording / Ingestion Volume account
completions
see provider documentation
Completion/session/trace recording volume may be plan-bounded.
Search & Bulk Operations account
requests
see provider documentation
API-only search and bulk endpoints may carry separate limits.

Policies

Tiered Limits
Limits scale with plan (Free/Starter, Growth, Enterprise) and deployment (cloud vs. self-hosted).
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429 responses.

Sources