generated: '2026-08-26'
method: probed
source: 'live response headers from https://api.poshdevelopment.com/api/v1, 2026-08-26'
limit_count: 0
limits: []
response_headers: []
exhaustion_status: null
retry_after: false
note: >-
  No rate limits are published and none were observable. The response headers returned by
  api.poshdevelopment.com on an unauthenticated request are: x-powered-by, content-type,
  content-length, etag, date, posh-correlation, via, alt-svc — no X-RateLimit-*, no RateLimit-*
  (RFC 9331 draft), no Retry-After. Posh publishes no API documentation, so there is no documented
  limit to record either. Recorded as an honest zero. The gateway is fronted by Google Cloud Load
  Balancing (via: 1.1 google), which commonly enforces limits without emitting client-visible
  headers, so an absence of headers is not proof of an absence of limits — it is proof the runtime
  signal an agent needs is not there.
evidence:
  - url: https://api.poshdevelopment.com/api/v1
    status: 404
    note: headers inspected; no rate-limit headers present
  - url: https://api.poshdevelopment.com/api-docs
    status: 403
    note: 'RBAC: access denied — documented limits, if any, are behind this wall'