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: Adaptive Shield
providerId: adaptive-shield
created: '2026-05-04'
modified: '2026-08-30'
generated: '2026-08-30'
method: searched
source: >-
  Integrator documentation for the Adaptive Shield API v1 (Brinqa, Axonius, Blink, Torq, Tines) and
  live probes of api.adaptive-shield.com. Adaptive Shield's own API reference is offline.
description: >-
  Adaptive Shield publishes no rate limits for its REST API. This file records that absence,
  replacing a scaffold written by the 2026-05-04 bulk sweep that invented per-tier limits, burst
  ceilings and a header set the provider never documented.
limit_count: 0
limits: []
headers: {}
responseCodes: {}
findings:
  - finding: No published rate limit, quota or throttling policy.
    detail: >-
      Every surviving description of the API — the Brinqa, Axonius, Blink, Torq and Tines connector
      docs, all of which quote the original reference — covers HTTPS-only transport, JSON responses,
      API-key auth and endpoint shapes, and none of them mentions a limit, a window, a burst
      allowance or a 429.
    source: https://docs.brinqa.com/docs/connectors/adaptive-shield/
    status: 200
  - finding: Response headers cannot be observed.
    detail: >-
      api.adaptive-shield.com and eu.api.adaptive-shield.com return an identical 134-byte 403 to
      every unauthenticated request including the root, emitting no RateLimit-*, X-RateLimit-* or
      Retry-After header. No runtime rate-limit signal can be confirmed without a tenant key.
    source: https://api.adaptive-shield.com/
    status: 403
  - finding: The reference that would have carried limits is decommissioned.
    detail: >-
      The API Reference article on adaptive-shield.zendesk.com sits behind a Cloudflare interstitial
      and the help centre itself is closed — its root redirects to zendesk.com/help-center-closed/
      and its Help Center API returns 404.
    source: https://adaptive-shield.zendesk.com/hc/en-us/articles/20587718569757-API-Reference
    status: 403
note: >-
  limit_count 0 means checked and nothing published, not unchecked. The previous version of this
  file asserted 10/100/1000 requests-per-minute tiers and a full X-RateLimit-* header set that no
  Adaptive Shield document has ever contained.
maintainers:
  - FN: Kin Lane
    X-twitter: apievangelist
    email: info@apievangelist.com