Public entry
TokenDance Documentation
Public product map, reading order, and boundary notes for TokenDance.
Start here
TokenDance is a family of AI-native engineering infrastructure products. The organization site owns public positioning, docs entry points, and identity boundaries; product repositories own implementation details.
- For multi-agent collaboration and the desktop workbench, read AgentHub.
- For how products fit together, read Ecosystem Architecture.
- For model API access, read TokenDance Gateway, Gateway Access And Keys, and Gateway Status And Support; keep API keys separate from TokenDance ID login.
- For current maturity and public promises, read Product Status.
- For CLI/agent experiments, read TokenDanceCode.
- For unified login, read Identity and Login.
- For public release, SEO, or i18n changes, read Release Evidence and Public Governance.
Product map
| Product | Audience | Use today | Primary entry | Maturity |
|---|---|---|---|---|
| AgentHub | Engineering teams and individual developers | Read the site, docs, and Desktop-first product direction | hub.vectorcontrol.tech | Active development, public site live |
| TokenDance Gateway | Agents, CLIs, and apps that need unified model APIs | Call OpenAI-compatible APIs with a TokenDance API key and read access/status/support boundaries | /docs/gateway | API live, public product experience in progress |
| TokenDance ID | Apps integrating TokenDance login | Authenticate with OIDC/PKCE | /docs/identity | Identity authority, admin UX in progress |
| TokenDanceCode | Developers exploring CLI agent UX | Use the GitHub repo as an experimental project | /docs/tokendance-code | Experimental |
| TokenDanceChat | Teams validating realtime agent interaction | Try chat and event-flow demos | chat.vectorcontrol.tech | Demo/proving ground |
Public documentation boundary
Public docs describe product capabilities, integration paths, and security boundaries only. Production host paths, backup directories, rollback commands, upstream provider secrets, real admin keys, and private logs belong in the server workspace or operator secret store.