API keys and authentication
Create server-side keys, rotate exposed secrets and fix 401 errors.
Open guidanceHelp center
Help for API keys, model routing, billing and production issues
Search common questions, follow the right documentation path or collect the details support needs to debug an account-specific issue.
Search
How do I get a SmarToken API key?▼
Sign in with Google, open the console and create a key in the API key area. Store the key server-side and rotate it immediately if it is exposed.
Which endpoint should my OpenAI-compatible client use?▼
Use https://thesmartoken.com/v1 as the base URL. Chat completion requests use the standard /chat/completions path under that base URL.
How do I choose a model?▼
Choose by workload. Start with DeepSeek for coding or cost-effective reasoning, Kimi for longer context and Qwen for multilingual product behavior, then verify with your own prompts.
What should I do after Error 429?▼
Reduce concurrency, add backoff and retry later. If it repeats, include timestamp, endpoint path, model ID and whether the request was streaming when you contact support.
What should I do when balance is insufficient?▼
Add balance, shorten prompts, lower max output length or switch to a lower-cost model. Review wallet history if the spend does not match expectations.
Can I put API keys in browser JavaScript?▼
No. Keep SmarToken keys in backend code, serverless functions, workers or secure automation environments. Browser apps should call your backend.
Where are public release notes posted?▼
Public release notes and maintenance notices appear on the announcements page when an announcement is enabled by the operator.
What should a support ticket include?▼
Include account email, request time, model ID, endpoint path, error code, approximate prompt size and reproduction steps. Do not paste private API keys.
Start here
Choose the problem area
Model IDs and routing
Choose DeepSeek, Qwen, Kimi or another configured route for a specific workload.
Open guidanceBilling and wallet balance
Understand token pricing, promotional credit, insufficient balance and payment channels.
Open guidanceStreaming and SDK setup
Use the OpenAI SDK shape, the SmarToken base URL and streaming responses.
Open guidanceMigration from OpenRouter
Move China-model traffic with model ID mapping and a controlled test set.
Open guidanceProduction readiness
Review budgets, fallback routes, support information and operational checks.
Open guidanceDiagnostics
First checks before opening a ticket
A ticket is easier to resolve when the initial evidence already separates authentication, route, cost and latency issues.
| Issue | What to check |
|---|---|
| Authentication failed | Check Bearer token format, key status and whether the request is running server-side. |
| Model not found | Confirm the model ID exists in the public catalog and is spelled exactly as documented. |
| High cost | Compare prompt size, output length, retries and selected model price. |
| Slow response | Check streaming mode, model family, prompt size and upstream route availability. |
Common questions
Most support requests start with these answers
How do I get a SmarToken API key?
Sign in with Google, open the console and create a key in the API key area. Store the key server-side and rotate it immediately if it is exposed.
Which endpoint should my OpenAI-compatible client use?
Use https://thesmartoken.com/v1 as the base URL. Chat completion requests use the standard /chat/completions path under that base URL.
How do I choose a model?
Choose by workload. Start with DeepSeek for coding or cost-effective reasoning, Kimi for longer context and Qwen for multilingual product behavior, then verify with your own prompts.
What should I do after Error 429?
Reduce concurrency, add backoff and retry later. If it repeats, include timestamp, endpoint path, model ID and whether the request was streaming when you contact support.
What should I do when balance is insufficient?
Add balance, shorten prompts, lower max output length or switch to a lower-cost model. Review wallet history if the spend does not match expectations.
Can I put API keys in browser JavaScript?
No. Keep SmarToken keys in backend code, serverless functions, workers or secure automation environments. Browser apps should call your backend.
Where are public release notes posted?
Public release notes and maintenance notices appear on the announcements page when an announcement is enabled by the operator.
What should a support ticket include?
Include account email, request time, model ID, endpoint path, error code, approximate prompt size and reproduction steps. Do not paste private API keys.
Still need help?
Use support for account-specific billing, key or route issues. Public help pages cannot expose private account data.