Endpoint
- Which runtime is executing
- Which capabilities are enabled
- Which schema versions are supported
- Whether signing is operational
- Whether replay protection is active
Why Runtime Manifests Exist
Authorization decisions are only meaningful if the runtime producing them is known. The runtime manifest exposes information about the execution environment.Example Request
Example Response
Response Fields
version
Runtime version.runtimeHash
Deterministic runtime identifier.capabilities
Features supported by the runtime.| Capability | Description |
|---|---|
| deterministic-evaluation | Deterministic policy evaluation |
| attestation-signing | Cryptographic attestation generation |
| replay-protection | Replay attack prevention |
| bundle-verification | Bundle and provenance verification |
supportedSchemaVersions
Policy schema versions supported by the runtime.startedAt
Runtime startup timestamp.signingKeyStatus
Signing subsystem status.auditDbStatus
Audit persistence status.replayProtection
Replay protection status.Operational Uses
Health Verification
External systems can confirm:Deployment Validation
Operators can verify:- Runtime version
- Runtime hash
- Capability set
- Startup status