30-second check

Provider Node

Provider Node is a component that connects capacity to Wokey’s hosted cloud routing network; it is not a standalone self-hosted API gateway. Connect unused AI subscriptions so users save money and providers earn.

code

Open Source Project

Provider Node is fully open source, so its behavior is auditable. Read the code on GitHub, build it yourself, verify a release, or report issues.

open_in_newView source on GitHub

The whole flow: install the node app on your machine → bind it to your Wokey account → authorize your subscription inside the node. Once the node is online, Wokey routes other people’s calls to your subscription and you earn per call.

1Install the node2Bind to account3Authorize subscription
checklist

Before you start

30-second check
workspace_premium

A supported subscription

Claude, ChatGPT (OpenAI), Zhipu, Kimi, and other AI subscription plans.

computer

A computer or server (VPS)

macOS / Windows / Linux all work, and it does not need to stay on.

1

Install the node

Use the one-line installer. macOS / Linux use bash, Windows uses PowerShell; Docker installation is also supported. No prerequisites to set up: if Node.js is missing, the installer installs it for you (winget or the official package on Windows, Homebrew or the official package on macOS, the official prebuilt binaries on Linux).

curl -fsSL https://github.com/focuxdot/wokey-provider-node/releases/latest/download/install.sh | bash
check_circle

Success looks like:After installation the local node management page opens automatically at 127.0.0.1:16888. Seeing it means you are set.

chevron_rightFallback packages (all platforms)
2

Bind to account

Link this node to your Wokey account so earnings are credited to you.

  1. 1On the node management page 127.0.0.1:16888, click “One-click bind”.
  2. 2You are taken to the Wokey Provider page; sign in to your provider account and confirm.
  3. 3The page returns to the node management page automatically — binding done.
check_circle

Success looks like:You can open the node management page, and the node shows as online on the Provider page /provider.

chevron_rightRemote / headless (CLI bind)
Remote / headless (CLI bind)
wokey-node add
wokey-node bind --value bind_...
wokey-node list
3

Authorize subscription

Once the node is online, authorize the subscription you want to share right from the Provider page /provider → “Add credential” — the authorization runs through your bound node’s egress (you can also do it in the local node console).

  1. 1On /provider click “Add credential”, then pick “OAuth” (Claude / ChatGPT / Grok subscription account) or “API Key”.
  2. 2Claude: sign in and paste the returned authorization code back; ChatGPT: enter the device code on its verification page; Grok: click “Open verification” once and the page generates the device code in the background, then opens Grok with the code prefilled.
  3. 3The exit node is auto-matched to your current network, so you usually don’t pick one; with multiple nodes you can click “Change”.
Security model: ① Provider Node is fully open source, so its behavior is auditable. ② The node on your machine acts only as a network egress, and by default may only reach model vendors’ official domains (the allowlist lives in the repo, official-exit-vendors.ts) — it reaches nothing else.
check_circle

Success looks like:The credential appears as active on the Provider page.

chevron_rightAPI key / remote import
API key / remote import
wokey-node import
wokey-node paste token --vendor openai --file ./token.json
rocket_launch

After it runs

bolt

Online = earnings

Calls are routed to your account and earn only while the node is online.

schedule

No need to stay on

You don’t have to stay online — come online whenever you like, and going offline never affects your account; you simply earn nothing for that idle time. Calls cluster around daytime working hours, so keeping it on during your normal computer use is usually enough.

pause_circle

To pause

Turn off the supply switch on the node management page, or just quit the node app.

Earnings and withdrawals live in the console.

paymentsOpen Provider console
help

Troubleshooting

errorHow do I open the node management page when the node is installed on a VPS?

Run the macOS / Linux install command above on the VPS, then use wokey-node status to confirm the node is running. On your local computer, run ssh -i /path/to/your-key.pem -o IdentitiesOnly=yes -N -L 16888:127.0.0.1:16888 ubuntu@SERVER_IP, keep the SSH window open, and visit http://127.0.0.1:16888. Do not expose the VPS port 16888 to the public internet.

errorDo I have to choose between Claude, ChatGPT/OpenAI, and Grok? Can one node add multiple account authorizations?

No. One node can authorize multiple Claude / ChatGPT / Grok accounts, and one Wokey Provider account can bind multiple nodes. To add another account, click “Add credential” on the Provider page /provider and repeat the authorization flow.

errorCan a node bind to someone else’s Wokey account? How many nodes can one account bind?

Yes. Nodes are decoupled from the installer’s Wokey login; the one-time binding code decides which Provider ID the node joins. Wokey does not limit the number of nodes under one Provider account. For shared setups, a friend can run Provider Node and bind it with a code generated from your Provider page.

errorHow do I bring an offline node back online?

Run wokey-node restart on the computer or server where the node is installed. To confirm it recovered, run wokey-node status afterward. The status → restart → status sequence is only for troubleshooting; a normal restart does not require all three commands.

errorCalls failing / credential errors?

Check whether the credential expired and re-authorize on the node if so; see wokey-node logs.

errorHow do I update or uninstall Provider Node?

Run commands on the node machine as the same operating-system user that runs Provider Node. Use wokey-node update on macOS, Linux, or Windows. On macOS, wokey-node uninstall removes the runtime and --purge also removes local data. On Linux or Windows, run wokey-node uninstall-service before removing the package or runtime directory. For Docker, update with docker compose pull && docker compose up -d; docker compose down keeps data, while docker compose down -v removes the node binding and local authorization data.

menu_bookMore questions

Contact support

terminal

CLI reference

Remote / advanced

After installation, use wokey-node to manage the local node. Running it without arguments opens the interactive menu; on remote servers prefer the CLI.

Bind

Bind
wokey-node add
wokey-node bind --value bind_...
wokey-node list

Status

Status
wokey-node
wokey-node status

Credentials

Credentials
wokey-node import
wokey-node paste token --vendor openai --file ./token.json

Update and maintenance

Update and maintenance
wokey-node version
wokey-node update
wokey-node restart
wokey-node status
wokey-node logs

Uninstall (macOS)

Uninstall (macOS)
wokey-node uninstall
wokey-node uninstall --purge

Remove service (Linux / Windows)

Remove service (Linux / Windows)
wokey-node uninstall-service

Docker update and uninstall

Docker update and uninstall
docker compose pull
docker compose up -d
docker compose down
# Purge local data
docker compose down -v