Product documentation
Getting started
Choose the correct OpenToken path and use only capabilities that are currently released.
Release status
ReleasedOutcome
Create an account context, understand the three product paths, and identify the next released action.
Prerequisites
- A supported browser
- A Google account for hosted account sign-in
Current path
- Choose whether you want to contribute capacity, use the Network API, or use owned models privately.
- Review the status and trust boundary for that path before authenticating.
- Sign in only when a released account or device-approval step requires it.
- Do not treat Development or Planned material as an available product workflow.
Authoritative success state
The account Overview loads authoritative device, Network Sharing policy, and API-key metadata without inferring unavailable state.
Common failures and recovery
- If sign-in fails, retry from the localized sign-in action and keep the original locale path.
- If account state is unavailable, retry later; the failed read changes no account state.
Security and privacy boundary
Signing in exposes account identity to the hosted control plane. It does not enable Network Sharing or upload model weights.