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: Microsoft Clarity
providerId: microsoft-clarity
created: '2026-05-04'
modified: '2026-08-13'
generated: '2026-08-13'
method: searched
source: https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-data-export-api
docs:
  - https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-data-export-api
  - https://learn.microsoft.com/en-us/clarity/third-party-integrations/clarity-mcp-server
tags:
  - Analytics
  - Web Analytics
  - Rate Limiting
  - Quotas
description: >-
  Published limits for the Microsoft Clarity Data Export API. Clarity documents
  a single, unusually small quota — 10 requests per project per day — under
  "Limitations and usage quotas", together with a hard 1,000-row unpaginated
  response cap and a 1-3 day lookback window. There are no per-minute or
  per-second limits, no burst allowance and no tiering: Clarity has one free
  plan for everyone (see plans/microsoft-clarity-plans-pricing.yml).
limit_count: 4
supersedes_note: >-
  Replaces a 2026-05-04 bulk-sweep scaffold that invented per-minute and
  per-month quotas across free/professional/enterprise tiers and asserted
  X-RateLimit-* response headers. None of that is published by Clarity. Method
  upgraded generated -> searched.
headers:
  documented: false
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
  note: >-
    Clarity documents NO rate-limit response headers. An agent cannot read
    remaining quota from a response; the only runtime signal is the 429 on
    exhaustion. This is the practical gap on this API: with a 10/day budget and
    no counter header, a client must track its own consumption.
responseCodes:
  throttled: 429
  quotaExceeded: 429
  quotaExceededResponse: TooManyRequests
  quotaExceededMessage: Exceeded daily limit
limits:
  - name: Data Export API daily request quota
    scope: project
    metric: requests
    limit: 10
    window: day
    burst: null
    applies:
      - Microsoft Clarity DataExport API
    operations:
      - getProjectLiveInsights
    statusOnExhaustion: 429
    quote: Maximum of 10 API requests are allowed per project per day.
    source: https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-data-export-api
  - name: Response row cap
    scope: request
    metric: rows
    limit: 1000
    window: request
    pagination: false
    applies:
      - Microsoft Clarity DataExport API
    quote: The response is limited to 1,000 rows and can't be paginated.
    source: https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-data-export-api
  - name: Lookback window
    scope: request
    metric: days
    limit: 3
    window: request
    applies:
      - Microsoft Clarity DataExport API
    quote: Data retrieval is confined to the previous 1 to 3 days.
    source: https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-data-export-api
  - name: Dimensions per request
    scope: request
    metric: dimensions
    limit: 3
    window: request
    applies:
      - Microsoft Clarity DataExport API
    quote: Maximum of three dimensions can be passed in a single request.
    source: https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-data-export-api
policies:
  - name: Client-side budgeting
    description: >-
      Clarity's published best practice is to "Anticipate and manage rate limit
      errors." With no quota headers and a 10/day ceiling, clients must budget
      and cache locally rather than react to a header.
    source: https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-data-export-api
  - name: MCP server shares the same budget
    description: >-
      The first-party MCP server calls the Data Export API, so every MCP tool
      invocation consumes from the same 10-requests-per-project-per-day quota.
      Microsoft Learn restates the limit on the MCP page.
    source: https://learn.microsoft.com/en-us/clarity/third-party-integrations/clarity-mcp-server
  - name: Announced increase
    description: >-
      Microsoft lists "Increased API limits: Expansion of daily request limits
      for the Clarity data export API" as a planned enhancement on the MCP
      server page. No date or new number is published.
    source: https://learn.microsoft.com/en-us/clarity/third-party-integrations/clarity-mcp-server
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com