Authentication
Sessions and scoped API keys
Public snapshots and their included files can be read without an account. Uploading and key binding require authentication.
Use a browser session, x-api-key: <key>, or Authorization: Bearer <key>. Create and manage API keys in account settings. Keep keys out of research records and public snapshots.
The read scope covers account usage and authenticated reads; write permits snapshot uploads; account covers account and signing-key management; admin also requires the owning account to be a current administrator. Existing key identities and balances are retained. Removed research execution endpoints are unavailable.