Long-term API availability
≥99.9%Customer API commitment.Live operational evidence
Observed systems are operational
Current health plus bounded, reproducible evidence for API reliability, service latency, and Search data freshness.
Checked · machine-readable JSON
Service commitments
Reliability you can plan around
These customer-facing objectives are distinct from the bounded live evidence reported below.
Standard read response time
P99 < 2sSuccessful Basic Reads measured service-side. Enriched Reads and Workflow APIs are outside this latency commitment.Monitor timeliness
P99 < 15sFrom an eligible source-event timestamp to the first delivery attempt.Public web
operationalThis page was rendered successfully by the public web application.
- Current check
- HTTP response served
Customer API
operationalA live health check plus the last 24 hours of eligible customer calls.
- Live health round trip
- 176 ms
- Successful responses
- 100.00%
- Observed sample
- 142
- Service latency
- p50 1216 ms · p95 1742 ms
Search data sample
live sampleThe fixed no-signup Search Demo is executed against current public data.
- Newest returned post
- 52m old
- Post timestamp
- Aug 7, 2026, 11:29:19 PM UTC
- Reproduce it
- Run the JSON Demo
Account monitors
no recent sampleDelivery outcomes from the latest seven UTC dates, when a customer delivery sample exists.
- Successful deliveries
- 0
- Failed deliveries
- 0
- Last sampled success
- No recent sample
Methodology
What these numbers do—and do not—prove
- Commitments. Customer-facing service objectives are separate from the bounded live evidence below. API availability and Basic Reads latency were validated from owner-reviewed production analysis. Monitor timeliness was validated in owner-reviewed offline testing and is measured from an eligible source-event timestamp to the first delivery attempt.
- API reliability. Rolling 24-hour completed 2xx and 5xx customer-call sample. Intentional validation, authentication, billing, and rate-limit outcomes plus owner and shared-Demo traffic are excluded.
- Latency. p50 and p95 are service-side latency for successful calls in the same 24-hour sample. The live probe is a web-to-API health round trip and is not an end-user SLA.
- Data freshness. Newest created_at timestamp returned by the fixed public Search Demo query. It proves that sample, not completeness or a platform-wide freshness guarantee.
- Monitors. Successful and failed deliveries aggregated over the latest seven UTC dates. No recent sample is reported explicitly instead of inferring delivery latency.