SOL 1 SERIES / NOW AVAILABLEREAD THE RELEASE NOTES
mindlarp_
KEEP YOUR KEYS SAFE

Simple access. Careful control.

Authenticate every API request with a bearer token created in your MindLarp console.

Bearer authentication

Include your secret key in the Authorization header of every request.

HTTP
Authorization: Bearer ml_sk_live_your_secret

Key lifecycle

A key can make requests as soon as it is created. You can set an expiration date, limit its scopes, and revoke it at any time. Revocation takes effect immediately.

Scopes

  • models:read allows listing the available model catalog.
  • inference:write allows chat completion requests.

Security checklist

  • Store keys in a server-side secret manager or environment variable.
  • Never include keys in client-side JavaScript, mobile apps, logs, or Git.
  • Use a separate key for each application and environment.
  • Set expiration dates and rotate credentials regularly.
  • Revoke a key immediately if you suspect it was exposed.