Skip to content
Start freeGPT-5 · Claude · DeepSeek V4 · Qwen3 — in ₹One OpenAI-compatible endpointBilled in rupeesGST invoiceNo international cardGet started →Start freeGPT-5 · Claude · DeepSeek V4 · Qwen3 — in ₹One OpenAI-compatible endpointBilled in rupeesGST invoiceNo international cardGet started →
Developer Guides

AI API uptime & SLA in India

unoblox targets 99.95% uptime across every AI model, with automatic multi-provider failover and one rupee-billed GST invoice monthly.

Production AI systems need guaranteed uptime, not best effort. unoblox backs every model behind its single OpenAI-compatible endpoint with a 99.95% uptime target, billed entirely in ₹ on one monthly GST invoice.

Why SLA matters for AI infrastructure

AI-driven products live or die by inference availability. A five-minute outage during a checkout flow, a support escalation, or an agent run costs real revenue—lost users, stalled transactions, frustrated customers. unoblox targets 99.95% uptime (at most roughly 52 minutes of downtime a year) with automatic failover across multiple upstream providers, so chatbots, RAG pipelines, and agents keep serving traffic even when one upstream has a bad day.

How failover actually works

Your code only ever sees one endpoint (https://api.unoblox.ai/v1) and one key (ub-gw-…). Behind that endpoint, unoblox tracks the health of every upstream provider serving a given model. If one provider slows down or errors out, requests route to a healthy alternate automatically, without you writing separate retry logic per provider. You get one invoice, in rupees, regardless of which upstream actually served a given request.

unoblox vs. going direct

FactorunobloxTypical single-provider API
Uptime target99.95%Often 99.9% or best-effort
FailoverAutomatic, multi-providerManual—you build it yourself
Incident visibilityLive status page + dashboardProvider status page only
Invoice₹, monthly, GST-compliantDepends on the provider
CoverageAll models, same targetVaries per model tier

Monitoring and alerts

Track uptime and latency in real time from your unoblox dashboard. Export request logs for 90–180 days, with a full audit trail of every token spent—no black-box billing, and a monthly GST invoice that lines up with what your dashboard shows.

Frequently asked questions

What happens if unoblox has an outage?

We target rapid incident detection and post updates to a public status page. Confirmed SLA misses are credited to your account—no claim form required.

Can I pass this uptime guarantee on to my own customers?

Yes. Many teams document unoblox as one link in their own uptime chain when writing SLAs for their end-users.

Does the SLA cover free and ₹0 models too?

Yes—the same 99.95% target applies across the catalog, including the free Qwen 1.7B tier, embeddings, and reranking. There's no downgrade for lower-cost models.

How do I verify uptime for my own reporting?

Check the live status page, and export your account's usage report—it shows request success rates for your own traffic over any billing period.

What should I do if my own internet connection drops?

Cache in-flight prompts locally and retry once connectivity returns. unoblox's API calls are safe to retry (idempotent), so a retry after a network blip won't double-charge you.

Can I get a higher SLA than 99.95%?

99.95% is the standard tier for every customer. For dedicated capacity or multi-region redundancy beyond that, contact support to discuss an enterprise arrangement.

Get started in rupees → https://unoblox.ai/sign-in

uptimeSLAreliabilityguides
ShareLinkedInWhatsAppTelegram

Start building in rupees

Call every major model through one OpenAI-compatible endpoint, billed in ₹ on a GST invoice.