Model limit probe

Reka Edge | region and IP limit

Reka Edge region and IP limit decides whether a key can enter a production route. TestKey reads model ID rekaai/reka-edge, provider Rekaai, catalog context, real-key headers, 429 errors, and region signals together.

Model

rekaai/reka-edge

Reka Edge

Provider

Rekaai

2 models in catalog

Limit dimension

region and IP limit

region-ip

Visible signal

catalog plus runtime

Context window: 16,384

Limit matrix summary

Model

rekaai/reka-edge

Limit dimension

region-ip

Visible signal

catalog plus runtime

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

Why this limit matters

Reka Edge region and IP limit decides whether a key can enter a production route. TestKey reads model ID rekaai/reka-edge, provider Rekaai, catalog context, real-key headers, 429 errors, and region signals together.

Model: rekaai/reka-edge
Provider: Rekaai
Limit dimension: region and IP limit

How to prove it

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

Start with the visible signal: catalog plus runtime, then read headers and error bodies with read-only requests.
region and IP limit must bind model ID rekaai/reka-edge; limits from another model at the same provider cannot be reused.
region and IP limit · catalog plus runtime · 16,384

Operator action

Reka Edge region and IP limit is not just a number. It should become route throttling, sale tags, headroom alerts, fallback model suggestions, and price protection.

Read-only check. Detection data burns after 5 minutes.
Visible signal: catalog plus runtime
Context window: 16,384

Open key checker

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