Mint Access Token
Exchange a long-lived machine credential for a short-lived access token.
Documentation Index
Fetch the complete documentation index at: https://docs.kynasmith.dev/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Body
Machine credential exchange request for POST /api/auth/access-tokens.
Migration path (#6, #53):
The preferred shape is evolving toward { api_key, scopes? } where the
project scope is inferred from the authenticated credential. During the
migration window both the legacy dual-credential shape and the simplified
api_key shorthand are accepted.
When project_id is omitted the API infers the project scope from the
authenticated credential. When provided, the API validates it matches.
Simplified API key secret. When provided as the sole credential field, the backend resolves the key by its secret hash. Preferred over the legacy api_key_id + api_key_secret pair.
API key identifier, if using the legacy credential pair.
API key secret, if using the legacy credential pair.
Explicit project context for the access token request. When omitted, inferred from the authenticated credential.
Requested access-token scopes.
Service-account identifier, if using a service account.
Service-account secret, if using a service account.
Response
Successful Response
Access-token exchange response.
Short-lived backend-signed access token.
Access-token lifetime in seconds.
Bound organization identifier.
Bound project identifier.
Bearer token type marker.
"Bearer"