Medable Rate Limits
Medable does not publish a conventional per-key/per-second HTTP rate limit for the Cortex API, and returns no RateLimit-*/X-RateLimit-* response headers. What it DOES publish is a set of hard platform quotas: per-execution limits on server-side Cortex scripts (jobs, routes, triggers), a daily job-run cap, a request size ceiling, and a documented throttling fault family that surfaces as HTTP 429. Throttling is also applied by org Policy (cortex.throttled.policy). Limits below are the published DEFAULTS; the docs describe them as defaults that a multi-tenant environment enforces so runaway scripts cannot monopolize shared resources.
Medable Rate Limits is the machine-readable rate-limit profile for Medable on the APIs.io network, in the API Commons Rate Limits shape.
It captures 12 rate-limit definitions.
Limit state is signalled in the rate_limit_headers, retry_after, and notes response headers.
Tagged areas include Company, Human Health, Clinical Trials, Life Sciences, and eCOA.
rate_limit_headersretry_afternotes
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.