401 or invalid API key
Check whether the key is valid for this account, is copied fully, is stored server-side, and is sent with the Bearer prefix.
Most API failures can be narrowed down quickly if you check the base URL, API key, model name, quota, request logs, and live pricing in the right order.
Check whether the key is valid for this account, is copied fully, is stored server-side, and is sent with the Bearer prefix.
Reduce concurrency, retry with backoff, check key or account limit, and inspect whether the same key is shared by multiple tools.
Confirm the model exists on live pricing, the model name is exact, and the endpoint type matches your request shape.
Use https://api.tacklekey.com/v1 for OpenAI-compatible requests unless your console or docs show a different documented endpoint.
| Step | What to check | Entry |
|---|---|---|
| First raw request | Run the cURL example first so SDK wrappers are not hiding the real status code. | Open |
| Logs | Find the request by API key, model, timestamp, status, and error message. | Open |
| Balance and pricing | Check whether the request consumed quota and whether the model price matches expectations. | Open |
| Small retry | Retry with one short prompt after fixing the most likely configuration issue. | Open |
Common causes include a missing Bearer prefix, using a key from another account, copying whitespace, using a revoked key, or sending the request to the wrong base URL.
Use exponential backoff, lower concurrency, avoid sharing one key across many jobs, and check key or account limit and logs before increasing traffic.
Copy the model name from live pricing or docs, confirm endpoint support, and send one small request before using the model in a batch.
Create an account, generate an API key, then replace your client base URL with the TackleKey endpoint. Keep keys server-side and verify live pricing before scaling traffic.