Provider Node/Use a proxy IP

Add a Node with a Proxy IP

If you already have a proxy server, you don't need to install Provider Node: enter the proxy URL, and once it passes verification it becomes your node. Then authorize subscriptions on the web.

No proxy server, or need Jimeng? Install Provider Node instead: Provider Node guide →

On this pageexpand_more

Requirementslink

  • A proxy server (a VPS or a proxy service) with a public IP or public hostname, and a port reachable from the internet. localhost and private network addresses are not allowed.
  • The proxy can reach port 443 on api.wokey.ai and on the model vendors’ official domains.
  • The proxy’s exit region must be supported by the model vendor. For example, an exit in mainland China cannot authorize Claude or ChatGPT subscriptions.
  • The proxy must stay running. You don’t need to install Provider Node or keep your own computer on.

Proxy URL formatslink

ProtocolExample URLNotes
HTTP CONNECThttp://user:[email protected]:8080Default port 80. The proxy username and password reach the proxy server in clear text.
HTTPS proxyhttps://user:[email protected]:8443Default port 443. Connects to the proxy server over TLS first, which protects the proxy credentials. The certificate must come from a public CA; self-signed certificates fail verification.
SOCKS5hsocks5h://user:[email protected]:1080Default port 1080; the proxy resolves domain names. socks5:// is not supported; write socks5h:// instead.
  • Put the credentials in the URL as user:password@. URL-encode special characters, for example @ as %40.
  • The URL cannot contain a path, query string, or #.
  • Each account can add up to 100 proxy nodes.

Add the nodelink

  1. 1

    Open the Provider page

    Go to the Provider page. With no nodes yet, click “Use a proxy IP”; if you already have nodes, click “Add proxy node” in the Shared nodes section.

  2. 2

    Accept the privacy terms

    The first time, the page asks you to accept the Provider privacy terms. Accept them to continue.

  3. 3

    Enter the proxy

    Choose the protocol and enter the proxy URL. The node name is optional, up to 40 characters.

  4. 4

    Verify and save

    Click “Verify and save”. Within 10 seconds the platform connects to api.wokey.ai:443 through the proxy and saves it once connected. When your first node passes verification, your account gets the Provider role.

check_circle

Success: The node appears in the Shared nodes list as online, typed SOCKS5h, HTTPS CONNECT, or HTTP CONNECT. The list shows only the IP and port, never the credentials.

Authorize subscriptionslink

A proxy node has no local page, so subscriptions are authorized on the Wokey website.

  1. 1

    Open the authorization page

    On the Provider page, click “Add credential”, choose “OAuth”, and open “Add authorized credential”.

  2. 2

    Pick the proxy node

    With several nodes, the platform matches one automatically. To authorize through this proxy, click “Change” in the Exit node bar and select it.

  3. 3

    Sign in

    Sign in to the subscription as the page instructs. The first time a vendor is authorized through a proxy, the platform checks that the proxy can reach that vendor’s official address. The check only opens an encrypted connection; it sends no request and no credential.

Works through a proxy
Web authorization for Claude, ChatGPT (Codex), Grok, and Kimi, plus API keys for every supported vendor.
Not through a proxy
Jimeng needs an installed Provider Node; proxy nodes do not appear in its node list.

Running and managementlink

Online status
Every 30 seconds the platform checks the connection through the proxy. The node shows as online when a check has passed in the last 3 minutes. After a connection or login failure the node stops taking requests for 30 seconds.
Concurrency and earnings
Each proxy node carries up to 32 connections at once. Earnings work as for Provider Node: you are paid for successful calls.
Pause and delete
Pausing closes every connection through the proxy. Deleting the node moves its bound accounts to a backup node; with no backup node, those accounts stay unbound.
Change the proxy URL
The page can’t edit the URL yet. To switch, add a new proxy node, then delete the old one.

Securitylink

  • The proxy URL and credentials are stored encrypted; the page shows only the IP and port.
  • Through the proxy, the platform connects only to port 443 on Wokey and on the model vendors’ official domains.
  • The proxy sees only the destination address and encrypted traffic, not the requests sent to model vendors.
  • With http:// or socks5h://, the proxy credentials reach the proxy server in clear text; use an https:// proxy to protect them.

Common errorslink

When adding a node or authorizing fails, the page shows one of the messages below. Follow the message to fix it.

The proxy rejected the username or password. Check the credentials and try again.

proxy_auth_failed

The proxy server could not be reached. Check the IP, port, and VPS firewall.

proxy_connect_failed

Connecting to the proxy timed out. Make sure the port is open and the VPS can reach the platform.

proxy_connect_timeout

The proxy must use a public IP or hostname; localhost and private network addresses are not allowed.

proxy_address_not_public

The selected protocol does not match the proxy URL scheme. Check both values.

proxy_protocol_mismatch

The proxy protocol handshake failed. Check the protocol type and proxy configuration.

proxy_handshake_failed

A secure connection to the HTTPS proxy could not be established. Check the proxy certificate and address.

proxy_tls_failed

The proxy could not reach the target (platform verification address or model vendor). Check the VPS outbound network, firewall, and allowlist.

proxy_target_connect_failed

The proxy credentials are malformed. Check the username, password, and URL encoding.

invalid_proxy_auth

You have reached the proxy node limit. Remove an unused node before adding another.

proxy_node_limit

Authorization says the vendor does not support the exit node’s region

The proxy exits in a region the model vendor does not support (for example mainland China). Use a proxy in a supported region and authorize again.