Documentation that carries its status.

A route is not described robustly until its behaviour, input boundary, fallback and release status agree. Internal modules are not renamed as public interfaces.

Start with deep links Integrations

Resources

Topics, contracts and status

Search the documentation

16 results

App entry pointsDeep LinksSupported clarity:// routes, session fallback and release gates.Available App entry pointsIntegrationsCanonical status matrix for native, manual and unavailable paths.Available Platform and operationsClarity MCPPurpose-bound Context Capsules for external assistants — prepared, safety-bounded and not yet publicly connected.Available Platform and operationsFeature LabPublic proposals and account-linked voting with no release promise.Available Platform and operationsChangelogVersions and publicly visible changes.Available Platform and operationsSystem statusOperating states and known limitations.Available TrustSecuritySecurity boundaries, reporting route and responsible disclosure.Available TrustAI transparencyModel boundaries, data paths and the difference between cloud and on-device.Available TrustActionsConsequence classes, preview, consent, receipt and undo.Available Developer SandboxSandbox APINine versioned server operations with scopes, quotas and stable error shapes.Available Developer SandboxTypeScript ClientServer-side ESM client, type definitions and examples for all nine sandbox operations.Available Developer SandboxTool BuilderManifest, permissions, review, installation and native Clarity synchronisation.Available Developer SandboxDeveloper AppsSandbox projects with an owner, redirects, scopes, keys and usage metrics.Available Developer SandboxAPI keysOne-time disclosure, expiry, revocation and derived-only storage.Available Developer SandboxWebhook LabSigned sandbox events for testing your verifier.Available Private PreviewProduction accessProduction scopes, other people's account data and external code execution remain closed.Private Preview

App entry points

Deep Links

Supported clarity:// routes, session fallback and release gates.

Integrations

Canonical status matrix for native, manual and unavailable paths.

Platform and operations

Clarity MCP

Purpose-bound Context Capsules for external assistants — prepared, safety-bounded and not yet publicly connected.

Feature Lab

Public proposals and account-linked voting with no release promise.

Changelog

Versions and publicly visible changes.

System status

Operating states and known limitations.

Trust

Security

Security boundaries, reporting route and responsible disclosure.

AI transparency

Model boundaries, data paths and the difference between cloud and on-device.

Actions

Consequence classes, preview, consent, receipt and undo.

Developer Sandbox

Sandbox API

Nine versioned server operations with scopes, quotas and stable error shapes.

TypeScript Client

Server-side ESM client, type definitions and examples for all nine sandbox operations.

Tool Builder

Manifest, permissions, review, installation and native Clarity synchronisation.

Developer Apps

Sandbox projects with an owner, redirects, scopes, keys and usage metrics.

API keys

One-time disclosure, expiry, revocation and derived-only storage.

Webhook Lab

Signed sandbox events for testing your verifier.

Private Preview

Production access

Production scopes, other people's account data and external code execution remain closed.

Documentation contract

What a page must answer.

The index separates usable documentation from target architecture. That preserves technical depth without simulating a platform that does not yet exist.

Status: Is the path available, manual, in Private Preview or unavailable today?
Input: Which route, ID, permission or source does the current product contract accept?
Effect: What does the path open, read or write — and what does it explicitly not do?
Fallback: What happens when the app, permission, allowlist or release prerequisite is missing?
Lifecycle: Which check must pass before release, rotation, revocation or shutdown?