Azure OpenAI speaks the OpenAI API shape with two GoModel-handled differences: anDocumentation Index
Fetch the complete documentation index at: https://gomodel.enterpilot.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
api-key header instead of Authorization: Bearer, and a required
api-version query parameter on every request.
Configure
config.yaml:
Run GoModel
Verify
GET /v1/models returns the deployments the Azure resource exposes with
owned_by: "azure". Streaming, Responses, embeddings, and batches all work the
same way; batch results route through the /openai/batches resource path.
Multiple deployments
Each Azure deployment is its own endpoint. Register them as separate providers with suffixed env vars:azure-gpt5 and azure-embed. To expose every deployment under
one resource through a single provider, point AZURE_BASE_URL at the resource
root (no /deployments/...) and use aliases or AZURE_MODELS to advertise
specific deployment names.
Notes
- GoModel accepts the deployment-scoped URL the portal hands you. For
account-wide operations (model listing, batches) GoModel strips the
/openai/deployments/<deployment>suffix automatically, so oneAZURE_BASE_URLcovers both chat and resource-level calls. AZURE_API_VERSIONonly needs to be set explicitly when you need a different stable or preview version — for example a newer Responses API surface.
Troubleshooting
401 Unauthorized/403—AZURE_API_KEYdoes not match the resource hosting the deployment, or the deployment name in the URL is wrong.Resource not found/DeploymentNotFound— the model in the request body must be the deployment name, not the underlying base model.unsupported api version— bumpAZURE_API_VERSIONto a version the feature you’re calling supports. Newer Responses API features require recent preview versions.