CHEESE API

Authentication

Create, store, scope, rotate, and revoke CHEESE API keys safely.

Suggest an edit

Send a CHEESE API key in the x-api-key header. The OpenAPI document represents this as an API-key security scheme, so generated tools and the interactive reference can authenticate correctly.

x-api-key: YOUR_API_KEY

Keys may be scoped independently for search, sampling, selections, and durable runs. A missing or invalid key returns 401; a valid key without the required entitlement returns 403.

Use DEEPMEDCHEM_API_KEY for Python automation or deepmedchem login for the OS credential store. Named default and dev profiles keep credentials isolated; navigator auth login remains a compatibility alias using the shared store. Rotate a key by creating its replacement, updating clients, verifying use, and then revoking the old key. Never send a key in a query string or to documentation analytics, feedback, or AI tools.

The interactive reference keeps a visitor-provided key in browser memory/session storage only. It calls the API directly over the explicit docs CORS origin and does not proxy credentials through the documentation server.