AI Model Routing Rule Checker

How to use AI Model Routing Rule Checker

A routing setting is useful only if the observed provider choice agrees with the intended constraints. Audit supplied request records against dated provider evidence and preserve missing facts as unknown.

1. Copy neutral request/provider identifiers and the exact dated provider evidence snapshot applicable to each record.
2. Declare your allowed providers, required capabilities, optional region and evidence freshness policy.
3. Investigate contradictions and unknowns with actual contracts, logs and live authorized tests before trusting a deployment.

Good to know

• Provider facts are entered declarations, not live capabilities. Stale, missing or future evidence does not establish a requirement; a known disallowed provider or declared no remains a contradiction.
• An exact region label is not verified data residency. No route, fallback, retention contract, endpoint, API or traffic is contacted or changed. Maximum evidence age is 3,650 days.
• Each input field is limited to 8,000 UTF-16 characters. CSV needs the exact displayed header and at most 100 data rows. Quoted commas, doubled quotes and quoted newlines are supported. Duplicate identities are refused unless the tool explicitly reports them as findings.
• Markdown and CSV are editable review artifacts, not certificates. Spreadsheet-like text is apostrophe-prefixed in CSV to reduce formula execution risk; check the actual importer before sharing. Decimal ratios are rounded to at most 12 places.
• Runs only on the records you enter, locally in your browser. No AI call, provider connection, account inspection, upload, automatic outreach or saved input. Use neutral identifiers rather than personal or secret content.