Use It From Anywhere
Connect Termux, OpenHands, an editor, a mobile app, an SDK or a workflow runner to the ZYRAXON line. One base URL, one model id, no adapter.
The ZYRAXON provider speaks the OpenAI chat-completions dialect, so the integration is the same everywhere: point a client at https://zyraxonai.lovable.app/api/public/zyraxon/v1, pick a model id, and build. There is nothing to install on our side, no provider key to buy, and no upstream vendor name in any response.
https://zyraxonai.lovable.app/api/public/zyraxon/v1 · Model: zyraxon-codex · API key: zyraxon (any non-empty string). Read https://zyraxonai.lovable.app/api/public/zyraxon/v1/models for the current model list and live limits.The snippets and the connection fields on this page are read from the same catalogue the /providers page and GET /v1/integrations serve, so what you read here is exactly what the endpoint hands out.
Pick your client
| If you use | Go to | What you do |
|---|---|---|
| Termux on Android | Termux on Android | Run one setup script, then use the zyraxon command. |
| Kali Linux or NetHunter | Kali Linux and NetHunter | Install curl and jq, then use the zyraxon-ask script. |
| OpenHands | OpenHands | Fill four fields in the custom-provider form and save. |
| Cursor, Continue, Cline, Zed | Editors and CLI Agents | Set an OpenAI-compatible base URL. |
| A mobile app you are building | Mobile apps | Call the HTTP endpoint from the platform's own client. |
| cURL, the OpenAI SDK, LangChain | SDKs and Frameworks | Change the base URL and keep your code. |
| Go, Rust, PHP, Java, .NET | Languages and Runtimes | Use the standard library's HTTP client. |
| Discord, Slack, Home Assistant | Bots and Home Automation | One HTTP call per message. |
| A Python, PowerShell or Bash shell | Your Shell | Download one client and import or source it. |
| n8n, Make, Zapier, Postman | Automation and HTTP Clients | Use an HTTP request node. |
GET https://zyraxonai.lovable.app/api/public/zyraxon/v1/integrations returns this whole page as JSON — the base URL, the key rule, the model list location and a working snippet per platform. Point an installer or an agent at it instead of copying code by hand.The rules of use
These apply to every client above. They are the same rules the endpoint publishes from GET /v1/provider, so a client can read them at runtime rather than trusting a page.
One base URL, ten models
Point your client at https://zyraxonai.lovable.app/api/public/zyraxon/v1 and use a ZYRAXON model id. There is no second endpoint to discover and no upstream vendor to name.
Send any non-empty key
The OpenAI SDKs refuse to build a client without an apiKey. Until the operator sets ZYRAXON_PROVIDER_KEY, any non-empty string works. When a key is configured, send it as Authorization: Bearer <key>.
Read the model list, do not hardcode limits
Context windows, output caps and modality support move with the serving pool. Fetch https://zyraxonai.lovable.app/api/public/zyraxon/v1/models at startup instead of baking in numbers.
Media is capped per request
At most 12 media parts and a body under 40 MB. Base64 adds about a third, so compress and slice video and transcode long audio to low-bitrate mono before sending.
You run your own tools
Define tools in the OpenAI wire shape and the model returns real tool calls. The provider never executes them — your code performs the action and sends the result back.
A rotated model is healthy, not down
Each ZYRAXON model is bound to a preferred upstream with the rest of the pool behind it. status: "rotated" means a sibling is covering. You keep calling the same name.
Retry the right codes
Retry 429, 502 and 503 with backoff and jitter, and honour Retry-After. Do not retry 400, 401 or 413 — fix the request instead. X-ZYRAXON-Capacity tells you whether the primary tier or the spill pool answered.
Capacity degrades, it does not crash
Primary lanes serve on ZYRAXON's own budget, overflow spills to the OpenCode Zen free pool, then queues, then sheds with 503 rather than blocking other callers.
Prove the connection in one call
curl -s https://zyraxonai.lovable.app/api/public/zyraxon/v1/chat/completions \
-H "Content-Type: application/json" \
-H "Authorization: Bearer zyraxon" \
-d '{"model":"zyraxon-codex","messages":[{"role":"user","content":"ping"}]}' \
| jq -r '.choices[0].message.content'If that prints a reply, the base URL and key are correct and every client below will work. If it fails, read the type field in the error body before changing anything else.