all docs
/ integrations

Google Gemini (Developer API) integration

Call Google Gemini (Developer API) through the ACE gateway: endpoint, zero-trust credential headers, stored-key alternative and runnable examples.

Send Google Gemini (Developer API) traffic to https://engine.acefleet.dev/gemini/v1beta/models/<model>:generateContent with your ACE developer key in Authorization: Bearer ace_dev_... and the provider credential on the zero-trust headers below. The request body is the vendor's own, relayed as written, and the vendor's answer comes back verbatim.

Zero-trust headers

Header Required What it carries
x-ace-google-key yes Upstream Google AI key, for the Gemini-shaped surface.
x-ace-provider situational Pin the channel to google_gemini rather than Vertex.

Stored key instead

A stored google vendor key replaces x-ace-google-key.

Example request

curl -X POST "https://engine.acefleet.dev/gemini/v1beta/models/gemini-2.5-flash:generateContent" \
  -H "x-goog-api-key: ace_dev_<your-dev-key>" \
  -H "x-ace-provider: google_gemini" \
  -H "x-ace-google-key: <your-gemini-key>" \
  -H "Content-Type: application/json" \
  -d '{ "contents": [{ "role": "user", "parts": [{ "text": "ping" }] }] }'

Quickstarts

Google Gemini proxy (cURL)

curl -X POST "https://engine.acefleet.dev/gemini/v1beta/models/gemini-2.5-flash:generateContent" \
  -H "x-goog-api-key: ace_dev_<your-dev-key>" \
  -H "x-ace-provider: google_gemini" \
  -H "x-ace-google-key: <your-gemini-key>" \
  -H "Content-Type: application/json" \
  -d '{ "contents": [{ "role": "user", "parts": [{ "text": "Optimize GPU allocations." }] }] }'