Werracle Radar API — Service Level Statement
| Pro | Institutional / Curator | |
|---|---|---|
Monthly availability target (API responds with 2xx/4xx to
/v1/radar/overview) |
best effort | 99.0% |
Data freshness target (data_stale=false in
/overview) |
best effort | 95% of the month |
| Support channel | e-mail, 2 business days | e-mail / shared channel, next business day |
| Planned maintenance notice | — | 48 h, max 4 h/month, excluded from availability |
| Service credit if availability < target | — | 10% of monthly fee per full 1% below target, capped at 50% |
Exclusions
The following are not counted as unavailability:
- force majeure;
- failures of third-party data sources, for example blockchain RPC providers or the Morpho public API;
- outages of the blockchain itself (chain halts, sequencer outages);
- customer-side issues;
- traffic that exceeds the rate limits;
- suspension under the Terms.
How it is measured
Monitoring. An external monitor on a separate server (Frankfurt) checks the API every 5 minutes. Monthly reports are available on request.
Credits. A customer must request a credit within 30 days of the month end. Credits are the sole remedy for missing a target.