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: Chemius providerId: chemius created: '2026-05-04' # Provenance: the 2026-05-04 bulk sweep wrote a scaffold here that declared X-RateLimit-* headers, # a 429 throttle code and per-tier request quotas. NONE of that was ever published by Chemius; it # was invented default content (roadmap#35). Replaced on 2026-09-05 with the measured finding after # reading every public Chemius API page and the pricing comparison table. Method upgraded to # searched because the absence was established by reading the provider's own pages, not assumed. method: searched modified: '2026-09-05' verified: '2026-09-05' limit_count: 0 headers_published: false headers_note: >- Chemius publishes no rate-limit response headers, no throttle status code and no documented quota of any kind. The seven Chemius APIs are sold as flat monthly add-ons (EUR 100-300/month each) with no call allowance stated anywhere on the pricing page or on any of the per-API pages. An integrator cannot learn a budget before buying, and an agent gets no runtime signal. sources: - url: https://www.chemius.net/our-pricing/ status: 200 note: Full plan comparison table, including the seven-row "APIs" section. No request quota, no throttle policy. - url: https://www.chemius.net/api/ status: 200 note: API landing page. Describes what each API does; states no limits. - url: https://www.chemius.net/safety-data-sheet-api/ status: 200 - url: https://www.chemius.net/erp-api/ status: 200 - url: https://www.chemius.net/adr-api/ status: 200 gate: >- Every Chemius API page ends at "Book a call & ask for the API documentation", so any published rate limits would live in the reference handed over after a sales call. Nothing rate-limit related is reachable without that call. tags: - Rate Limiting - Chemicals - Compliance - Safety Data Sheets description: >- Measured record of Chemius rate limits: there are none published. Recorded as an honest zero rather than omitted, so the absence is countable and so the earlier scaffold values cannot be mistaken for provider-published limits. limits: []