Authentication & API keys

Getting a key

Visit /cli.
Connect a wallet. This links your current network for 24 hours and issues a key prefixed ltk_.
Use that key from any machine, CLI, or SDK. It isn’t tied to the browser it was issued in.

No key at all is required for a small guest allowance (3 requests/network), send any placeholder string as the key in that case.

Any of these are accepted:

curl https://asklethe.ai/v1/chat/completions \
  -H "Authorization: Bearer ltk_..." \
  -H "Content-Type: application/json" \
  -d '{...}'

curl https://asklethe.ai/v1/messages \
  -H "x-api-key: ltk_..." \
  -H "Content-Type: application/json" \
  -d '{...}'

x-api-key and api-key headers are checked first; Authorization: Bearer <key> is used otherwise.

Status	Code	Meaning
401	`invalid_api_key` / `missing_api_key`	No key sent, or the key doesn’t resolve to a known identity.
503	`unconfigured`	No LETHE API keys are configured server-side (deployment issue, not a client error).

See Errors for the full response shape.

⌘I