API keys.
Scripts authenticate with a key. The web app uses a signed-in session. Both spend the same USD balance.
Send the key
Authorization: Bearer hw_live_...Keys look like hw_live_ followed by a random string. Put the key in an environment variable. A key that is wrong or revoked returns 401.
We store a hash. If you lose the key, revoke it in the app and create another. An API key cannot create further keys.
Create a key in the app
Open API keys while signed in. Give the key a name and choose scopes:
| Scope | Use it for |
|---|---|
humanize | Creating, reading, and canceling runs. This is the scope a rewrite script needs. |
billing:read | Reading balance, ledger, and usage. It does not spend money by itself. |
Creating keys is limited to 10 per hour. The browser session that creates the key must send the site’s CSRF cookie. Scripts that already have a key do not.
/v1/me
The signed-in account: identity, balance, and whether a run can start.
{
"id": "usr_01J9ABCDEF",
"email": "[email protected]",
"name": "Alex",
"balance": {
"paid_usd": "12.000000",
"bonus_usd": "1.000000",
"held_usd": "0.050000",
"available_usd": "12.950000",
"bonus_expires_at": "2026-11-04T00:00:00+00:00"
},
"restrictions": {
"batch_enabled": true,
"max_chars_per_run": 5000,
"can_run": true,
"can_run_reason": null
}
}available_usd is paid plus bonus, minus anything held for a run in progress. When can_run is false, can_run_reason says why — usually an unconfirmed email or an account that is still being set up.
/v1/api-keys
Lists keys that have not been revoked. The response includes the prefix, name, scopes, created_at, and last_used_at. It never includes the secret.
/v1/api-keys/{id}
Revokes a key. The response is 204 with an empty body. A revoked key stops working immediately.
/v1/billing/balance
The same balance figures as /v1/me, without the profile. Useful for a script that only needs to know whether it can spend.
{
"paid_usd": "12.000000",
"bonus_usd": "1.000000",
"held_usd": "0.050000",
"available_usd": "12.950000",
"bonus_expires_at": "2026-11-04T00:00:00+00:00"
}/v1/billing/ledger
Append-only balance history, newest first. Query limit (default 50, max 200), cursor, and type. The next page is next_cursor.
GET /v1/billing/ledger?limit=50/v1/billing/usage
Usage grouped by day. days defaults to 30.