Model limit probe

Goliath 120B | RPM limit

Goliath 120B RPM limit decides whether a key can enter a production route. TestKey reads model ID alpindale/goliath-120b, provider Alpindale, catalog context, real-key headers, 429 errors, and region signals together.

Model

alpindale/goliath-120b

Goliath 120B

Provider

Alpindale

1 models in catalog

Limit dimension

RPM limit

rpm-limit

Visible signal

real key probe required

Context window: 6,144

Limit matrix summary

Model

alpindale/goliath-120b

Limit dimension

rpm-limit

Visible signal

real key probe required

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

Why this limit matters

Goliath 120B RPM limit decides whether a key can enter a production route. TestKey reads model ID alpindale/goliath-120b, provider Alpindale, catalog context, real-key headers, 429 errors, and region signals together.

Model: alpindale/goliath-120b
Provider: Alpindale
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 alpindale/goliath-120b; limits from another model at the same provider cannot be reused.
RPM limit · real key probe required · 6,144

Operator action

Goliath 120B 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: 6,144

Open key checker

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