Product documentation
Contribute model capacity
Understand the contribution path without implying that unreleased validation and Credit flows are available.
Release status
DevelopmentOutcome
Connect a device, serve compatible local models, opt in to Network Sharing, and contribute validated work when the production path is released.
Prerequisites
- A hosted account
- A released CLI channel
- A compatible loopback model runtime
- Explicit consent to the Shared Inference boundary
Current path
- The released website can sign in an account and approve a one-time CLI device request.
- CLI installation, local discovery, and provider startup instructions will be published only with the validated release channel.
- The web account will remain authoritative for enabling Network Sharing per device; the CLI cannot enable it independently.
- Validation, eligibility, contribution availability, and Credit state will appear only when their authoritative APIs are released.
Authoritative success state
A complete production success state requires released device presence, sharing policy, provider availability, validation, and settlement data. That complete state is not yet available.
Common failures and recovery
- Keep Network Sharing off for workloads unsuitable for contributor-operated infrastructure.
- A missing unreleased state is unavailable, not failed or zero.
Security and privacy boundary
The contributor processes plaintext application content. OpenToken shares bounded inference capacity, never model weights, local API keys, or machine access.