Developers
Call it. Inspect it. Verify it.
Seal data, use safe tokens, govern reveals, protect AI paths, erase subjects, and export evidence through one versioned API.
Live requests stay private.
Public visitors browse real examples. Organization members execute inside the authenticated console.
Developer surface
Browse publicly. Test inside your organization.
The reference never asks for a credential. The internal Studio applies the member’s organization, role, and vault policy.
Build
TypeScript SDKRepository client
HTTP APIVersioned JSON
Production APITokens · policy · AI · evidenceGETPOSTPUTPATCHDELETE
Internal API StudioLive, organization-authorized requests
Public referenceReal examples, no credential input
Application pattern
Your database stores the token.
Securelay stores the source value. A reveal returns the permitted value or an explicit denial—and records both outcomes.
Data sources
Databases
Applications
Files & events
Privacy vaultDetect · tokenize · encryptGoverned use
Application tokens
Controlled reveal
Verifiable receipt
Tenant key boundary Purpose + policy Linked evidence
Idempotent writes
Retry supported operations without duplicating the intended action.
Explicit denials
Separate authentication, policy, consent, rate, and infrastructure refusals.
Offline verify
Validate exported evidence outside the running product.