Authentication — ML Junction docs

Inference endpoints accept a gateway API key in the Authorization header. Dashboard and organization endpoints use the signed user session supplied by Clerk. Public catalog and status endpoints require no authentication.

Authorization: Bearer YOUR_API_KEY

Credential · Use · Storage guidance
Gateway API key · Server-to-server inference calls · Secret manager or encrypted server environment
Clerk user token · Dashboard authentication · Obtain from the active Clerk session; organizations and RBAC are owned by ML Junction
Provider BYOK secret · Calls billed by your provider account · Submit once through the protected BYOK API; never read back
No credential · Catalog, provider directory, usage popularity, and public status · Safe for browser fetching

Use separate keys for development, staging, and production.. Rotate a key immediately if it appears in a repository, screenshot, browser bundle, or support transcript.. Apply model, RPM, TPM, concurrency, and maximum-output policies to each key.. Treat a 401 response as invalid or missing authentication and a 403 response as an authorization or policy failure.

Canonical URL: https://mljunction.com/docs/authentication