specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Recraft
providerId: recraft
created: '2026-05-08'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-08, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-08'
reconciled: partial
tags:
- AI
- Image Generation
- Design
- Vector
- Style
- Rate Limiting
- Quotas
- Throttling
description: >-
  Recraft API access requires a positive API Unit balance; throughput is gated primarily by
  available units rather than published HTTP RPS. Specific rate limits are not publicly
  listed; standard 429 backoff applies.
notes: API Unit balance is the primary gating mechanism; HTTP RPS limits are not public.
sources:
- https://www.recraft.ai/docs/api-reference/getting-started
- https://www.recraft.ai/docs/api-reference/pricing
responseCodes:
  throttled: 429
limits:
- name: API Unit Balance
  scope: account
  metric: api_units
  limit: prepaid
  notes: Account requires positive API Unit balance to call the API.
- name: HTTP Requests
  scope: account
  metric: requests
  limit: not publicly documented
policies:
- name: Backoff Strategy
  description: Clients should implement exponential backoff with jitter and honor any Retry-After header.
- name: Unit Top-Up
  description: Pre-purchase API Units in advance of high-volume jobs to avoid balance-based throttling.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com