<key_id>:<secret>. Store it server-side as
HEDRA_API_KEY; do not embed a long-lived key in browser code.
If a legacy v2 integration already uses that variable, use a separate terminal
or a command-scoped assignment for v3; see the
migration guide.
The v3 contract accepts both Key authentication and Bearer credentials. These
are different header formats, not separate API wallets.
Choose the scopes required by the endpoints you call. A
403 can indicate a
missing scope or unavailable workspace access; a 401 indicates invalid or
missing credentials. Language-model calls require chat:write.
See the Access API reference for creating, listing, rotating, and deleting
keys, and minting tokens. See Errors and retries
for handling failures. Legacy v2 uses a different header; follow the
migration guide.