Definitions
Counts as Downtime
- API returns 5xx errors for more than 5 consecutive minutes
- API response time exceeds 30 seconds for more than 5 consecutive minutes
- Complete inability to authenticate with a valid API key
API StatusAll systems operational
API StatusAll systems operational
Reliability Commitment
Our commitment to reliability. Contractual uptime guarantees, response time targets, and support SLAs backed by wallet credits.
99.95%Enterprise Uptime
50msP50 Computation
1 hrCritical Response
50%Max Credit
Uptime Targets
Each plan includes a defined uptime target. If we fall short, eligible plans receive wallet credits applied to the next billing cycle.
| Plan | Uptime SLA | Monthly Downtime Budget | Downtime Credit |
|---|---|---|---|
| Starter | 99.5% | ~3.6 hours | None |
| Professional | 99.9% | ~43 minutes | 10% of monthly cost |
| Business | 99.9% | ~43 minutes | 25% of monthly cost |
| Enterprise | 99.95% | ~22 minutes | 50% of monthly cost |
Definitions
Definitions
Definitions
Performance
Performance targets measured at the API gateway. Actual latency may vary based on query complexity and network conditions.
| Endpoint Type | Target P50 | Target P95 |
|---|---|---|
| Computation (birth chart, planets, panchang) | 50ms | 200ms |
| AI Chatbot (natural language query) | 3s | 15s |
| Streaming (real-time AI response) | First token: 1s | Complete: 15s |
| Batch endpoints | 500ms | 2s |
Support
Maximum initial response time by priority level. All times refer to business-hours response unless otherwise noted. Enterprise critical support operates 24/7.
| Priority | Starter | Professional | Business | Enterprise |
|---|---|---|---|---|
| Critical (API down) | 24 hours | 12 hours | 4 hours | 1 hour |
| High (degraded performance) | 48 hours | 24 hours | 8 hours | 2 hours |
| Normal | 5 business days | 3 business days | 1 business day | 4 hours |
| Low | Best effort | 5 business days | 3 business days | 1 business day |
Credits
How downtime credits are calculated and applied to your account.
Credits
Credits are applied to your next billing cycle as a wallet balance addition. No cash refunds.
Credits
Credit requests must be submitted within 30 days of the incident. Include the date, time, and affected endpoints.
Credits
The maximum credit for any billing period is 50% of your monthly subscription cost, regardless of total downtime.
Credits
Email [email protected] with incident details
Include the affected dates, times (UTC), and endpoint paths
We verify against our monitoring data within 5 business days
Approved credits are added to your wallet balance
Transparency
We continuously monitor all API endpoints and provide full transparency into platform health.
Transparency
Uptime monitored every 60 seconds from multiple geographic regions
Transparency
Opt-in email notifications for outages and degraded performance
Transparency
Historical uptime and incident reports available on request
Maintenance
We perform most updates with zero downtime. When maintenance is required, we follow a predictable schedule.
Maintenance
Tuesdays and Thursdays, 2:00 – 4:00 AM IST. Announced at least 48 hours in advance via the status page and opt-in email.
Maintenance
Announced via the status page as soon as possible. Reserved for critical security patches or infrastructure issues that cannot wait for a scheduled window.
Maintenance
The majority of updates are deployed with zero downtime using rolling deployments. No maintenance window required for routine releases.
Enterprise customers can negotiate custom uptime targets, dedicated support channels, and tailored credit policies. Contact our sales team to discuss your requirements.
Last Updated: February 10, 2026