Key error diagnosis

Tngtech | tools unsupported

Tngtech returning 400 / tools unsupported should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider

Tngtech

global provider route

Error type

tools unsupported

medium

Status code

400

tools-unsupported

Sample models

DeepSeek R1T2 Chimera

Error route summary

Error type

tools-unsupported

medium

Provider

Tngtech

Status code

400

Read-only check. Detection data burns after 5 minutes.

What this error usually means

Tngtech returning 400 / tools unsupported should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider: Tngtech
Error type: tools unsupported
Status code: 400

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 Tngtech, not just a compatible protocol.
Then list models or run a lightweight probe: check whether models like DeepSeek R1T2 Chimera 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
DeepSeek R1T2 Chimera

Open key checker

Read-only check. Detection data burns after 5 minutes.

Open providers

Tngtech

Open models

DeepSeek R1T2 Chimera