---
title: JIL Pre-Clearance Service Level Agreement
version: 2026.05.03
owner: JIL Sovereign Technologies, Inc.
audience: institutional custodians, MSA addendum
status: GA
---

# JIL Sovereign Pre-Clearance  -  Service Level Agreement

This SLA governs the JIL Pre-Clearance API (`https://preclearance.jilsovereign.com`).
It is incorporated by reference into any Master Services Agreement (MSA) signed
with JIL Sovereign Technologies, Inc.

## 1. Availability

| Window | Target |
|---|---|
| Monthly uptime | 99.5% (single-region active, "Pilot tier") |
| Monthly uptime | 99.9% ("Production tier", multi-region active/standby  -  Q3 2026) |
| Monthly uptime | 99.95% ("Mission-critical tier", multi-region active/active  -  Q1 2027) |

Uptime is measured at the public ingress (`preclearance.jilsovereign.com`) by an
independent synthetic prober (Cloudflare Monitor + Pingdom). A request counts as
"available" if it returns any 2xx, 4xx (other than 429), or any non-5xx status
within 5 seconds.

## 2. Latency

Tier 1 Pre-Clearance latency targets follow §10 of the
[Custodial Egress Design Document](/docs/strategy/preclearance/JIL_Custodial_Egress_PreClearance_Design.md).

| Stage | p50 | p99 | Notes |
|---|---|---|---|
| **PoCS attestation** (Phase 0/1 today: PSA bundle without cosign) | 350ms | 1,500ms | Stage 1 address-intel + Stage 2 KYC + Stage 3 sanctions + Stage 4 risk; signed but advisory |
| **PoCS attestation full** (target with §6.3 deep-checks at scale) | 8s | 30s | Phase 1 deployment target |
| **Threshold signing** (Phase 2 - co-signer service) | n/a (pre-Phase 2) | n/a | Target: p50 4s once §5 cosigner ships |
| **End-to-end clearance to broadcast** (Phase 2/3) | n/a (pre-Phase 2) | n/a | Target: p99 60s once full Tier 1 is live |
| `POST /v1/preclearance/verify` | 25ms | 150ms | Read-only signature verification |
| `GET /v1/preclearance/psa/:id` | 15ms | 100ms | Cached lookup |

**Phase 0 / 1 (today):** the PSA produced by `/v1/preclearance/validate` is the
signed PoCS attestation bundle from §6.3 of the design doc. The full Tier 1
flow (§6.4 pre-image binding, §6.5 threshold cosigning, §6.6 OOB confirmation,
§6.7 multi-source broadcast) lands in Phase 1-3. Latency targets in this table
are split accordingly.

Latency is measured server-side at the JIL ingress, excluding network RTT
between caller and the JIL edge. Customer-measured latency may exceed targets
due to network conditions JIL does not control; remedies below apply only to
server-side latency.

## 3. Throughput

- Default sustained rate: **100 req/s per customer**, **200 burst**.
- Above-default tiers available per MSA addendum:
  - Tier B: 500 req/s sustained, 1,000 burst.
  - Tier C: 5,000 req/s sustained, 10,000 burst (requires capacity reservation).
- Excess requests return HTTP `429` with `Retry-After` header.

## 4. Validity Window

Issued PSAs are valid for **60 seconds** from `issued_at`. After expiry, the
custodian must re-call `/validate` (idempotent within the same `transit_id`
inside 60s, no re-billing).

## 5. Fault Attribution

The following are **excluded** from SLA breach calculation:

1. Network outages between customer and the JIL edge (DNS, BGP, transit).
2. Force-majeure (regulator order, validated nation-state attack, BFT halt
   triggered by adaptive quorum policy  -  see `docs/CANONICAL_PARAMETERS.md`).
3. Customer-misuse: malformed requests, expired credentials, traffic above
   contracted rate before opting in to Tier B/C.
4. Maintenance windows announced 72h+ in advance via status page (≤ 4h/mo).
5. Outages caused by upstream Tier-1 dependency degradation (kyc-service,
   sanctions-screening-cache, risk-scoring-attest)  -  JIL operates these on
   the same SLA and the same penalty waterfall applies.

## 6. Remedies

If the **monthly uptime** target is missed, the customer is entitled to a
service credit on the next monthly invoice:

| Uptime achieved | Credit |
|---|---|
| < 99.5%, ≥ 99.0% | 10% of monthly fees |
| < 99.0%, ≥ 95.0% | 25% of monthly fees |
| < 95.0% | 50% of monthly fees |

If the **p99 latency** target is missed in 2+ consecutive months, the customer
may terminate the MSA without penalty on 30 days' notice.

Credits are exclusive remedy; JIL is not liable for consequential damages
arising from PSA delivery failure (custodian's TAP must implement a fallback
policy  -  see Section 8).

## 7. Status Page + Incident Communication

- Real-time status: `https://status.jilsovereign.com`
- Incident class definitions (Sev1 outage, Sev2 degraded, Sev3 partial-feature):
  see `docs/operations/incident-response.md`.
- Sev1 → public RFO within 5 business days.
- Customers on Tier B/C receive a dedicated Slack/Teams shared channel.

## 8. Customer Obligations (TAP Fallback)

Custodians **must** configure a fallback policy in their Transaction
Authorization Policy for `/validate` 5xx or timeout (default: hold for human
review, do not auto-pass). JIL is not liable for transfers signed without
attestation when the API is unreachable.

## 9. Change Process

This SLA may be amended on 30 days' written notice. Material reductions in
target (e.g. lowering uptime from 99.5% to 99.0%) require customer
counter-signature. Improvements take effect on the announced date.

---

_Last updated: 2026-05-03 (initial GA SLA, supersedes informal targets in
`JIL_PreClearance_Layer_TDD.md` §9)._