name: Synup API rate limits
generated: '2026-08-13'
method: searched
source: https://developer.synup.com/
description: Synup publishes no rate limits for the v4 API. The developer portal, the getting-started
  guide, the MCP guides and all 210 published operations contain no request quota, no window, no burst
  allowance and no rate-limit response header. An anonymous live call returned no RateLimit-* or Retry-After
  header either.
url: https://developer.synup.com/
documented: false
limit_count: 0
limits: []
headers: []
exhaustion_status: null
evidence:
- url: https://api.synup.com/api/v4/locations
  http_status: 401
  probed: '2026-08-13'
  finding: Response carries no RateLimit-*, X-RateLimit-* or Retry-After header.
- url: https://developer.synup.com/llms.txt
  http_status: 200
  probed: '2026-08-13'
  finding: The 533-line documentation index contains no rate-limit or throttling page.
indirect_signals:
- signal: The first-party Node SDK synup-js documents "retries 429 + 5xx with backoff" (maxRetries default
    2), which confirms HTTP 429 is reachable even though no threshold is published.
  source: https://www.npmjs.com/package/synup-js
- signal: The MCP guide advises narrowing date ranges and location counts when requests time out, and
    the SDK default timeout is 240 seconds — long-running reads are expected.
  source: https://developer.synup.com/synup-mcp-putting-it-to-work-doc-2223537
notes:
- 'limit_count: 0 is a measured absence, not an unchecked field.'
- A prior version of this artifact asserted per-key, plan-tier-varying limits and a 429 response. None
  of that is published by Synup; the unsupported claims have been removed and replaced with what was actually
  probed.
- Agents integrating with Synup have no runtime rate-limit signal to obey — the only backpressure available
  is the HTTP status.