Model limit probe

Reka Flash 3 | RPM limit

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

Model

rekaai/reka-flash-3

Reka Flash 3

Provider

Rekaai

2 models in catalog

Limit dimension

RPM limit

rpm-limit

Visible signal

real key probe required

Context window: 65,536

Limit matrix summary

Model

rekaai/reka-flash-3

Limit dimension

rpm-limit

Visible signal

real key probe required

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

Why this limit matters

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

Model: rekaai/reka-flash-3
Provider: Rekaai
Limit dimension: RPM limit

How to prove it

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

Start with the visible signal: real key probe required, then read headers and error bodies with read-only requests.
RPM limit must bind model ID rekaai/reka-flash-3; limits from another model at the same provider cannot be reused.
RPM limit · real key probe required · 65,536

Operator action

Reka Flash 3 RPM 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: real key probe required
Context window: 65,536

Open key checker

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