MiniMax H3 (Hailuo 3) is live on EvoLinkTry it with 10 free credits

Gemini 3.5 Pro API

Google-Text and input modes not publicly specified-Partner testing · No public API route

Google says Gemini 3.5 Pro is testing with partners and will become broadly available when ready. It is not listed in the public Gemini API catalog, so there is no confirmed public model ID, price, input-mode specification, or callable EvoLink route yet.

Is the Gemini 3.5 Pro API officially available?

Google Status

Confirmed model; currently testing with partners

Public API Status

No public route, model ID, pricing row, or access program

Last Verified

August 1, 2026
Partner Testing · EvoLink Route Pending

Get the Gemini 3.5 Pro API Launch Alert

EvoLink will notify you after a public upstream route, request model ID, pricing, and route behavior are verified. This is an independent product alert, not Google Early Access, a partner program, or a guarantee of access.

Get notified when the EvoLink route is ready

EvoLink product alerts only. No Google affiliation, partner access, access guarantee, or spam.

Want faster updates? Join the EvoLink Discord

What this page will publish after launch

The confirmed request model ID, supported input modes and tools, live EvoLink pricing, limits, compatibility, and a controlled migration path through the unified API.

Gemini 3.5 Pro API Access, Pricing, Model ID, and Inputs

These are the facts needed for a real integration. Google has confirmed partner testing, but the public API details below remain unpublished as of August 1, 2026.

Confirmed

Official product status

Google has named Gemini 3.5 Pro and says it is currently testing with partners, with broader availability planned when the model is ready.

Not Public

Where can developers access it?

No public Gemini API, Google AI Studio, Vertex AI, or EvoLink route is documented for Gemini 3.5 Pro. Partner testing is not public Early Access.

Awaiting Publication

Model ID and request format

Google's public model catalog does not list a Gemini 3.5 Pro request ID. Treat strings such as `gemini-3.5-pro` as unverified placeholders, not production configuration.

Awaiting Publication

API pricing and service tiers

No official input, output, caching, batch, priority, or long-context price has been published for Gemini 3.5 Pro. EvoLink will reuse its live pricing module after SKUs are approved.

Awaiting Publication

Input modes, tools, context, and limits

Text, image, audio, video, PDF, tool calling, context length, output limit, quotas, and regions are not yet documented for the public route.

What can you prepare before Gemini 3.5 Pro launches?

Prepare the evaluation and routing layer now without making an unreleased model a production dependency.

1

Keep the model ID configurable

Store the selected model in configuration so the verified request ID can be added without changing application business logic.

2

Save representative evaluation tasks

Build a fixed set of coding, agent, document, and multimodal tasks using inputs you are permitted to test.

3

Record a callable baseline

Measure task success, latency, token use, retries, and tool errors on Gemini 3.1 Pro or Gemini 3.5 Flash now.

4

Define an acceptance gate

Choose the minimum improvement in quality, reliability, or cost per successful task required before moving traffic.

5

Plan shadow and canary traffic

Evaluate the verified route offline, then with shadow requests and a small canary before changing the default model.

6

Keep a tested fallback

Retain a callable Gemini route and explicit timeout, retry, and rollback rules until the new route proves stable.

Why use EvoLink for Gemini 3.5 Pro after launch?

The reason is operational flexibility, not early access. EvoLink can add the verified Gemini 3.5 Pro route to the same gateway teams already use for available Gemini and cross-provider models.

One integration, more model choices

Keep authentication and request handling stable while comparing Gemini 3.5 Pro with available Gemini, OpenAI, Anthropic, and other routes.

Compare cost per successful task

Use live route pricing together with token use, retries, latency, and acceptance results instead of choosing from list price alone.

Switch with canary and fallback controls

Move a small share of traffic after validation, keep the previous route available, and roll back without rebuilding a provider-specific integration.

Gemini 3.5 Pro release evidence and alternatives

Follow the status evidence, compare the available Flash route, or start with the current Pro option.

Gemini 3.5 Pro API FAQ

Has Google officially announced Gemini 3.5 Pro?

Yes. Google says Gemini 3.5 Pro is currently testing with partners and will become broadly available when ready.

Is Gemini 3.5 Pro publicly available in the Gemini API?

No. As of August 1, 2026, it is not listed in Google's public Gemini API model catalog, pricing page, or API reference.

Is Gemini 3.5 Pro available on EvoLink?

Not yet. EvoLink will list the route only after upstream access, the request model ID, pricing, route behavior, and a successful real call are verified.

What is the Gemini 3.5 Pro model ID?

No public request model ID is confirmed. Do not infer an ID from this page's URL or hard-code a rumored string in production.

How much will the Gemini 3.5 Pro API cost?

Pricing is not published. This page will show EvoLink's live pricing module after the route and SKUs are approved rather than guessing a price.

Which inputs and tools will Gemini 3.5 Pro support?

Google has not published the public route's input modalities, context limit, tool support, output limit, quotas, or regions.

Is partner testing the same as Early Access?

No. Partner testing is restricted testing. Google has not published a public signup, waitlist, eligibility policy, preview route, or access guarantee.

Which Gemini model can I use now?

Use Gemini 3.1 Pro for the current Pro-family option or Gemini 3.5 Flash for the publicly available 3.5-generation route on EvoLink.

How can I switch quickly after launch?

Keep the model ID configurable, benchmark a fixed task set, add the verified route in shadow mode, move a small canary, and retain a tested fallback before broader rollout.