Keeper is the supply side of HALO's model gateway. A provider can register validated inference, pass identity checks, monitor health, and request settlement for eligible earnings.
#Provider types
| Type | Current availability |
|---|---|
| Custom endpoint | OpenAI-compatible text inference with production validation |
| Hosted credential | Configuration may be preserved, but seller traffic and earnings are rollout-gated |
#Custom endpoint contract
- Public HTTPS base URL with no credentials, query, or fragment.
- Relative chat path ending in
/chat/completions; HALO derives the matching models path. - Choose Bearer or
X-API-Keyauthentication for both discovery and chat. - Return uncompressed JSON. Only same-origin 307/308 redirects are followed, at most two hops.
{
"data": [
{ "id": "qwen/qwen3.6-35b-a3b" }
]
}{
"model": "qwen/qwen3.6-35b-a3b",
"messages": [
{ "role": "user", "content": "Reply with the single word OK." }
],
"max_tokens": 16,
"stream": false
}#Validation & health
Registration performs discovery and bounded baseline calls. Optional logprob probes report capability but do not affect billing. Continuing health checks run in bounded batches; repeated recorded failures can put a key on watch and later disable it.
#Metering
Custom text usage uses deterministic HALO text units from the canonical request and visible assistant response. Seller-reported usage, hidden reasoning, cache claims, and model-native tokenizers do not determine the customer charge.
#Payouts
- Complete individual KYC and save a Base USDC receive wallet.
- The UI shows the current fee split before activation.
- One active payout request can allocate available cash-funded earnings.
- Pending requests may be cancelled and expire after seven days.
- Processing and transfer are manually reviewed; timing is not guaranteed.