Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Gemini API has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 4 scoped observations for Gemini API. The baseline covers rate-limit dimensions, long-context support, batch concurrency and enqueued work, batch/file storage. 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 |
|---|---|---|---|
| rate-limit dimensionsLimits apply per project, not per API key, and daily requests reset at midnight Pacific Time. | RPM, TPM, and RPD vary by model and usage tier | Per Google Cloud project | GoogleAug 22, 2026 |
| long-context supportThe exact input and output budget must be read from the deployed model specification. | Many Gemini models support 1M+ tokens | Model specific | GoogleAug 22, 2026 |
| batch concurrency and enqueued workBatch token capacity is separate from the fixed concurrent request count. | 100 concurrent batch requests; enqueued tokens vary by model and tier | Per project | GoogleAug 22, 2026 |
| batch/file storageThe file and aggregate storage ceilings are independent of prompt context capacity. | 2 GB per input file; 20 GB project file storage | Per project | GoogleAug 22, 2026 |
Tracked constraints and impact
Project-scoped RPM, TPM, daily, batch, file, and model context limits. 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.
Gemini API Rate Limits: RPM, TPM & RPD
Gemini API Rate Limits: RPM, TPM & RPD, verified against Gemini API's official documentation with scope, implementation impact, caveats, and a direct check.
Gemini API Long Context Limits
Gemini API Long Context Limits, verified against Gemini API's official documentation with scope, implementation impact, caveats, and a direct check.
Gemini API Batch Limits
Gemini API Batch Limits, verified against Gemini API's official documentation with scope, implementation impact, caveats, and a direct check.
Gemini API File & Storage Limits
Gemini API File & Storage Limits, verified against Gemini API'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 Gemini API baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
RPM, TPM, RPD, tiers, batch requests, and file storage
Model context-window guidance