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: Ballerina
providerId: ballerina
generated: '2026-09-04'
created: '2026-05-04'
modified: '2026-09-04'
method: probed
source: live responses from https://api.central.ballerina.io, observed 2026-09-04
description: >-
  Ballerina publishes no rate limits for the Ballerina Central API, and the API returns no
  rate-limit headers. Both halves were checked: the docs carry no limits page, and the response
  headers on live 200 and 4xx responses carry no X-RateLimit-*, RateLimit-* or Retry-After
  field. This file previously carried a scaffold asserting a 10 req/min free tier and a full set
  of X-RateLimit-* headers; none of that was published by Ballerina and it has been removed.
limit_count: 0
limits: []
headers:
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
responseCodes:
  throttled: null
  note: No 429 was observed; no throttling behaviour is documented.
observed_response_headers:
  - date
  - content-type
  - content-length
  - set-cookie
  - x-envoy-upstream-service-time
  - strict-transport-security
  - x-azure-ref
  - x-cache
evidence:
  - url: https://api.central.ballerina.io/2.0/registry/packages?q=http&limit=1
    status: 200
    note: Full response headers captured; no rate-limit family present.
  - url: https://api.central.ballerina.io/2.0/registry/organizations/ballerina
    status: 404
    note: Error response headers likewise carry no rate-limit or Retry-After field.
notes:
  - >-
    An unmetered public API with no published limits is not the same as an API with no limits.
    WSO2's own MCP client requests limit=1000 pages, which suggests generous ceilings, but a
    consumer has no signal to back off on and no documented contract to rely on.