generated: '2026-08-26'
method: probed
source: >-
  https://api.samaya.ai/v1/openapi.json, live response headers from https://api.samaya.ai/ and
  https://mcp.samaya.ai/mcp
limit_count: 0
limits: []
note: >-
  Samaya documents no rate limits. The published OpenAPI declares no 429 response on any of its six
  operations, there is no docs site or developer portal to state limits in prose, and no
  rate-limit response header was observed on any live request. An agent integrating this API has no
  runtime backpressure signal to read and no documented number to plan against.
response_headers:
  documented: []
  observed: []
  observed_note: >-
    Live responses from api.samaya.ai and mcp.samaya.ai carry only Cloudflare (cf-ray,
    cf-cache-status) and Envoy (x-envoy-upstream-service-time) headers. No X-RateLimit-*,
    RateLimit-*, or Retry-After header was present on any probe.
status_on_exhaustion: unknown
status_note: >-
  Not declared in the contract and not observed. Both hosts front on Cloudflare, so an edge-level
  429 or 403 is plausible, but nothing was measured and nothing is asserted.
evidence:
- url: https://api.samaya.ai/v1/openapi.json
  status: 200
  finding: no 429 response declared on any operation
- url: https://api.samaya.ai/
  status: 302
  finding: no rate-limit headers in response
- url: https://mcp.samaya.ai/mcp
  status: 401
  finding: no rate-limit headers in response