Developer resources

Build around identity, selected context and useful work.

Use the API owned by each service. Sign-in, file access, agent knowledge and collaboration participation are distinct permissions.

Cortex collaboration

Profiles, shared requests, versioned results and reviewed hand-offs. These browser-backend routes require a current Cortex session and participation; they are not a general third-party bearer API.

Read the payload guide

Personal Data Vault files

Owner-device setup, application consent, encrypted upload/retrieval and separate selected-file decryption. Independent of MPC wallets.

Owner API schema · File API schema

Hybrid ID authentication

Register actual HTTPS origins and exact callbacks. Owners approve the purpose and scope of access. An email address is not a permission grant.

Registered-client participation API

Reference for owner-authorized participation and introductions. Customer access is disabled. Request integration review before implementing against this candidate contract.