Authentication - Klint

Every request sends an API key as a bearer token:

curl "https://api.tryklint.ai/v1/instagram/accounts/ig_account_01j2k9m4q7" \
  -H "Authorization: Bearer $KLINT_API_KEY"

You create keys in the Klint dashboard.
Store the key in the KLINT_API_KEY environment variable. Never store it in code, prompts, or repositories.
In agent contexts, provide the key through the environment. Klint never requires an interactive login mid-task.

The key format and the account-free onboarding flow (trial token → npx klint setup → claim) are planned, not final contract.

If you get a 401

A missing, malformed, or revoked key returns 401 authentication-required as a problem object:

{
  "type": "https://api.tryklint.ai/problems/authentication-required",
  "status": 401,
  "request_id": "req_example_50",
  "detail": "Missing or invalid API key. Send Authorization: Bearer <api-key>."
}

Check these items in order:

The Authorization: Bearer prefix is present.
The key has no surrounding quotes or whitespace.
The key is active in the dashboard.

A 401 is never retryable with the same credentials.

Key safety

Treat keys as secrets.
Rotate a key on suspicion of exposure.
Scope one key per integration.
Revoke unused keys.
Klint keys will appear in secret-scanning feeds at launch. Treat a key that lands in a public repository as compromised.

API reference overview Errors

⌘I