HALODocs
Dashboard
Model Gateway

Gateway overview

Use provider-native APIs behind one HALO key.

HALO exposes separate provider-native entrypoints behind one project-scoped client key. Existing SDKs generally need only a base URL and credential change.

#Provider-native APIs

HALO does not flatten every provider into one synthetic request schema. Gemini keeps Gemini resources, Anthropic keeps Messages, and OpenAI-compatible providers keep Chat Completions.

#Base URLs

ProviderHALO base URLProtocol
Google Geminihttps://api.agihalo.comGemini Developer API
OpenAIhttps://api.agihalo.com/openai/v1Chat Completions
Anthropichttps://api.agihalo.com/claude/v1Messages
DeepSeekhttps://api.agihalo.com/deepseek/v1Chat Completions
Open-sourcehttps://api.agihalo.com/open-source/v1OpenAI-compatible

#Choose an integration

Gemini

Text streaming plus priced Imagen and Veo long-running generation.

OpenAI

Chat Completions with OpenAI client compatibility.

Anthropic

Claude Messages with Anthropic headers and payloads.

Open-source

Listed families routed to validated custom inference endpoints.

#Authentication & billing

HALO authenticates the client key, enforces the account usage limit, resolves an eligible upstream, and records completed usage. If prepaid balance is unavailable, the request may enter the x402 flow before dispatch.