Model error diagnosis

Reka Edge | model permission denied

Reka Edge returning 403 / model permission denied means you should first confirm whether model ID rekaai/reka-edge is visible for this Rekaai key, then separate permission, context, capability, rate limit, or route issues.

Model

rekaai/reka-edge

Reka Edge

Provider

Rekaai

2 models in catalog

Error type

model permission denied

permission-denied

Status code

403

global model route

Model error summary

Model

rekaai/reka-edge

Error type

permission-denied

Status code

403

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

What this model error usually means

Reka Edge returning 403 / model permission denied means you should first confirm whether model ID rekaai/reka-edge is visible for this Rekaai key, then separate permission, context, capability, rate limit, or route issues.

Model: rekaai/reka-edge
Provider: Rekaai
Status code: 403

How to prove it during checking

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

List models: confirm whether rekaai/reka-edge is actually visible instead of guessing from the display name.
Light probe: use minimal input to verify whether Rekaai returns the same 403, then record the error body.
Compare model facts: context 16,384, input $0.100, output $0.100.
supports frequency_penalty
supports max_tokens
supports presence_penalty
supports seed

Next action

Reka Edge model permission denied should not end at failed. Return the next move: change model ID, add permission, reduce context, disable unsupported capability, change route, monitor, or hold listing.

Context: 16,384
Price: $0.100 / $0.100
Read-only check. Detection data burns after 5 minutes.

Open key checker

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