# Service Levels: Predge API and Verdicts (draft)

Version 0.1, drafted 20.10.2026. Draft, not yet reviewed by counsel. Applies only once a contract with an incorporated entity is signed. Until then, this document describes targets, not commitments.

## 1. Who we are and when we are covered

- Support is provided by the founder, alone. Coverage is best effort, seven days a week, and is not 24-hour staffed.
- Support contact: hello@predge.io. Status and incident updates: predge.io/trust and X @PredgeAI.

## 2. Severity definitions

| Level | Definition | Example |
|---|---|---|
| P1 | Production API or verdict service unavailable to most callers, or a signing or data integrity fault | Signing returns invalid signatures; API returns 5xx on all paid routes |
| P2 | Major function degraded, workaround exists | One route or data source stale; Desk alerts delayed |
| P3 | Minor issue or question | Documentation error; single caller error |

## 3. Targets

| Measure | Target |
|---|---|
| P1 acknowledgement | Within 4 hours of report, best effort |
| P1 first public update | Within 4 hours of acknowledgement, on predge.io/trust and X |
| P1 workaround or fix plan | Within 24 hours of acknowledgement |
| P2 acknowledgement | Within 1 business day |
| P3 acknowledgement | Within 3 business days |
| Planned maintenance notice | At least 48 hours on predge.io/trust, except emergencies |

## 4. Availability

- Target monthly availability for the public API: 99.0 percent, measured from our own health checks. This is an objective, not a guarantee.
- No service credits are offered until a public status page with uptime history exists. We will not issue credits we cannot measure.
- Once published, the uptime history will be on predge.io/trust. History starts on publication, not earlier.

## 5. Exclusions

Not counted against the target: outages of the Polygon, Arc, Base, Monad or other blockchains; outages of x402 facilitators, RPC providers and Polymarket data APIs; customer-side failures; planned maintenance notified per section 3; events outside Predge's reasonable control.

## 6. Paid calls and refusals

- A paid call that fails with a non-2xx status is not charged, because x402 settles only on success.
- Verdict and data responses are signed. A customer who receives an invalid signature should report it immediately to hello@predge.io. That is handled as P1.

## 7. Data and security obligations

Governed by the DPA (DPA-TEMPLATE.md, once signed) and the security questionnaire (SECURITY-QUESTIONNAIRE.md).

## 8. Changes

We may update this document with 30 days notice for material changes. Current version: predge.io/trust.