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: Ready Player Me
providerId: ready-player-me
created: '2026-05-25'
modified: '2026-05-25'
reconciled: false
generated: '2026-08-26'
method: derived
limit_count: 0
headers: []
status_on_exhaustion: unknown
note: >-
  method set 2026-08-26. Ready Player Me published NO numeric rate limits, and none can now be
  found or observed: docs.readyplayer.me and api.readyplayer.me were removed from DNS after the
  2026-01-31 platform shutdown (curl exit 6 on 2026-08-26). limit_count is an honest 0 — the
  policies below name throttled surfaces and scopes, not published numbers, and none of the three
  OpenAPI definitions declares a 429 response or any X-RateLimit-*/RateLimit-*/Retry-After header.
  An agent had no runtime rate-limit signal from this API. See lifecycle/ready-player-me-lifecycle.yml.
status: retired
tags:
  - Avatars
  - Rate Limits
description: Ready Player Me does not publish a globally-fixed rate-limit table. Limits are applied per
  application (X-APP-ID), per endpoint family, and per asset/avatar render to protect the shared rendering
  fleet. The values below capture observed and documented patterns for the Avatars and Assets surfaces.
sources:
  - https://docs.readyplayer.me/
policies:
  - id: ready-player-me-avatar-render
    name: Avatar Render
    appliesTo:
      - /v1/avatars/{avatarId}.glb
      - /v1/avatars/{avatarId}.png
      - /v2/avatars/{avatarId}.glb
    scope: application
    limits:
      - type: concurrency
        description: Concurrent render requests per application are throttled by the rendering fleet to
          protect shared infrastructure. Use precompile and CDN-cacheable URLs to avoid burst storms.
        metric: concurrent-requests
        unit: requests
        observed: true
  - id: ready-player-me-asset-listing
    name: Asset Listing
    appliesTo:
      - /v1/assets
      - /v1/phoenix-assets
    scope: application
    limits:
      - type: request-rate
        description: Asset listing endpoints accept paginated reads. Heavy listing should be cached by the
          integrator; sustained high-rate listing across all pages can be throttled.
        metric: requests
        unit: requests
        observed: true
  - id: ready-player-me-avatar-mutation
    name: Avatar Mutation
    appliesTo:
      - POST /v2/avatars
      - PATCH /v2/avatars/{avatarId}
      - PUT /v2/avatars/{avatarId}
      - DELETE /v2/avatars/{avatarId}
    scope: user
    limits:
      - type: request-rate
        description: Avatar mutation is bound to interactive user flows; sustained scripted writes can
          trigger anti-abuse throttling.
        metric: requests
        unit: requests
        observed: true