Provider scanner
Integration Readiness
See what’s configured and where keyless connections may be possible.
Detected Providers
Matched from known variable names in this runtime.
No providers detected
No recognized provider variable names were found. Add a provider configuration, then scan again.
Preview configured exampleManaged-access options
Choose a Path to AI Access
Compare 2 managed approaches before adding provider configuration.
Start with Vercel AI Gateway for the shortest path on Vercel.
Choose Azure Foundry instead when Azure identity, governance, or private networking is a primary requirement.
| Factor | ▲Vercel AI Gateway | AAzure Foundry |
|---|---|---|
| Setup | One gateway endpoint with model routing designed to fit Vercel and the AI SDK. | Create a Foundry project, choose a deployment, and connect it to your Azure application. |
| Credentials | Vercel deployments can use OIDC-based access; other runtimes can use a gateway credential. | Microsoft Entra ID and Azure RBAC support identity-based access; API keys are also available. |
| Operations | Centralized usage, spend controls, fallbacks, and provider switching through one gateway. | Azure-native governance, monitoring, networking, and controls across model deployments. |
| Best fit | Teams shipping on Vercel that want a fast path and flexibility across model providers. | Teams standardized on Azure that need enterprise identity, policy, and network controls. |
Research-based guidance, not a configuration check. Envscope has not verified your account, permissions, region, model availability, or credentials. Compare the fit, configure access in your chosen provider, then scan variable names again—never enter secret values here.
How this scan works: Envscope compares environment variable names against a local provider catalog. It never reads values, sends network requests, or writes scan data to logs.