> ## Documentation Index
> Fetch the complete documentation index at: https://doc.entelligence.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Model Router privacy, credentials, and troubleshooting
> Understand Proxy and BYOK credentials, visible session metadata, rollback, and common routing problems.
Proxy and BYOK use different credential and billing paths. Choose the path approved for your organization before enabling routing.
## BYOK credentials
The current BYOK screen supports AWS Bedrock and OpenRouter. The product states that submitted credentials are encrypted at rest.
Use a dedicated credential with the smallest required scope. Rotate it through your provider's normal process, and never include a real value in documentation or support screenshots.
## What administrators can inspect
The dashboard exposes routing metadata such as member, session ID, time, model, token counts, cost, and savings. Confirm prompt, response, logging, retention, region, and support-access terms against your approved architecture and agreement.
## Common problems
| Symptom | Check |
| -------------------------- | -------------------------------------------------------------------------- |
| Routing is inactive | Active state, workspace entitlement, CLI authentication, and Proxy balance |
| Session is missing | Supported tool, member mapping, time range, and active routing |
| Unexpected model | Balanced or Eco mode, request difficulty, availability, and fallback |
| Cost is unexpected | Baseline, cached tokens, task mix, and provider pricing |
| Proxy is paused | Balance, routing limit, auto top-up, and payment status |
| BYOK request fails | Credential validity, provider permissions, quota, region, and network |
| Agent fails after rollback | Direct provider URL, credential, and local configuration |
| Savings do not reconcile | Date range, session coverage, baseline, and invoice source |
## Recover safely
1. Pause routing or run entelligence router off.
2. Confirm direct provider access.
3. Record affected users, session IDs, timestamps, and routing mode.
4. Check wallet, credential, provider, and network state.
5. Resume only after a representative task succeeds.