generated: '2026-08-13'
method: searched
source: >-
  https://docs.customeros.ai (full docs corpus searched through the docs MCP filesystem),
  openapi/ (seven published specs), https://customeros.ai/pricing
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: CustomerOS
providerId: customeros
created: '2026-06-20'
modified: '2026-08-13'
reconciled: true
limit_count: 0
tags:
- CRM
- Revenue
- Go-To-Market
- Rate Limiting
- Quotas
- Throttling
description: >-
  CustomerOS publishes no API rate limits. This is a measured zero rather than an assumed one: the
  entire documentation corpus was grep-searched for "rate limit" through the provider's own docs MCP
  filesystem and the only hit is prose inside a marketing example on the Grain integration page. No
  operation in any of the seven published OpenAPI documents declares a 429 response, none declares a
  Retry-After or X-RateLimit header, and the pricing page attaches no call quota to either tier.
notes: >-
  What CustomerOS does publish are SENDING throttles inside the Flow API, and they must not be
  mistaken for API rate limits — they govern how fast the product sends email on the customer's
  behalf, not how fast a client may call the API. They are recorded separately below.
sources:
- https://docs.customeros.ai
- https://customeros.ai/pricing
- openapi/customeros-flow-api-openapi.yml
responseCodes:
  throttled: null
  note: No 429 is declared in any published spec.
headers:
  published: []
  note: >-
    No X-RateLimit-*, RateLimit-* or Retry-After header is documented or declared anywhere. An agent
    has no runtime signal to back off on; it can only infer from 5xx.
limits: []
product_sending_throttles:
  note: >-
    NOT API rate limits. Customer-configurable sending controls on a flow schedule.
  source: openapi/customeros-flow-api-openapi.yml
  fields:
  - {name: limits.emailsPerMailboxPerHour, type: integer, scope: mailbox, window: hour}
  - {name: limits.emailsPerMailboxPerDay, type: integer, scope: mailbox, window: day}
  - {name: rules.minutesDelayBetweenEmails, type: integer, scope: flow}
  - {name: dailySendLimit, type: integer, scope: sender, source: SenderCreate}
policies:
- name: Per-Request Access
  description: >-
    API endpoint groups are enabled per customer on request by the CustomerOS team, which functions
    as the de facto access control in place of a published quota.
- name: Backoff Strategy
  description: >-
    Client-side only. With no 429 and no Retry-After, clients should apply exponential backoff with
    jitter on 5xx and treat 4xx as terminal.
evidence:
- {method: 'MCP tools/call query_docs_filesystem — grep -ril "rate limit" /', result: '1 file: /integrations/meeting-transcripts/grain.mdx (marketing prose, not a limit)'}
- {method: spec scan, result: '0 of 55 operations declare a 429 response'}
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com