Probe Help article

Provider routing checks

Learn what to verify when an AI provider, model, or routing path behaves differently than expected.

aiprovidersadmin
Visibility
public
Reading time
1 min read
Last reviewed
Reviewed 2026-05-13

Short answer

Provider routing issues need the model, provider path, tool mode, and product surface where the request ran.

When to use this

Use this article when an AI action works in one surface but not another, or when model behavior changes by provider.

Requirements

Do not expose API keys, provider secrets, or private tool payloads in support messages.

What to collect

Record the model label, provider path if visible, product surface, tool or agent mode, and the user-visible error.

Common problems

Different providers and modes can support different tool behavior. A support request should describe the route and tool expectation, not only the final answer.

Read Provider routing basics for the user-facing model overview.

Escalation guidance

For provider issues, include safe request metadata and the exact action that failed.

Related articles

publicReviewed 2026-05-13

Provider routing basics

Understand how Help Center articles should describe model providers, connected apps, and integration limits.

publicReviewed 2026-05-13

Safe AI answers

Learn how to evaluate AI answers, reduce risky context, and escalate when a response is not enough.

Was this article helpful?

Your feedback helps Probe improve articles, search synonyms, and support triage.