Statistic · AI Tagging · From the AI Tagging Provider Index
5of 10
Vision APIs publishing a paid-tier uptime SLA.
Five of the 10 leading image-tagging APIs publish a paid-tier uptime SLA — a documented uptime commitment with service credits for breaches. The three hyperscaler clouds all do, plus Google Gemini (via Vertex AI) and Cloudinary AI. Two of the three frontier multimodal LLMs publish only a status page, not an SLA. For operators whose production workload depends on tagging being up, that's a difference that matters.
Production SLA published · by provider
| Provider | SLA published | Notes |
|---|---|---|
| Google Cloud Vision | Yes | Vision API SLA published with monthly uptime percentages and credit schedule. |
| AWS Rekognition | Yes | Rekognition SLA documented with uptime tiers and credits. |
| Azure AI Vision | Yes | Azure Cognitive Services SLA covers Vision; standard credit schedule. |
| Google Gemini (vision) | Yes | Vertex AI generative-AI SLA covers Gemini deployments. |
| Cloudinary AI | Yes | Enterprise plan SLA published; lower tiers reference best-effort. |
| Clarifai | Partial | Enterprise SLA available; not published in self-serve documentation. |
| Imagga | Partial | Enterprise plan SLA referenced; not visible on self-serve plans. |
| Hive AI | Partial | Enterprise SLA available on request; not in public docs. |
| Anthropic Claude (vision) | No | Status page published; no paid-tier uptime SLA contract in public docs as of snapshot. |
| OpenAI GPT-4o (vision) | No | Status page published; no paid-tier uptime SLA contract in public docs as of snapshot. |
"Yes" requires a public, documented uptime SLA with quantified targets and a credit or remedy schedule. Status pages, while useful, do not constitute an SLA. "Partial" means the SLA is available on enterprise contracts but not visible on the public self-serve tier. Cells re-verified monthly. Methodology →
Why this is the column we hear about most
When a procurement team picks a vision API for a production pipeline, the SLA column is almost always the column that gets escalated to legal. Status pages tell you what's broken now; SLAs tell you what the vendor is on the hook for when it breaks. The fact that two of the three frontier multimodal LLMs don't publish one is the single biggest reason we see them deployed in research and analysis pipelines but not in production tagging at large enterprises — yet. The classical CV providers, including all three hyperscalers, score "Yes" on this column primarily because they've been selling to enterprise procurement for a decade.
What counts
- Yes — a public SLA document with quantified uptime targets and a documented credit schedule, applicable to a self-serve paid tier.
- Partial — SLA exists on enterprise contracts but is not visible to self-serve customers in public docs.
- No — no SLA contract documented; status page only.
Cite this statistic
DAM LLM Research. "Vision APIs publishing a production SLA, May 2026." damllm.ai, 2026. https://damllm.ai/statistics/vision-apis-with-sla/