Reference

Capability status

What the platform offers today, stated at the level of the capability registry. A capability that is not beta or production is not available for enforcement, no matter what any other page says. The same registry is served at GET /api/v1/meta.

Beta

Available in sandbox and shadow mode to evaluation customers. Not evidence that production validation has passed.

CapabilityStateSummary
action_registryBetaRegistered protected actions with risk class, context schema, mode, audiences, and proof TTL.
assurance_profileBetaTyped claims with status, coverage, freshness, limitations, and versions. Confidence values are omitted until real-human calibration exists.
authorizeBetaServer-created authorization requests returning allow, challenge, hold, or deny. Insufficient evidence is an assurance status translated by policy.
challenge_passkeyBetaAction-bound WebAuthn challenge with an immutable display snapshot and explicit relying-party confirmation.
evaluationsBetaShadow evaluations with coverage, abstention, challenge, and outcome metrics.
evidence_ingestBetaSigned, replay-checked derived-feature windows from the browser SDK.
explicit_action_approval_claimBetaCompleted action-bound challenge with method and strength preserved.
outcome_reportingBetaCustomer-reported enforcement outcomes attached to decisions.
policy_versionsBetaImmutable policy versions with activation and rollback.
proof_of_agencyBetaES256-signed, audience-bound, action-bound proof with JWKS publication, revocation status, and optional one-time consumption.
shadow_modeBetaPer-action shadow decisions that never issue enforceable proofs or execute protected handlers.
subjectsBetaTenant-scoped pseudonymous subjects with enrollment, revocation, deletion, and export.

In development

Exists in the codebase; verification is not complete and behavior can change.

CapabilityStateSummary
consoleIn developmentCore operational views exist; exhaustive role and assistive-technology journeys remain under verification.
demoIn developmentSandbox protected-action demonstration under local verification. It is not evidence of real-human accuracy.
open_verifierIn developmentVerifier libraries exist in this repository; a public specification is not yet published.
status_monitoringIn developmentExternal monitoring is not configured; the status page states this plainly.
webhooksIn developmentDurable delivery exists, but atomic event-to-outbox reconciliation remains under verification.

Research

Experimental. Outputs are for sandbox and shadow evaluation only and carry no calibrated confidence.

CapabilityStateSummary
automation_claimResearchNarrow heuristic automation and replay indicators, not general bot detection.
cross_device_evidenceResearchQuarantined until the device evidence program is defined.
native_sdksResearchSwift and Kotlin legacy adapters are quarantined and are not compatible with the canonical API or released.
operator_change_claimResearchExperimental within-session change indicator evaluated on synthetic data only.
operator_continuity_claimResearchExperimental categorical status for sandbox and shadow evaluation only. No calibrated confidence or live enforcement approval.
real_human_benchmarkResearchNo recorded-human evaluation of the continuous engine exists yet.

Unsupported

Not offered. The Assurance Profile reports these claims as unsupported so policies cannot rely on them.

CapabilityStateSummary
agent_mandate_validity_claimUnsupportedAgent authorization is rejected. No mandate verifier exists.
challenge_smsUnsupportedThe legacy SMS channel is not action-bound and is not offered by the canonical challenge API.
device_integrity_claimUnsupportedNo attestation evidence is accepted yet.
human_presence_claimUnsupportedInteraction activity is not accepted as proof of human presence or liveness.
identity_anchor_validity_claimUnsupportedIdentity anchors are declared at enrollment but not verified by GrayPass.
personhood_claimUnsupportedNot offered.

Generated from the API contract in contracts/ and the source in docs/. The build fails if this page disagrees with the running API.