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: Clerk.io
providerId: clerk-io
generated: '2026-08-13'
method: searched
source: >-
  https://docs.clerk.io/llms.txt (full docs index), https://docs.clerk.io/docs/api,
  https://www.clerk.io/pricing, live response-header observation on https://api.clerk.io/v2
created: '2026-05-04'
modified: '2026-08-13'
tags:
  - AI
  - Commerce
  - E-Commerce
  - Personalization
  - Recommendations
  - Search
  - Rate Limiting
description: >-
  Clerk.io publishes NO rate limits. This file REPLACES a fabricated scaffold written by the 2026-05-04
  bulk sweep that asserted 10/100/1000 requests-per-minute tiers, monthly quotas and a full
  X-RateLimit-* header set - none of which Clerk.io publishes or returns. An honest zero is the finding.
limit_count: 0
limits: []
headers: {}
responseCodes: {}
findings:
  documentation:
    searched: true
    result: >-
      Clerk.io's complete documentation index (https://docs.clerk.io/llms.txt, 47 reference pages and 27
      guides) contains no page on rate limits, throttling, quotas or backoff, and the word does not
      appear in the index. The Basics page describes only version, endpoint and arguments.
  openapi:
    searched: true
    result: >-
      The provider-published OpenAPI declares only 200 and 400 responses across all 101 operations. No
      429 response is declared on any operation.
  live_headers:
    probed: true
    url: https://api.clerk.io/v2/recommendations/popular
    http_status: 401
    result: >-
      The response carries no RateLimit-*, X-RateLimit-*, or Retry-After header. Observed 2026-08-13.
      Only date, content-type and content-length were returned.
  pricing:
    searched: true
    result: >-
      https://www.clerk.io/pricing meters usage in searches, recommendations, conversations, opened
      emails and active subscribers per month, but attaches no request-rate ceiling to any band and
      publishes no throttling behaviour on band exhaustion.
implication: >-
  An agent integrating Clerk.io has no runtime signal for how close it is to any ceiling and no documented
  status code or header to react to. Backoff must be inferred from generic 5xx behaviour. This is a real
  gap to raise with the provider, not a data-collection failure.
maintainers:
  - FN: Kin Lane
    email: kinlane@gmail.com