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: API Blueprint
providerId: api-blueprint
created: '2026-05-04'
modified: '2026-09-02'
generated: '2026-09-02'
method: probed
source: >-
  Live unauthenticated calls to https://api.apiblueprint.org on 2026-09-02
  (GET /, POST /parser, POST /validate, POST /transform, OPTIONS on each), plus
  a documentation search across apiblueprint.org, /developers.html and the
  provider's own API Blueprint contract in apib/.
limit_count: 0
note: >-
  NO RATE LIMITS ARE PUBLISHED, AND NONE WERE OBSERVED. The provider's contract
  documents no quota, no throttle and no 429. Every response captured during
  this pass carried the same small header set — Date, Content-Type,
  Content-Length, Connection and three Access-Control-Allow-* headers — and no
  rate-limit header of any family. Repeated calls in quick succession all
  returned 200. This is an honest zero: an absence of published limits, not a
  guarantee of unlimited capacity. An agent has no runtime signal to back off
  on, and no documented ceiling to design against.


  SUPERSEDES A SCAFFOLD. Until this pass this file described free /
  professional / enterprise tiers at 10, 100 and 1,000 requests per minute with
  X-RateLimit-* headers. None of that was ever published by API Blueprint; it
  came from the 2026-05-04 bulk sweep. It has been removed.
headers_observed: []
headers_documented: []
retry_after: false
status_on_exhaustion: null
limits: []
policies: []
observed_responses:
  - request: 'GET https://api.apiblueprint.org/'
    status: 200
    rate_limit_headers: []
  - request: 'POST https://api.apiblueprint.org/parser (text/vnd.apiblueprint)'
    status: 200
    rate_limit_headers: []
  - request: 'POST https://api.apiblueprint.org/transform (application/json)'
    status: 200
    rate_limit_headers: []
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com