HTTP(S) proxy
Customer traffic enters the gateway as an HTTP proxy. Username carries targeting.
Demo data. Not a live network, credential, or invoice.
Customer protocols and the supply-node contract. Implementation lives in services later. The shapes are reserved now.
Customer traffic enters the gateway as an HTTP proxy. Username carries targeting.
Same credential, SOCKS5 listener. Port differs by product class in the demo builder.
POST a URL to the unlocker. It selects an exit, retries, and returns the body.
Tuxly, HiveBand, SilentPipe, and NodePayout SDK call the registry. Contract only, in this repo.
POST /v1/nodes/register
Authorization: Bearer <node_token>
{
"supply": "hiveband",
"node_id": "node_demo_01",
"network_type": "residential",
"country": "us",
"city": "New York",
"asn": "AS7922"
}Full contract: docs/integrations/node-registration.md in the monorepo. This block is a teaser, not a live endpoint.