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: Better Stack
providerId: betterstack
generated: '2026-09-04'
method: searched
source: >-
  https://betterstack.com/docs/uptime/api,
  https://betterstack.com/docs/uptime/api/getting-started-with-uptime-api/,
  https://betterstack.com/docs/logs/api/getting-started/,
  https://betterstack.com/docs/errors/api/, https://betterstack.com/pricing, plus live
  unauthenticated probes of uptime.betterstack.com/api/v2,
  telemetry.betterstack.com/api/v1 and errors.betterstack.com/api/v1 on 2026-09-04.
created: '2026-05-04'
modified: '2026-09-04'
supersedes: >-
  The 2026-05-04 bulk-sweep scaffold, which asserted a 10-requests-per-minute free tier and a
  full set of X-RateLimit-* / RateLimit-Policy response headers. None of that was published by
  Better Stack and none of it appeared on the wire. It is removed rather than corrected: an
  invented limit is worse than a recorded absence, because a client will pace itself to it.
tags:
  - Observability
  - Uptime Monitoring
  - Rate Limiting
  - Quotas
  - Throttling
description: >-
  Better Stack publishes no API rate limits. This artifact records that absence with the
  evidence for it, rather than asserting numbers.
limit_count: 0
documented: false
headers:
  observed: []
  note: >-
    No RateLimit-Limit / RateLimit-Remaining / RateLimit-Reset (RFC 9331 draft), no
    X-RateLimit-* variant, and no Retry-After header appeared on any response from
    uptime.betterstack.com, telemetry.betterstack.com or errors.betterstack.com. An agent has
    no runtime signal to pace against — it cannot discover its budget, cannot tell how much is
    left, and will only learn a limit exists by tripping it.
responseCodes:
  throttled: unknown
  note: The status code returned on exhaustion is not documented and was not induced — this
    pipeline does not deliberately trip a production limit.
limits: []
quotas:
  api_requests_metered: false
  note: >-
    Better Stack's pricing meters product usage (monitors, heartbeats, telemetry GB,
    exceptions, session replays, transaction-check minutes, AI SRE tokens) and does not meter
    API calls at all. There is no request quota attached to any plan. See
    plans/betterstack-plans-pricing.yml.
evidence:
  - url: https://betterstack.com/docs/uptime/api
    status: 200
    finding: No rate-limit section; the API reference navigation lists Getting an API token,
      Pagination, Monitors, Heartbeats, On-call & incidents, Status pages, Metadata,
      Integrations, Team members, Organization roles, Usage and Reporting — no rate limits.
  - url: https://betterstack.com/docs/uptime/api/rate-limits/
    status: 404
  - url: https://uptime.betterstack.com/api/v2/monitors
    status: 401
    finding: Response carried no rate-limit header of any kind.
  - url: https://telemetry.betterstack.com/api/v1/sources
    status: 401
    finding: Response carried no rate-limit header of any kind.
  - url: https://errors.betterstack.com/api/v1/applications
    status: 401
    finding: Response carried no rate-limit header of any kind.