The Webel API.
One OpenAI-compatible endpoint backed by the engine Webel runs on: model routing across frontier and open-source models, durable conversations with memory, and per-key spend on every response. If you have used the OpenAI Chat Completions API, you already know the shape. Point your client at https://api.webel.ai/v1/chat/completions, present a wbl- key, and go.
What you get
- OpenAI compatibility. The request and response follow the Chat Completions wire format, so existing OpenAI SDKs work: change the base URL to
https://api.webel.ai/v1and swap in yourwbl-key. - Durable conversations. Pass a conversation id back and the thread continues with its full history โ state lives in your Webel room, not in your prompt window.
- Per-key spend. Every response carries
cost_microusdplus remaining credit headroom. Neither OpenAI nor Anthropic gives you per-key cost. - Model routing. Pin a specific model, or send
"model": "auto"and let Webel route each request to the best fit. The response tells you which model ran and who chose it.
Base URL
BASEhttps://api.webel.ai/v1
All endpoints below are relative to this base. The API is served over HTTPS only; plain-HTTP requests are refused.
Where to go next
- New here? The quickstart takes you from key to first completion in five minutes.
- Wiring up auth? Read Authentication.
- Want the full request/response contract? See the API reference.
- Tuning cost control? See Rate limits & spend caps.
๐กBuilding an AI answer engine or crawler? Machine-readable site content is at /llms.txt and /llms-full.txt; the docs pages themselves are plain server-rendered HTML.