Key error diagnosis

Inflection | revoked key

Inflection returning 401 / revoked key should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider

Inflection

global provider route

Error type

revoked key

high

Status code

401

revoked-key

Sample models

Inflection 3 Pi · Inflection 3 Productivity

Error route summary

Error type

revoked-key

high

Provider

Inflection

Status code

401

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

What this error usually means

Inflection returning 401 / revoked key should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider: Inflection
Error type: revoked key
Status code: 401

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 Inflection, not just a compatible protocol.
Then list models or run a lightweight probe: check whether models like Inflection 3 Pi · Inflection 3 Productivity are visible and return stable evidence.
Finally record 401, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.

Next action

revoked key 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
Inflection 3 Pi · Inflection 3 Productivity

Open key checker

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

Open providers

Inflection

Open models

Inflection 3 Pi · Inflection 3 Productivity