Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean OpenRouter has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 3 scoped observations for OpenRouter. The baseline covers free-model allowance, routed model context, rate-limit scope. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| free-model allowanceThe purchased-credit threshold changes the documented daily free-model allowance. | 50 requests/day below $10 credits; 1,000/day after $10+ purchased | Free model variants | OpenRouterAug 22, 2026 |
| routed model contextOpenRouter model metadata also exposes provider-specific per-request limits when available. | Varies by model; exposed as context_length | Per model | OpenRouterAug 22, 2026 |
| rate-limit scopeRouting cannot guarantee identical capacity across different upstream model providers. | Account, model, and upstream-provider dependent | All accounts | OpenRouterAug 22, 2026 |
Tracked constraints and impact
Free-model requests, account credits, model context metadata, and provider routing. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
OpenRouter Free Model Request Limits
OpenRouter Free Model Request Limits, verified against OpenRouter's official documentation with scope, implementation impact, caveats, and a direct check.
OpenRouter Model Context Limits
OpenRouter Model Context Limits, verified against OpenRouter's official documentation with scope, implementation impact, caveats, and a direct check.
OpenRouter Provider Rate-Limit Scope
OpenRouter Provider Rate-Limit Scope, verified against OpenRouter's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current OpenRouter baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Free-model request allowances and account credit rules
Context length and per-request limit fields