Monthly successful request availability for contracted paid API traffic, measured at the service edge.
Service objectives
Enterprise promises need measurement rules.
These are product design objectives. A signed order form defines the commitments, credits and exclusions that apply to a customer.Minimum notice target for a backwards-incompatible stable API change, except urgent security or legal requirements.
Target from a durable canonical correction or rights change to its appearance in the change feed.
Target from a durable event to the first delivery attempt for healthy subscriber endpoints.
Measurement
Clear boundaries. No vanity uptime.
Availability
Successful responses are measured against eligible authenticated requests. Customer errors, quota rejections and documented maintenance do not count as service failures.
Freshness
Delivery clocks begin only after an item, correction or rights update becomes durable in the canonical ledger. Editorial reporting time is not API latency.
Subscriber endpoints
Webhook objectives cover the first attempt. Retries caused by a buyer endpoint, invalid TLS or rate limiting are visible in delivery records but excluded from platform availability.
Contract controls
Service credits, priority response, data regions, retention, recovery objectives and support hours belong in the executed order form.
Operational transparency