Support docs being productized
Gateway Status And Support
Public boundaries for model availability, error codes, rate limits, status vocabulary, and support-triage evidence.
Current public promise
| Topic | Can promise now | Still being completed |
|---|---|---|
| Models | Gateway exposes model calls through an OpenAI-compatible API | Public model list, aliases, context windows, and availability notes |
| Errors | Errors should include stable code, message, and request id | Common auth, model, quota, rate-limit, and provider degradation tables |
| Rate limits | Quota and rate limits are governed by Gateway | Visible quota and reset windows per key, team, and organization |
| Status | The API entry is live | Public status page, provider health, degradation semantics, and maintenance notices |
Error triage
| Error type | Check first | Support evidence |
|---|---|---|
| Authentication failed | Authorization header, key ownership, whether a TokenDance ID token was used by mistake | Status code, error code, request id, request time |
| Model not found | model name, alias, and whether the key can access that model | Model name, request id, SDK configuration |
| Quota or rate limit | key owner, quota, concurrency, reset window | Status code, error code, time window, client type |
| Provider degradation | model name, retry policy, whether a degradation notice exists | request id, time, redacted task description |
| Invalid request schema | messages, tools, stream, payload schema | SDK version and redacted payload shape |
What to provide for support
- Request time, HTTP status code, error code, request id, and model name.
- SDK name and version, and whether the base URL is https://api.vectorcontrol.tech/v1.
- Client type: AgentHub, TokenDanceCode, CI, backend service, or local script.
- A redacted task description. Do not provide real keys, complete prompts, private files, or full provider responses.
Status page direction
The public status and model availability surfaces are still being productized. Until a formal status page is live, public docs should promise only the API entry, credential boundary, placeholder SDK examples, and support-evidence requirements. Do not claim enterprise SLA, full model catalogs, or automatic degradation guarantees.
TokenDance ID boundary
- TokenDance ID login proves a human or organization identity; it is not model API authentication.
- TokenDance API keys call Gateway model APIs; they do not log users into TokenDance ID.
- Admin UX, key self-service, quota/usage views, and status pages are still being completed, so public docs should not imply a complete self-service backend is already released.