Create an environment-bound API key with explicit product permissions
const url = 'https://api.katara.com/katara/v1/account/keys';const options = { method: 'POST', headers: { 'Idempotency-Key': 'example', 'X-Katara-CSRF': '1', Authorization: 'Bearer <token>', 'Content-Type': 'application/json' }, body: '"example"'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.katara.com/katara/v1/account/keys \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --header 'Idempotency-Key: example' \ --header 'X-Katara-CSRF: 1' \ --data '"example"'Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Header Parameters
Section titled “Header Parameters”Browser cookie mutations require value 1 and an allowed Origin. Session bearer clients may omit this header.
Required for cookie-authenticated changes. Use the UUID of the account that loaded the application. A different current cookie account returns account_changed before the handler runs. Session bearer and API key clients do not require this header.
Request Bodyrequired
Section titled “Request Bodyrequired”Keys with Cortex permission and no direct billing mode require managed-run creation permission. Their inference uses separately consented run budgets. Direct inference requires a configured billing mode, a personal identity and no resource restriction. A Live key pays with credits, the wallet allowance or a prepaid balance. A Test key pays with test USDC through the allowance or a prepaid balance, and only where the deployment runs a Test network; otherwise, or when it asks for credits, the request is refused with param mode. Community false keeps a key’s direct Cortex requests on Katara’s own models; it is on when omitted, and a marketplace-only key cannot turn it off.
object
Responses
Section titled “Responses”Successful request
object
object
object
Example
{ "api_key": { "audience": "katara:platform", "scopes": [ "billing:read" ], "mode": "" }}Account_changed: reload and review with the signed-in account.
default
Section titled “default”Request error
object
object
Stable; branch on it. Any operation can answer invalid_request, with param naming the refused field when there is one; human_session_required, when an API key, service account or workload calls an operation only a signed-in person may perform; reauthentication_required, when a person’s sign-in is too old for the operation; permission_denied; route_not_found and method_not_allowed, when no operation matches the path or method; and feature_unavailable, when the operation’s service is not enabled on this deployment.
The request field a refusal is about, such as the agent_id or run_id query parameter; null when the refusal is not about one field.
Example
{ "error": { "action": "sign_in" }}