Service Level Agreement
Last Updated: 2026-04-15
This page describes the service-level targets we are committing to track for the Smarter Weather developer platform. During the beta period these targets are informational; they help you plan integrations and tell you what we hold ourselves to internally, but they do not create contractual remedies. A binding Service Level Agreement will be attached to the Developer Terms when the platform exits beta.
1. What we measure
- Monthly availability — the percentage of successful requests over a calendar month on the public REST APIs and MCP servers. A request is considered unsuccessful if we return a
5xxstatus that is not caused by client input, or if the request fails to complete within a reasonable upstream timeout under our control. Maintenance windows announced at least 48 hours in advance are excluded; unannounced maintenance is counted as downtime. - Latency — p50, p95, and p99 server processing time for each public endpoint and MCP tool, measured at the origin (excluding your network and any edge or CDN you place in front of us).
- Error rate — the proportion of
5xxresponses per endpoint and per tool, broken down by cause. - Meter accuracy — the lag and reconciliation delta between the usage counters shown in the developer dashboard and the billed amount on the next invoice. This is how we hold ourselves to truthful billing.
Live-ish availability and incident history will be published on a status page at status.smarterweather.com once it launches with the rest of Phase 1 of the developer platform.
2. Targets by tier
| Tier | Monthly availability | p99 latency | Support | Remedies |
|---|---|---|---|---|
| Free developer tier | 99.5% | Best-effort | Community support | None. Provided as-is for evaluation and prototyping. |
| Paid developer tiers | 99.9% (aspirational) | < 400 ms at the origin | Email support, best-effort response within 1 business day | Informational targets only during the draft period. Remedies will be defined in a binding SLA before exit from beta. |
| Enterprise | Negotiated per contract | Negotiated per contract | Named contact, negotiated response time | Service credits as defined in the master agreement. |
The 99.9% paid-tier target corresponds to approximately 43 minutes of downtime per month. The 99.5% free-tier target corresponds to approximately 3 hours 38 minutes per month. We aim to exceed both in practice.
3. Exclusions
The following are excluded from availability calculations and do not count as downtime:
- Announced maintenance windows (at least 48 hours' notice, not more than one window per calendar month, not more than 2 hours per window in aggregate).
- Issues caused by your code, your network, your third-party dependencies, or misuse of the API (including calls that violate the rate limits or the Acceptable Use Policy).
- Failures or degradation of upstream data providers (NOAA, the National Weather Service, and other sources identified in our Acknowledgements) that we cannot route around. We will surface such upstream incidents on the status page but they do not count against this SLA.
- Events beyond our reasonable control, as described in the Developer Terms.
4. Path to a binding SLA
The targets above describe the bar we intend to hold for the generally-available (GA) release of the developer platform. Before exit from beta we will:
- Publish at least three full months of measured availability, latency, and error-rate data on the status page.
- Publish a concrete service-credit schedule for paid tiers (for example, a percentage of monthly fees credited on the next invoice for each availability band missed).
- Attach the binding SLA to the Developer Terms and notify paid customers in advance of the effective date.
Until that happens, this page is a good-faith statement of intent, not a contractual commitment.
5. Enterprise customers
Enterprise customers can negotiate a binding SLA with higher availability targets, defined latency bands, service credits, and support-response commitments as part of their master agreement. Contact us via the contact form or email alex@smarterweather.com to discuss.