Share your AI. Power the network.
Run the TokenSwitch client on a Linux server, open a share, and monetize idle Claude, Codex & Gemini access — or buy routed usage on the markets.
Providers need a Linux host (amd64 or arm64).
One-line install on Linux (amd64 / arm64).
Used for your provider node Web UI login. Never sent to this website.
curl -SsL https://jptokenswitch.cc/install-client.sh | bash -s https://jptokenswitch.cc <Email> <Password>How the network works
Providers run the client on a server they control. Routers route traffic. Markets connect consumers — upstream keys stay on your provider node.
- 1
Share. Install the client, register to a router, and open an outbound SSH tunnel.
- 2
Route. Public requests hit a subdomain on the router and proxy back through the tunnel.
- 3
Earn. List on Token Market (usage) or Share Market (period) and collect revenue.
Four pieces, one network
TokenSwitch is the ecosystem brand. The open-source client runtime is cc-switch-server.
Provider revenue flow
On Token Market, $1.00 of usage yields ~$0.85 net to the provider after platform fees.
Market 10% · Router 5% · fully ledgered
Trust center
How TokenSwitch protects providers, consumers, and platform boundaries.
Provider
- Upstream API keys stay on your provider node — never sent to markets or this website.
- Shares sync metadata only — router stores subdomain & ACL, not secrets.
- Token Market revenue is ledgered; withdrawals are auditable.
Consumer
- Token Market API keys are market-issued, separate from provider keys.
- Usage is metered and visible in your dashboard.
- Share Market: access granted only after the owner confirms payment.
Platform boundary
- Share Market does not hold funds, verify transfers, or guarantee refunds.
- Router is the trust boundary for routing and ACL — not a payment processor.
- Token Market uses double-entry ledger; admin cannot silently edit balances.
Live network
Click a region node to explore the network.