CURRENT RELEASE · PRODUCT V1.13.0

Execution-critical health, without a green-screen shortcut.

Operational means the database, strict schema and receipt signing path all passed live checks. Any red state requires payment callers to fail closed.

Overall serviceSelected hosted-service dependency checks passed.OPERATIONAL
policy engineReported by the live production health probe.OPERATIONAL
databaseReported by the live production health probe.OPERATIONAL
strict authority schemaReported by the live production health probe.OPERATIONAL
signed receiptsReported by the live production health probe.OPERATIONAL
execution evidence signingReported by the live production health probe.OPERATIONAL
scheduled maintenanceReported by the live production health probe.OPERATIONAL
provider reconciliationReported by the live production health probe.OPERATIONAL
provider credential encryptionReported by the live production health probe.CONFIGURED
x402 chain verificationReported by the live production health probe.CONFIGURED
billingReported by the live production health probe.CONFIGURED
threat intelligenceReported by the live production health probe.CONFIGURED

Checked Sep 7, 2026, 4:17:51 PM UTC UTC · release 1.13.0

This complete status snapshot was rendered on the server. It remains visible to people, search crawlers and AI agents when browser JavaScript is disabled.

Authoritative current release

MandateShield product v1.13.0, OpenAPI v3.4.0 and boundary specification v2.4.0 were released at . Mutable discovery URLs must be revalidated; production integrations can pin the immutable versioned contracts.

Current-release JSON · Immutable OpenAPI v3.4.0 · Immutable discovery v1.13.0

Availability contract

The public plans do not include a contractual uptime SLA or automatic service credits. The API publishes machine-readable health and uses explicit timeouts, retry guidance and fail-closed authorization semantics. A separate written order must state any enterprise SLA.

What this page proves

This is a current first-party runtime probe, not an independent uptime history. It does not claim certification or third-party monitoring. The raw response remains available at /api/health.