Proposed design · not live
Developer Free — planned
A future managed API could include 100,000 managed request units per UTC calendar month for USD 0, with no card required. The managed API is not live and no signup is available.
Developer Free — planned
100,000 units/month. No payment method. Small commercial and non-commercial integrations permitted, subject to permission and licensing. Best-effort/community support only; no SLA.
Hard stop with 429 at the allowance until the next UTC month. No automatic overage charge, paid conversion, or surprise bill.
Growth — planned
A future base subscription, included calls, and transparent metered overage. Prices, included volume, and rates are not published/TBD. Any charge requires explicit opt-in; free users never auto-convert.
Enterprise — planned
Potential custom volume, SLA/support, procurement, and security options. Exact price is not published.
Current crisis information stays free
The existing site, static API v1, feeds, widget, and data remain free, keyless, and unmetered. They will not be degraded or paywalled. Use the current integration guide or open the static API manifest.
What one proposed unit means
One unit is an authenticated, authorized managed-artifact GET or HEAD attempt, including 200/304 responses and attempts rejected only by the monthly allowance. Health, exact OPTIONS, authentication failures, forbidden requests, unknown or query-bearing routes, and all free static surfaces use zero units. Short-term rate limiting is separate.
Privacy boundary
A future monthly counter may retain only account-level aggregate technical units for a UTC month. It must not retain URLs, queries, raw paths, country/category/hotline/crisis intent, user behavior, IP/referrer, contact data, authorization or raw keys, or distress analytics.
Read the versioned synthetic contract →One ordered, replay-safe planning boundary
The static model has one transition-producing operation. It takes only the exact authoritative store-read generation, UTC month, and usage state, a trusted instant, and the request classification. In-month metered attempts derive one full-state transition; the first metered attempt in a later month atomically changes month and records unit 1. Allowance-rejected attempts advance generation while preserving the 100,000 cap. Zero-unit classes never transition, including at rollover. A future store must full-state-CAS the derived expected state to its exact derived next state, rejecting stale, concurrent, or replayed transitions. The model accepts no caller-selected next state. This is a design contract only; no counter store, CAS helper, billing system, or managed API is deployed.