VAREXIS-INDEX ยท Free evidence
AI provider routing and processing evidence
Eight operator decisions: provider preference versus restriction, key selection, regional scope, profile authorization and historical route evidence. Complete documentary reviews; no live verification or new executable support. Existing trial guides remain unchanged.
Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.
Complete exact-ID manifest · Full catalogue · Existing MCP coverage
Provider preference is not a provider restriction
Does Vercel AI Gateway provider order restrict every fallback to that list?
Vercel documents order as a preference: other eligible providers can still be tried. The only list removes providers outside it; if none of its providers can serve the model, the request fails. Review the effective restriction as well as the order.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Refuse to infer a provider allowlist from order alone; bind the actual request and effective team policy.
- A request with both order and an applicable only list can restrict the pool; an order setting is not inherently unrestricted when another control applies.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
An enabled allowlist still needs its contents reviewed
Does enabling Vercel AI Gateway Provider Allowlist immediately restrict the team to a previously reviewed provider subset?
The captured guide says initial enablement includes every currently available provider. Owners must remove unwanted providers; later new providers start disabled. A request-level only list must also satisfy the team list. Provider exclusion does not necessarily exclude a model offered by another allowed provider.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Refuse to treat the enabled flag or a model name as the reviewed processor set; retain the list contents and change time.
- An owner who explicitly removes other providers can establish a declared restricted set; the initial default is not permanent.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
A configured personal key does not prove which credential served
Does adding a Vercel AI Gateway BYOK key establish that each successful request used that key?
Vercel selects the oldest enabled dashboard key for a provider, with a separate ZDR eligibility rule. Standby keys are not the failure fallback: system credentials can be used instead. Request-scoped BYOK excludes dashboard credentials for that request but still permits system fallback.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Require the successful attempt and credential source; do not infer a customer account or agreement from key presence or a successful key test.
- A correlated successful attempt identifying BYOK supports that credential-path observation, subject to log integrity; the default fallback need not occur.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
Regional inference does not pin the complete request path
Does Vercel inferenceRegion establish that the gateway and every downstream copy stayed in that region?
The documented pin controls provider inference and configured provider storage; a request-level region must remain within a team pin. Gateway processing may occur in any Vercel region. Gateway-run tools and provider abuse or safety handling have separate location boundaries. Check the serving attempt region, not just the requested value.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Refuse an end-to-end regional or sovereign-processing claim from inferenceRegion alone; review tool transfers, safety exceptions and provider terms separately.
- A region-pinned inference attempt can satisfy the narrower documented provider-location question while gateway or tool processing remains outside that scope.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
An account region list is not the inference destination set
Does a Bedrock source Region or manually enabled Region list constrain every cross-Region request to that location?
Bedrock uses the selected inference profile to define eligible processing destinations. Geographic profiles stay within their specified geography; global profiles can route worldwide among supported commercial Regions. Cross-Region inference can use Regions not manually enabled in the account. Source-region selection therefore does not identify the processing destination.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Require the exact profile, model, destination list and request-time evidence; do not infer a single processing region from the client endpoint or account enablement.
- A geographic profile can constrain its declared pool even though its request may leave the source Region; global routing is not mandatory for every profile.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
Profile and destination permissions have different evaluation context
Can a Bedrock inference-profile exception bypass a denied originating Region?
For Geographic cross-Region inference, AWS evaluates the profile and foundation-model resources in the source and candidate destination Regions. The InferenceProfileArn condition is present for foundation-model evaluations, but absent for the profile-resource evaluation. A destination-region exception using that condition cannot bypass the originating-call Region restriction.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Review source and destination authorization separately; do not treat a profile-condition exception as universal authorization or assume denied destinations are silently removed.
- A scoped profile exception can permit destination model evaluations while ordinary Region restrictions remain for other services and the originating call.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
Deployment class matters more than resource location
Does an Azure Foundry resource location establish the exact geography where every model request is processed?
The captured Microsoft guides distinguish Global, Data Zone and geography-based deployments; the resource location alone does not select their processing scope. Their EU descriptions differ: the privacy page says EU member nations, while the deployment guide includes the EU Data Boundary and possible EFTA regions. An exact country set remains unresolved from these captures.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Refuse an exact-country, sovereign or compliance determination until the applicable deployment, model, current destination membership and governing terms resolve this source discrepancy.
- A deployment-specific current agreement and destination evidence may resolve the narrower question; the discrepancy does not mean every deployment routes globally.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
A visible request row can outlive its routing evidence
Can an old Vercel AI Gateway request row establish all attempted providers and credential sources?
Vercel documents a 30-day lifetime for routing-attempt details. Older rows can remain visible without those details. The dashboard export covers the rows currently loaded under its filters; a row or export is therefore not necessarily a complete retained provider-attempt history.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Refuse historical attempt or credential completeness when details have expired or export selection is unknown; retain a separately verified suitable record before relying on it.
- A recent complete correlated routing detail can identify the recorded successful attempt; this does not establish every export is incomplete.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review