Gemini (gemini) is part of the surface enum, but it has no live capture path in v1. It returns a 422 rather than a stand-in that isn’t the real Gemini experience.
Submitting surfaces: ["gemini"] today returns 422 UNSUPPORTED_METHOD_FOR_SURFACE. This is deliberate: nothing we currently offer clears the bar for a trustworthy Gemini capture (see below).

Why there’s no v1 path

Every capture we serve must faithfully represent either the vendor’s official API or the real consumer experience — never a sanitized stand-in. Gemini doesn’t clear that bar yet:
  • Google’s Gemini API terms bar resale of its output, so serving it through Google’s own API isn’t on the table.
  • The Gemini web app is login-walled: every guest capture hits a login stop. Serving it faithfully needs an authenticated account pool, which isn’t provisioned yet.
You can confirm this at any time from the live capability matrix:
Excerpt

What a request returns today

422 Unprocessable Entity
The rejection happens at admission — nothing is spawned and nothing is billed. On a batch, only the Gemini item is rejected; other items proceed.

Cover Google’s AI answers today

While Gemini is pending, Google’s AI-generated answers are live through two other surfaces:

Google AI Overview

The AI summary at the top of Google Search — live via real browser (google_ai_overview).

Google AI Mode

Google’s conversational AI search experience — live via real browser (google_ai_mode).

When it goes live

Gemini support lands once an authenticated account pool is provisioned. When it does, you’ll request it like any other surface — surfaces: ["gemini"], same request body, same canonical Envelope — with no integration changes. Watch the changelog or poll GET /v1/surfaces for the flip.

All surfaces

What’s live today and what’s coming next.

Errors

The 422 you’ll see if you request Gemini early.