What this error usually means
Diagnose Inception tools unsupported (400) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
- Provider: Inception
- Error type: tools unsupported
- Status code: 400
Key error diagnosis
Inception | tools unsupported
Diagnose Inception tools unsupported (400) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
Provider
Inception
global provider route
Error type
tools unsupported
medium
Status code
400
tools-unsupported
Sample models
3
Mercury · Mercury 2 · Mercury Coder
Error route summary
Error type
tools-unsupported
medium
Provider
Inception
Status code
400
Read-only check. Detection data burns after 5 minutes.
Read-only check. Detection data burns after 5 minutes.
How to prove it during checking
Read-only check. Detection data burns after 5 minutes.
- Run read-only identity first: confirm whether the key really belongs to Inception, not just a compatible protocol.
- Then list models or run a lightweight probe: check whether models like Mercury · Mercury 2 · Mercury Coder are visible and return stable evidence.
- Finally record 400, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.
Next action
tools unsupported should not only show failed. The console should return the next move: refill balance, change Base URL, switch model, add permission, change egress IP, hold listing, or monitor.
- Read-only check. Detection data burns after 5 minutes.
- global provider route
- Mercury · Mercury 2 · Mercury Coder