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: Akita Software
providerId: akita-software
created: '2026-05-04'
generated: '2026-08-30'
modified: '2026-08-30'
method: searched
source: >-
  https://learning.postman.com/docs/insights/overview/ (read 2026-08-30);
  rest/base_client.go in https://github.com/postmanlabs/postman-insights-agent;
  https://docs.akita.software/ (DNS NXDOMAIN — domain expired);
  https://www.akitasoftware.com/ (HTTP 403, Cloudflare block)
limit_count: 0
tags:
  - Acquired
  - API Discovery
  - API Mapping
  - API Observability
  - Traffic Analysis
  - Rate Limiting
description: >-
  No rate limits are published for the Akita API or for the Postman
  observability API that succeeded it. limit_count is an honest ZERO. Two
  independent checks agree: the Postman Insights documentation states no limits,
  and the first-party open-source agent's REST client implements no rate-limit
  header parsing, no 429 handling and no Retry-After backoff — a client that
  ignores the runtime signal is strong evidence the API does not send one.
headers: {}
response_codes: {}
limits: []
policies: []
observed:
  rate_limit_headers_handled_by_client: false
  status_429_handled_by_client: false
  retry_after_handled_by_client: false
  source: rest/base_client.go, rest/errors.go
  note: >-
    The only 4xx conditions the client recognises are two 403 entitlement/TTL
    errors (see errors/akita-software-problem-types.yml). Neither is a
    throttling signal.
history:
  - date: '2026-08-30'
    change: >-
      REPLACED a fabricated scaffold. The previous version of this file declared
      X-RateLimit-* / RateLimit-Policy headers and free/professional/enterprise
      limits of 10/100/1000 requests per minute with 1,000 and 100,000 monthly
      quotas. Akita never published any of it; the values were bulk-sweep
      defaults written 2026-05-04. Advertising response headers an API does not
      send is worse than recording nothing, so they have been removed.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com