Status notes
Product Status
Current maturity, public entry points, and overclaim boundaries for TokenDance products.
How to read status words
| Status | Meaning | Copy rule |
|---|---|---|
| Live | A public entry point or callable API exists and has current release evidence | Document the entry, boundary, and minimal usage path |
| Active development | The product direction is clear and capabilities are shipping, but details may change quickly | Say what works now and where to read the latest docs |
| Experimental | Used to validate interaction, architecture, or product ideas | Keep promises low; do not claim enterprise SLA or stable compatibility |
| Being productized | The underlying capability exists, while public self-service, docs, or governance are still being completed | Name in-progress areas instead of writing roadmap work as done |
Current product matrix
| Product | Current status | Public entry | Can promise | In progress |
|---|---|---|---|---|
| AgentHub | Active development | https://hub.vectorcontrol.tech | Site, docs, Desktop-first product direction, and Hub-backed Web boundaries | Desktop/Web interactions, docs depth, and design-system convergence |
| TokenDance Gateway | API live, being productized | https://api.vectorcontrol.tech/v1 | OpenAI-compatible API entry, TokenDance API key boundary, and placeholder-safe SDK examples | Self-service keys, quota/usage, model list, error codes, and status vocabulary |
| TokenDance ID | Unified identity | https://id.vectorcontrol.tech | Identity authority for TokenDance products and OIDC/PKCE integration direction | Admin UX, provider UX, and organization-level self-service |
| TokenDanceCode | Experimental | https://github.com/TokenDanceLab/TokenDanceCode | CLI-agent experiment positioning, source entry; Anthropic-compatible auto enablement; OpenAI provider mapping exists | CLI auto-selection for OpenAI/Gateway, tool boundaries, and docs |
| TokenDanceChat | Demo/proving ground | https://chat.vectorcontrol.tech | Realtime chat and agent interaction validation entry | AgentHub collaboration events, webhooks, and demo docs |
Release judgment
- Public pages should promise only entries that are live and recently verified. Unverified capabilities should be written as in progress.
- Product docs may show placeholder commands and environment variable names, but not real keys, user data, or internal model names.
- Gateway wording must keep TokenDance API keys separate from TokenDance ID sessions.
- Experimental projects can explain motivation, trial paths, and feedback direction, but not stable support, enterprise SLA, or compatibility commitments.
Reader next steps
- To use a multi-agent workbench, read AgentHub docs for Desktop, Web Workbench, and Run Lifecycle.
- To call model APIs, read Gateway docs, Gateway Access And Keys, and Gateway Status And Support for base URL, SDK examples, key management, errors, and support evidence.
- To integrate login, read Identity and Login for OIDC, TokenDance ID, and product-local authorization boundaries.
- To publish public-site changes, read Release Evidence before Governance so route, discovery, i18n, visual, and security proof stays complete.
- To try a CLI agent, use the TokenDanceCode repository and docs with experimental-project expectations.