← Volver a las guías

Gemini CLI via 59API: A Practical 2026 Relay Guide

Use a unified relay without changing your workflow

Using Gemini CLI through a unified relay should simplify billing and configuration, not introduce mysterious compatibility failures. This 2026 guide focuses on a reliable setup: install the official CLI, configure 59API's native Gemini endpoint, select API-key authentication, and verify both responses and billing before working with a real repository.

1. Match the protocol, not just the provider

A unified account does not mean every model uses the same API format. 59API documents a native Gemini interface for Gemini CLI. Set the base URL to the bare service domain; do not append /v1 or /v1beta. Its Gemini requests use Google's native protocol rather than the OpenAI chat-completions endpoint. ([59api.com](https://59api.com/docs))

The official CLI setting is GOOGLE_GEMINI_BASE_URL, which applies when using Gemini API-key authentication. Setting OPENAI_BASE_URL alone is not the documented configuration path for this workflow. ([geminicli.com](https://geminicli.com/docs/reference/configuration/))

2. Install and establish a clean baseline

Use Node.js 20 or later, then install the official package with npm install -g @google/gemini-cli. Run gemini --version and record the installed version. For automation, pin a tested version rather than allowing unattended upgrades to change your environment. ([geminicli.com](https://geminicli.com/docs/get-started/installation/))

Create a dedicated relay key and begin with a small prepaid balance. Keep the first experiment outside your production repository so configuration mistakes cannot expose sensitive project context.

3. Configure the endpoint and authentication

In Bash, set the endpoint:

export GOOGLE_GEMINI_BASE_URL="https://api.59api.com"

Load your 59API key into GEMINI_API_KEY through your secret manager. For a temporary local test, enter it without placing the literal secret in your command:

read -rsp '59API key: ' GEMINI_API_KEY; export GEMINI_API_KEY; echo

Then run gemini and select Use Gemini API key. The relay supplies the credential; Gemini CLI supplies the native request format. This endpoint-and-key combination is documented by 59API, while Google's authentication guide documents the CLI's API-key selection. ([59api.com](https://59api.com/docs))

If you previously authenticated through Google sign-in, explicitly switch authentication methods before testing. Headless runs can reuse cached authentication, so a successful response alone does not establish that the relay handled the request. ([geminicli.com](https://geminicli.com/docs/get-started/authentication/))

Choose an available model such as Gemini 3.8 Flash or Gemini 3.1 Pro, copying its API identifier from 59API's documentation rather than guessing it from the display name. Set that identifier through GEMINI_MODEL. ([59api.com](https://59api.com/docs))

4. Test responses, usage, and tool behavior

From an empty test directory, run gemini -p 'Reply with exactly: relay-ready' --output-format json. The prompt flag starts headless operation, and JSON output includes the response and usage statistics. Check the command's exit status as well as its text output. ([geminicli.com](https://geminicli.com/docs/cli/headless/))

Find the matching request in 59API's dashboard and inspect its recorded tokens and cost. Next, test a harmless file-reading task and a small approved edit in a disposable Git repository. Treat streaming, tool execution, and billing verification as separate acceptance checks. 59API documents per-request usage and cost logs. ([59api.com](https://59api.com/pricing))

5. Troubleshoot before adding complexity

• Authentication failure: confirm the exported key and selected authentication method.
• Unexpected routing: inspect project settings, user settings, environment variables, and cached authentication.
• Endpoint failure: restore the bare base URL and confirm the documented model identifier.
• HTTP 402: check your prepaid balance; 59API documents this response for an empty balance.

Configuration can come from multiple layers, so inspect effective settings rather than repeatedly changing credentials. ([geminicli.com](https://geminicli.com/docs/reference/configuration/))

Keep the economics practical

59API is a compelling low-cost choice for developers who prefer prepaid, pay-as-you-go usage over another mandatory subscription. It promotes official-quality model capability, supports multiple developer clients, and offers a referral rebate. Compare current input, output, and cache rates against your actual workload rather than assuming one headline price predicts every task's cost. ([59api.com](https://59api.com/))

For production use, separate development and CI credentials, exclude secrets from Git, restrict tool approvals, and review a representative usage sample before scaling. If this fits your workflow, consider signing up for 59API and validating the setup with a small initial balance.

Precios · Docs