Model limit probe

Writer: Palmyra X5 | RPM limit

Writer: Palmyra X5 RPM limit decides whether a key can enter a production route. TestKey reads model ID writer/palmyra-x5, provider Writer, catalog context, real-key headers, 429 errors, and region signals together.

Model

writer/palmyra-x5

Writer: Palmyra X5

Provider

Writer

1 models in catalog

Limit dimension

RPM limit

rpm-limit

Visible signal

real key probe required

Context window: 1,040,000

Limit matrix summary

Model

writer/palmyra-x5

Limit dimension

rpm-limit

Visible signal

real key probe required

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

Why this limit matters

Writer: Palmyra X5 RPM limit decides whether a key can enter a production route. TestKey reads model ID writer/palmyra-x5, provider Writer, catalog context, real-key headers, 429 errors, and region signals together.

Model: writer/palmyra-x5
Provider: Writer
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 writer/palmyra-x5; limits from another model at the same provider cannot be reused.
RPM limit · real key probe required · 1,040,000

Operator action

Writer: Palmyra X5 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: 1,040,000

Open key checker

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