https://api.firzaw.space/v1$FIRZAW_API_KEYUse a key issued for this relay. Never paste a production key into a browser, public issue, or client-side code.
PUBLIC API · OPENAI-COMPATIBLE
A clean, authenticated gateway for coding clients, agents, and production workflows. Point an OpenAI-compatible client at the base URL, choose a model from the live catalog, and keep your prompts in control.
Your key stays in your client. The relay never logs prompt or response content.
POST https://api.firzaw.space/v1/chat/completionsAuthorization: Bearer $FIRZAW_API_KEY{"model": "cx/gpt-5.6-sol","messages": [{ "role": "user" }]}01 / QUICKSTART
Use the base URL below, set your key as an environment variable, and start with a model that is live right now. All examples use placeholders only.
https://api.firzaw.space/v1$FIRZAW_API_KEYUse a key issued for this relay. Never paste a production key into a browser, public issue, or client-side code.
The catalog is read from the same gateway used for completions. It is a route list, not a promise that every provider is available for every request.
Inspect model metadata →02 / MODEL EXPLORER
03 / REFERENCE
These are the stable public routes. The relay forwards compatible requests, adds a small set of routing conveniences, and keeps the response close to the upstream contract.
Discover model IDs and the sanitized capability metadata returned by the gateway.
curl https://api.firzaw.space/v1/modelsOpenAI Chat Completions shape, including streaming responses when stream: true.
messages · tools · temperature · streamResponses shape for clients that prefer the newer OpenAI request envelope.
input · instructions · reasoningAnthropic Messages bridge for compatible clients. Availability depends on the selected route and active provider.
messages · system · stream04 / TRANSPARENCY
↗Status is liveThe page checks a sanitized local health endpoint and the current model catalog.
⌁Errors are usefulUnauthorized requests receive a clear 401; invalid JSON and upstream failures are not disguised as successful empty responses.
◌No prompt telemetryRequest events contain routing metadata only. Prompts, responses, hidden reasoning, and credentials are excluded.