Model limit probe

Google: Gemma 3 4B | RPM limit

Google: Gemma 3 4B RPM limit decides whether a key can enter a production route. TestKey reads model ID google/gemma-3-4b-it, provider Google, catalog context, real-key headers, 429 errors, and region signals together.

Model

google/gemma-3-4b-it

Google: Gemma 3 4B

Provider

Google

32 models in catalog

Limit dimension

RPM limit

rpm-limit

Visible signal

real key probe required

Context window: 131,072

Limit matrix summary

Model

google/gemma-3-4b-it

Limit dimension

rpm-limit

Visible signal

real key probe required

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

Why this limit matters

Google: Gemma 3 4B RPM limit decides whether a key can enter a production route. TestKey reads model ID google/gemma-3-4b-it, provider Google, catalog context, real-key headers, 429 errors, and region signals together.

Model: google/gemma-3-4b-it
Provider: Google
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 google/gemma-3-4b-it; limits from another model at the same provider cannot be reused.
RPM limit · real key probe required · 131,072

Operator action

Google: Gemma 3 4B 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: 131,072

Open key checker

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