Skip to main content
Google’s gemini-cli (and the family of CLIs / IDE extensions built on top of it) speaks the Gemini Native protocol — query-param auth (?key=...) against /v1beta/models/{model}:generateContent. ByteSpike serves that protocol verbatim at llm.bytespike.ai/v1beta.

Prerequisites

  • A ByteSpike account + a key bound to the gemini-default group (or any group that serves Gemini models). See Register.
  • Gemini CLI installed:

Configure

Gemini CLIs typically read GEMINI_API_KEY and let you override the base URL via env or flag.
For the official Google CLI that doesn’t expose a base-URL flag, set the variable per its docs (some versions read GOOGLE_API_BASE_URL); or use the raw curl form (next section) inside a wrapper script.

Verify

Expect a 200 with a candidates[0].content.parts[0].text field, plus the standard X-Quota-Remaining-Credits header.

Switching models

The model name lives in the URL path:
Any model id from your key’s group works. See /v1beta reference for the full request shape.

Streaming

Switch the method suffix:
SSE stream matches Google’s native format — data: {chunk}\n\n blocks terminated by a final [DONE] marker.

SDKs

Both Google’s official Generative AI SDK and most third-party Gemini clients accept a baseUrl override at client construction:

Image + video models via Gemini stack

Veo (Google’s video model) ships under the Gemini API surface but the long-running shape uses ByteSpike’s async tasks API instead:
See POST /tasks/submit and the Veo 3.1 model page.

Troubleshooting

Next

/v1beta reference

Full request / response / streaming protocol.

Gemini models

Models, capabilities, pricing.

Claude Code CLI

The Anthropic-native equivalent.

Cursor IDE

Editor-level Gemini integration.