Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

createAI: Azure OpenAI v1 URLs (the @ai-sdk/azure default) are not routed

Open Beginner friendly
#2,629 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript

Research direction

Start in packages/agents/src/models/core/gateway-providers.ts and read azureEndpoint alongside the Azure provider URL mapping described in cloudflare/ai#604. Check how /openai/v1/responses should map and how other v1 paths are handled. Done means default @ai-sdk/azure v1 URLs route as intended, unmatched paths remain unmatched, and the error gives the useDeploymentBasedUrls: true guidance when appropriate.

Written by the indexing model from the issue text.

Description

@ai-sdk/azure builds v1 URLs by default (useDeploymentBasedUrls: false), e.g. https://<resource>.openai.azure.com/openai/v1/responses. createAI only maps the deployment form (/openai/deployments/<d>/...), so a default Azure model can't be routed:

const azure = createAzure({ resourceName: "acme" });
const ai = createAI({ binding: env.AI, id: "gw" });
await generateText({ model: ai(azure("gpt-5")), prompt });
// TypeError: AI Gateway has no provider for acme.openai.azure.com. ... the supported providers are ..., azure-openai, ...

azureEndpoint in packages/agents/src/models/core/gateway-providers.ts returns undefined for anything but the deployment path, and the error then claims the host itself is unsupported while listing azure-openai. cloudflare/ai#604 maps /openai/v1/responses to the gateway's <resource>/openai/responses endpoint and leaves other v1 paths unmatched. At minimum the error should say to use useDeploymentBasedUrls: true.

From cloudflare/ai#604.

Dominant language
TypeScript
Stars
5.9k
Forks
788
Avg merge
21h 59m
Merged PRs (30d)
175

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudflare/agents

All issues in cloudflare/agents

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.