Trust center

Service level

What CapitolMath commits to for availability and support. It applies to every paid plan; a signed enterprise agreement may set different terms.

Last updated November 5, 2026

Availability

The CapitolMath application and the v1 API will be available at least 99.5% of each calendar month — no more than about 3 hours 39 minutes of downtime in a 30-day month.

How it's measured

Availability is the share of minutes in the month in which the service answered correctly. A probe on a separate server checks /api/health, which includes the database, once a minute; a minute counts as down when it gets no answer within 10 seconds, or anything but a healthy one. The record is public on the status page. Your own records of failed requests are welcome evidence when you report an outage.

What doesn't count

  • Scheduled maintenance announced at least 48 hours ahead, up to 4 hours a month, preferably outside US business hours.
  • Problems at a legislature's own website that delay new data. Freshness depends on each source and isn't covered here.
  • Requests refused for exceeding your plan's rate limit or quota, or an account suspended under the terms.
  • Delivery failures at your webhook endpoints, and failures of your own networks or systems.
  • Events beyond our reasonable control, such as a widespread outage of our hosting provider or the internet.

Support response times

Report problems to support@capitolmath.ai or with the help button on any page. Say what's happening and how widely, and we'll agree the severity with you. Business hours are 9:00–17:00 US Eastern time, Monday to Friday, excluding US federal holidays.

Support response targets by severity
SeverityMeansFirst response within
Severity 1The API or the application is unavailable, or data is exposed, for your whole account.4 business hours
Severity 2A major feature — webhooks, exports, a data endpoint — is failing or badly degraded, with no workaround.1 business day
Severity 3A feature is impaired but a workaround exists, or data looks wrong.2 business days
Severity 4A question, a documentation request, or a feature request.5 business days

A first response is a person looking at your problem and telling you what happens next — not an automatic acknowledgement. We work on Severity 1 issues continuously until they're resolved or downgraded.

If we miss

This version of the service level doesn't include service credits. If we miss the availability target in a month, we'll tell you on request what happened and what we've changed to stop it happening again.