GET /health
Check whether the public gateway is reachable without sending a prompt or credential.
Point an OpenAI-compatible client at HAL, inspect anonymous health, or run the gateway on your own machine. Protected model, chat, and peer routes require an operator-issued bearer token; this page never asks you to paste one into the browser.
Discovery is not permission. The API reports health openly, while protected capability routes require authentication and keep provider credentials server-side.
GET /healthCheck whether the public gateway is reachable without sending a prompt or credential.
GET /v1/modelsList HAL virtual model modes and current routing surface.
POST /v1/chat/completionsUse the familiar message format through HAL policy and routing.
GET /v1/peersInspect HAL identity and enabled peer nodes without exposing their secrets.
curl -fsS https://api.halsupreme.com/healthA healthy response proves the edge answered. It does not prove every provider or model route is ready.
A spare GPU can help HAL only through a bounded, authenticated provider connection. Registry visibility is not routing permission, and a listed node never gains access to the owner’s computer, files, WorkGraph, or credentials.
Share the HTTPS base URL, allowed model IDs, capability and privacy classes, expected availability, rate limit, interruption behavior, and a contact for revocation. Send the bearer credential only through the operator’s approved private channel.
The normal sequence is candidate → probed → owner reviewed → admitted. A peer may remain useful for discovery without ever becoming routeable.
Community and marketplace nodes receive public, synthetic, or separately approved inputs only. Sensitive repository, identity, payment, medical, and unpublished media data stay off the route.
Most visitors should use the browser chat. Developers can self-host. Peer access is an intentional operator relationship, not a public-token scavenger hunt.
No setup. Choose a mode and start with the composer.
Own the gateway, policy, provider configuration, and local credentials.
Review the protocol and discuss a bounded, authenticated connection with the community.