An agent choosing between two APIs that do the same job has one obvious tie-breaker: which one promises to stay up. The service levels collection on apis.io holds 284 SLA4OAI documents, one per provider. Only 3 of them contain a promised uptime figure.
The collection is honest about why. apis.io is a discovery service and runs no monitors, so nothing in it is measured by us. Every figure is quoted from a provider’s own SLA page or status page, and every document says which.
What the 284 are made of
| Kind | Documents | What it holds |
|---|---|---|
| Synthetic base | 262 | generated from the provider’s plans and rate limits, because no service level was found; no uptime figure |
| Searched | 22 | figures quoted from pages listed in sources |
| …with a promised uptime | 3 | a guarantee from an SLA page |
| …with reported uptime | 19 | percentages read off a status page |
Each document records a coverage block that separates what was promised from what was reported, and whether each was checked, found or not found. In 258 documents, neither was checked. That is a recorded absence, and it is more useful than a guessed number.
The three promises
- SAP aims for 99.7% availability across its cloud services, unless a supplement says otherwise.
- Google Dialogflow commits to 99.9% or better.
- Doconda offers 99.5% monthly availability on its Enterprise plan, with credits if it is missed.
Doconda’s is the most usable of the three, because it names the plan and the remedy. A promise without a plan is hard to act on, because SLAs are usually tier-specific.
What status pages report instead
The 19 status-page documents carry observed figures, and they vary much more than the promises do. Telstra reports its Messaging API at 100.00% over the past 7 days, while its KYC Match API reads 97.35%. Kyma API lists 33 components, and its lowest, a routed Gemini 3.7 Flash model, reads 63.69%. A status page is not a commitment, but it is evidence of what the provider is willing to show, component by component.
Seven documents are flagged non-conformant against SLA4OAI, and all seven are status-page-only files with no guarantee to express.
What a good one looks like
A good SLA document names the plan, the percentage, the measurement window and the credit, and points to the page it came from. Few providers publish all four. Most publish rate limits and pricing tiers, which is why 262 bases could be generated at all, and leave availability unstated.
Takeaway
If you publish an API, a one-line uptime commitment on a public page, tied to a plan, moves you from the synthetic 262 into the searched 22. If you integrate one, read the coverage block before you read the number. Browse every document at apis.io/sla/.