Limitations & Tips

Limitations

Each request is single‑turn only; multi‑turn context is simulated by including previous messages in the prompt.
Rate limits exist because Google may throttle high‑frequency requests; the server retries automatically.
To use the Pro model (gemini-3.1-pro) you need a Gemini Advanced (paid subscription) cookie; otherwise it falls back to Flash.
Image upload may require cookies; configure a Gemini cookie if you encounter empty responses.
The free tiers of the hosting platforms have daily request limits; monitor usage to avoid service interruption.

For production, consider setting your own API key instead of the default now-and-then and monitor your usage.
If you encounter HTTP 429: Too Many Requests, configure a valid Gemini cookie (COOKIE_STRING and SAPISID environment variables) to improve reliability.
If you see HTTP 405: Method Not Allowed, update the GEMINI_BL environment variable to the latest build tag (see the “Updating BL Version” section in the platform-specific guides).
The Pro model requires a paid Gemini Advanced cookie; without it, gemini-3.1-pro routes to the same Flash model.
For image inputs, ensure your cookie is set if anonymous upload fails.
Use the health endpoint (/health) to verify your deployment is running correctly.