Personal API token
A personal API token lets your scripts or CI call the agent over HTTP with your account's access. Treat it like a password: anyone with the value can act with your permissions. You must be signed in to create and manage tokens.
Create and store a token
- Open Account → API tokens.
- Choose New token, enter a recognizable name and optionally set an expiry date. It stops working at the end of that day in UTC; leave the date empty for a token that lasts until you delete it.
- Choose Create token and copy the value from the reveal window. Elowen shows it only once and stores only its hash.
- Save it in a secret manager or CI secret store, not in source code, chat or logs.
- Use it as a bearer credential for the Agent API. The Calling the agent row can copy a ready curl example with your instance address.
If you close the reveal or lose the value, it cannot be displayed again. Choose Copy for the token and confirm regeneration. Elowen issues and reveals a replacement value; update every caller because the old value stops working immediately.
Review and manage tokens
Open a token's row to inspect its usage over a selected date range and its limits. The range is shared by token rows. The summary includes requests, turns, answered and failed turns, tokens and tracked cost. Unknown cost is shown as unknown, not zero. See Usage & Costs for other usage views and the Agent API guide for request details.
Choose Limits to set optional daily or monthly cost, per-minute request or concurrent-turn limits. Reaching a limit can cause requests to be refused. Choose Delete to revoke a token and delete its recorded usage. New requests using it are rejected immediately; a turn it already started keeps running and can finish. Regenerating a value keeps the token's name, limits and recorded usage.
If tokens or statistics fail to load, use the displayed retry action. Do not include the token value in a support request.