Keys to your workspace.
Keep access intentional, scoped, and easy to revoke.
Pre-launch documentation. HexSolver is under development. Check Service status and confirm access with support before sending live requests.
Task API authentication.
Include your workspace API key in the clientKey field of task API requests. Keys begin with hx_live_. Each key belongs to one account; task results are checked against that account before being returned.
The database stores only a SHA-256 digest and a short display prefix. Full key values cannot be recovered after creation. Make a new key if you lose the secret.
{ "clientKey": "hx_live_YOUR_SECRET_KEY", "taskId": "YOUR_TASK_ID"}Dashboard sign-in.
Sign in to the dashboard to manage your account, API keys, billing, and usage. If your session expires, sign in again to continue.
Use your API key for solver requests and your email and password for dashboard sign-in. Never send your dashboard password to a solver endpoint or include it in integration code.
Rotate without surprises.
- 1
Create a new API key with a descriptive name.
- 2
Update your server-side secret and deploy your integration.
- 3
Confirm requests are succeeding with the new key.
- 4
Revoke the old key in Dashboard → API keys.
Up to 10 active keys are allowed per account. Revoked keys stop working immediately. Changing your password signs you out of all sessions, but does not revoke your API keys.
Keep secrets on the server.
Never use a NEXT_PUBLIC_ environment variable for an API key. Do not put secrets in a query string or expose them in browser code. Contact support with a task ID or request ID, never your secret key.