generated: '2026-09-06'
method: probed
source: >-
  live unauthenticated calls to https://api.asyncapi.com/v1 on 2026-09-06, plus a
  search of https://www.asyncapi.com/docs and the asyncapi/server-api README
provider: AsyncAPI
providerId: asyncapi
note: >-
  REPLACES a 2026-05-04 scaffold that asserted free/professional/enterprise tiers
  with invented per-minute and per-month numbers. AsyncAPI publishes no rate
  limits at all. Two live unauthenticated calls (GET /v1/help, POST /v1/validate)
  both returned 200 and carried NO RateLimit-*, X-RateLimit-* or Retry-After
  header — the full response header set was security headers, etag, cache-control
  and Cloudflare/DigitalOcean routing headers. An honest zero is the finding: an
  agent gets no runtime budget signal from this API and must treat throttling as
  unannounced.
limit_count: 0
limits: []
headers:
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
observed_headers:
  - strict-transport-security
  - content-security-policy
  - etag
  - cache-control
  - x-content-type-options
  - cf-ray
responseCodes:
  throttled: null
  documented: false
evidence:
  - request: GET https://api.asyncapi.com/v1/help
    http_status: 200
    rate_limit_headers_present: false
    observed: '2026-09-06'
  - request: POST https://api.asyncapi.com/v1/validate
    http_status: 200
    rate_limit_headers_present: false
    observed: '2026-09-06'
  - url: https://www.asyncapi.com/docs
    finding: no rate-limit or quota documentation for the hosted Server API
    checked: '2026-09-06'
upstream_protection:
  note: >-
    The service sits behind Cloudflare (server: cloudflare, cf-ray present), so
    edge-level abuse protection almost certainly exists. It is not a published
    contract and produced no headers on normal traffic, so it is recorded here
    as context rather than as a limit.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com