[ English | δΈζ ]
Web-based Gemini models wrapped into an OpenAI-compatible API. Powered by HanaokaYuzu/Gemini-API.
β Call Gemini's web-based models via API without an API Key, completely free!
- π No Google API Key Required: Use web cookies to freely access Gemini's models via API.
- π Google Search Included: Get up-to-date answers using web-based Gemini's search capabilities.
- πΎ Conversation Persistence: LMDB-based storage supporting multi-turn conversations.
- πΌοΈ Multi-modal Support: Support for handling text, images, and file uploads.
- βοΈ Multi-account Load Balancing: Distribute requests across multiple accounts with per-account proxy settings.
For Docker deployment, see the Docker Deployment section below.
- Python 3.12
- Google account with Gemini access on web
secure_1psidandsecure_1psidtscookies from Gemini web interface
git clone https://github.com/Nativu5/Gemini-FastAPI.git
cd Gemini-FastAPI
uv syncgit clone https://github.com/Nativu5/Gemini-FastAPI.git
cd Gemini-FastAPI
pip install -e .Edit config/config.yaml and provide at least one credential pair:
gemini:
clients:
- id: "client-a"
secure_1psid: "YOUR_SECURE_1PSID_HERE"
secure_1psidts: "YOUR_SECURE_1PSIDTS_HERE"
proxy: null # Optional proxy URL (null/empty keeps direct connection)Note
For details, refer to the Configuration section below.
# Using uv
uv run python run.py
# Using Python directly
python run.pyThe server will start on http://localhost:8000 by default.
docker run -p 8000:8000 \
-v $(pwd)/data:/app/data \
-v $(pwd)/cache:/app/cache \
-e CONFIG_SERVER__API_KEY="your-api-key-here" \
-e CONFIG_GEMINI__CLIENTS__0__ID="client-a" \
-e CONFIG_GEMINI__CLIENTS__0__SECURE_1PSID="your-secure-1psid" \
-e CONFIG_GEMINI__CLIENTS__0__SECURE_1PSIDTS="your-secure-1psidts" \
-e GEMINI_COOKIE_PATH="/app/cache" \
ghcr.io/nativu5/gemini-fastapiTip
Add CONFIG_GEMINI__CLIENTS__N__PROXY only if you need a proxy; omit the variable to keep direct connections.
GEMINI_COOKIE_PATH points to the directory inside the container where refreshed cookies are stored. Bind-mounting it (e.g. -v $(pwd)/cache:/app/cache) preserves those cookies across container rebuilds/recreations so you rarely need to re-authenticate.
Create a docker-compose.yml file:
services:
gemini-fastapi:
image: ghcr.io/nativu5/gemini-fastapi:latest
ports:
- "8000:8000"
volumes:
# - ./config:/app/config # Uncomment to use a custom config file
# - ./certs:/app/certs # Uncomment to enable HTTPS with your certs
- ./data:/app/data
- ./cache:/app/cache
environment:
- CONFIG_SERVER__HOST=0.0.0.0
- CONFIG_SERVER__PORT=8000
- CONFIG_SERVER__API_KEY=${API_KEY}
- CONFIG_GEMINI__CLIENTS__0__ID=client-a
- CONFIG_GEMINI__CLIENTS__0__SECURE_1PSID=${SECURE_1PSID}
- CONFIG_GEMINI__CLIENTS__0__SECURE_1PSIDTS=${SECURE_1PSIDTS}
- GEMINI_COOKIE_PATH=/app/cache # must match the cache volume mount above
restart: on-failure:3 # Avoid retrying too many timesThen run:
docker compose up -dImportant
Make sure to mount the /app/data volume to persist conversation data between container restarts.
Also mount /app/cache so refreshed cookies (including rotated 1PSIDTS values) survive container rebuilds/recreates without re-auth.
The server reads a YAML configuration file located at config/config.yaml.
For details on each configuration option, refer to the comments in the config/config.yaml file.
Tip
This feature is particularly useful for Docker deployments and production environments where you want to keep sensitive credentials separate from configuration files.
You can override any configuration option using environment variables with the CONFIG_ prefix. Use double underscores (__) to represent nested keys, for example:
# Override server settings
export CONFIG_SERVER__API_KEY="your-secure-api-key"
# Override Gemini credentials for client 0
export CONFIG_GEMINI__CLIENTS__0__ID="client-a"
export CONFIG_GEMINI__CLIENTS__0__SECURE_1PSID="your-secure-1psid"
export CONFIG_GEMINI__CLIENTS__0__SECURE_1PSIDTS="your-secure-1psidts"
# Override optional proxy settings for client 0
export CONFIG_GEMINI__CLIENTS__0__PROXY="socks5://127.0.0.1:1080"
# Override conversation storage size limit
export CONFIG_STORAGE__MAX_SIZE=268435456 # 256 MBConversations are stored with the ID of the client that generated them. Keep these identifiers stable in your configuration so that sessions remain valid when you update the cookie list.
Warning
Keep these credentials secure and never commit them to version control. These cookies provide access to your Google account.
To use Gemini-FastAPI, you need to extract your Gemini session cookies:
- Open Gemini in a private/incognito browser window and sign in
- Open Developer Tools (F12)
- Navigate to Application β Storage β Cookies
- Find and copy the values for:
__Secure-1PSID__Secure-1PSIDTS
Tip
For detailed instructions, refer to the HanaokaYuzu/Gemini-API authentication guide.
Each client entry can be configured with a different proxy to work around rate limits. Omit the proxy field or set it to null or an empty string to keep a direct connection.
- HanaokaYuzu/Gemini-API - The underlying Gemini web API client
- zhiyu1998/Gemi2Api-Server - This project originated from this repository. After extensive refactoring and engineering improvements, it has evolved into an independent project, featuring multi-turn conversation reuse among other enhancements. Special thanks for the inspiration and foundational work provided.
This project is not affiliated with Google or OpenAI and is intended solely for educational and research purposes. It uses reverse-engineered APIs and may not comply with Google's Terms of Service. Use at your own risk.