Key error diagnosis

Essentialai | project scope missing

Diagnose Essentialai project scope missing (403) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.

Provider

Essentialai

global provider route

Error type

project scope missing

medium

Status code

403

project-scope-missing

Sample models

Rnj 1 Instruct

Error route summary

Error type

project-scope-missing

medium

Provider

Essentialai

Status code

403

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

What this error usually means

Diagnose Essentialai project scope missing (403) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.

Provider: Essentialai
Error type: project scope missing
Status code: 403

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

Next action

project scope missing 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
Rnj 1 Instruct

Open key check

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