Skip to main content
Gemini Enterprise Agent PlatformProduct page

Gemini Enterprise Agent Platform Signals

What teams building AI features on Gemini Enterprise Agent Platform report, with every finding tied to its evidence.

Read the findings

What the evidence says

Whose sources count

Practitioner sentiment, all practitioners

−27 Negative from 45 sources that take a side

How this figure is made

Negative overall signal, net 27 points negative

From 41 authors in 40 discussions. Run a pilot on your own prompts to measure output quality and cost per task.

Analyzed
78 total sources
Top praise
Model Choice & Claude Access (10 of 10 sources) See praise evidence
Top concern
Quotas & 429 Errors (10 of 11 sources) See concern evidence

Feb 2025 to Oct 2026.

64 sources from practitioners, by month and sentiment.

Of 64 public accounts, the 45 with a counted stance split 15 positive, 6 mixed and 24 negative. Quotas & 429 Errors is the most raised concern, in 10 sources. All 10 that discuss Model Choice & Claude Access praise it, and teams that keep Claude or Gemini inside Google Cloud for compliance give much of the praise.

Positive, mixed and negative sources

The score counts them as 12 positive, 6 mixed and 23 negative votes, one per author. See How the numbers work.

See the evidence

Below: 4 praise themes, 6 concerns, 3 close to agreement and 1 disagreement.

Findings

Counted for All practitioners, from 64 sources. Change group

What practitioners praise

Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.

  1. Model Choice & Claude AccessAll 10 sources on it praise itReaching Gemini, Claude, and open models through Model Garden on one Google Cloud account.

    Counted for All practitioners.

    1. Mixed

      Rajesh Beri (rajeshberi), author of THE DAILY BRIEF, on X

      Post on X by Rajesh BeriPost on X

      Advises defaulting to Amazon Bedrock and choosing Vertex AI when Gemini is the main model.

      "Default to Bedrock; Vertex if Gemini is your main model…"
      Excerpt, Rajesh Beri

      Published Oct 25, 2026self-described: Summarizing his comparison of Bedrock, Vertex AI and Microsoft Foundry

    2. Positive

      yieldcrv, Hacker News commenter

      Comment on: Ask HN: Did Google kill its enterprise workhorse model?Hacker News comment

      The commenter points to Model Garden on Vertex AI for other models, including ones a team can download and run elsewhere if Google ends access.

      Published Sep 12, 2026self-described: Advice to a team losing access to a Gemini model

    3. Positive

      Shaurya Kethireddy, Lead Member of Technical Staff, Slack

      Slack AI: The Path to Multi-CloudEngineering blog post, Slack Engineering

      Slack added Vertex AI to Slack AI's serving stack in early 2026, for redundancy and for a broader catalog of models. After matching models to features across both clouds, Slack reports about 10% better quality metrics on complex reasoning tasks and about 67% lower latency on high-volume, low-token workloads.

      "~67% reduction in latency for high-velocity, low-token workloads."
      Excerpt, Shaurya Kethireddy

      Published May 28, 2026Slack AI serving infrastructure, a second model cloud beside Amazon Bedrock

    4. Positive

      Philip-J-Fry, Hacker News commenter

      Comment on: Apple's accidental moat: How the "AI Loser" may end up winningHacker News comment

      The commenter's team runs an internal proxy to many models on Vertex AI. The commenter accidentally started using Claude Opus and Sonnet 4 when they meant to use 4.6, and didn't notice until checking the configuration.

      Published Apr 13, 2026self-described: Team with an internal proxy to many models on Vertex AI

    5. Positive

      PaulShin, builder at Markhub, Hacker News commenter

      Comment on: Ask HN: What Does Your Self-Hosted LLM Stack Look Like in 2025?Hacker News comment

      Markhub runs summarization, code generation and creative work on Gemini through Vertex AI, saying the reliability and reasoning are worth the API cost, and keeps small frequent tasks on self-hosted open models.

      Published Jun 9, 2025self-described: Markhub, an AI collaboration product with a hybrid model stack

    6. No opinion stated

      zxspectrum1982, Hacker News commenter

      Comment on: Our decision on Cursor following its acquisition by SpaceXHacker News comment

      The commenter's company now tells staff to use Claude directly through Anthropic or Vertex AI, and Codex through OpenAI, so it skips paying Cursor's token rate.

      Published Aug 29, 2026self-described: Company that directs staff to buy Claude from Anthropic or Vertex AI

    7. Positive

      lenerdenator, Hacker News commenter

      Comment on: Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash CyberHacker News comment

      The commenter's US healthcare IT company runs Claude on Vertex AI. Its customers accept models sourced from the US, and data with PHI or PII must stay in the US, so compliance matters more than the model itself.

      Published Jul 21, 2026self-described: US healthcare IT company running Claude on Vertex AI

    8. Positive

      NitpickLawyer, Hacker News commenter

      Comment on: The US is winning the AI race where it matters most: commercializationHacker News comment

      The commenter says Vertex hosts Claude itself, lets a team choose regions with EU traffic served from Belgium, adds encryption at rest, and keeps Claude inside Google Cloud's FedRAMP High boundary.

      Published May 13, 2026self-described: Claude hosted by Google on Vertex AI

    9. Positive

      fomoz, Hacker News commenter

      Comment on: Accelerating Gemma 4: faster inference with multi-token prediction draftersHacker News comment

      The commenter says paid Gemma 4 on Vertex AI costs about a third of Gemini 3 Flash.

      Published May 6, 2026self-described: App with 5 agents on Gemma 4 31B, 1.5k requests per day each

    10. Positive

      verdverm, Hacker News commenter

      Comment on: Ask HN:Do people configure Claude Code to use other modelsHacker News comment

      The commenter notes that Claude Desktop can use Vertex AI for Claude models at the same price as Anthropic, and calls it more reliable.

      Published May 2, 2026self-described: Pays per token through Vertex AI

    GILD's fact checks, which don't count as sources

    Checked Oct 28, 2026.Google lists partner models from other AI vendors, such as Anthropic Claude, Grok and Mistral AI, as integrated into Agent Platform. Gemini Enterprise Agent Platform models

    Checked Oct 28, 2026.In Agent Studio, the main agent and each local subagent have a Model setting where you choose the model that powers the agent. Design agents in Agent Studio

    Open them in the record
  2. Token Pricing5 of 8 sources on it praise itPer-token prices, free limits, and how they compare with other routes to the same models.

    Counted for All practitioners.

    Positive, 5

    1. Positive

      fomoz, Hacker News commenter

      Comment on: Accelerating Gemma 4: faster inference with multi-token prediction draftersHacker News comment

      The commenter says paid Gemma 4 on Vertex AI costs about a third of Gemini 3 Flash.

      Published May 6, 2026self-described: App with 5 agents on Gemma 4 31B, 1.5k requests per day each

    2. Positive

      Jeremy Longshore, maintainer of claude-code-plugins

      Scaling AI Batch Processing: Enhancing 235 Plugins with Vertex AI Gemini on the Free TierPersonal blog post, DEV Community

      The author ran an overnight Vertex AI Gemini batch that wrote documentation for 235 plugins, spacing calls 90 to 120 seconds apart to stay inside the free limits the author cites, and reports a 100% success rate at no cost.

      Published Mar 25, 2026self-described: Overnight batch job writing documentation for 235 plugins

    3. Positive

      verdverm, Hacker News commenter

      Comment on: Ask HN:Do people configure Claude Code to use other modelsHacker News comment

      The commenter notes that Claude Desktop can use Vertex AI for Claude models at the same price as Anthropic, and calls it more reliable.

      Published May 2, 2026self-described: Pays per token through Vertex AI

    4. Positive

      verdverm, Hacker News commenter

      Comment on: Claudetop: htop for Claude Code sessions (see your AI spend in real-time)Hacker News comment

      The commenter pays per token through Vertex and gets higher limits and quota that grow with spend. Gemini Flash is nearly as good for their work, with less spend and latency.

      Published Mar 14, 2026self-described: Pays per token through Vertex AI for coding work

    5. Positive

      PaulShin, builder at Markhub, Hacker News commenter

      Comment on: Ask HN: What Does Your Self-Hosted LLM Stack Look Like in 2025?Hacker News comment

      Markhub runs summarization, code generation and creative work on Gemini through Vertex AI, saying the reliability and reasoning are worth the API cost, and keeps small frequent tasks on self-hosted open models.

      Published Jun 9, 2025self-described: Markhub, an AI collaboration product with a hybrid model stack

    Mixed or negative, 3

    1. Negative

      Current_Trick6380, r/googlecloud

      429s and slow responses on the EU multi-region endpoint and Priority PayGo is served as standard thereReddit post

      For about 1.5 years the team has seen frequent 429 errors and slow responses on the EU multi-region endpoint; one day gemini-3.7-flash averaged 80 seconds to first token there against 4.5 seconds on the global endpoint. Retries and model fallbacks help a little, Priority PayGo did not go through in the EU, and Provisioned Throughput is too expensive for their volume.

      Published Oct 13, 2026self-described: Team running customer-facing chat applications that need EU data processing

    2. Negative

      arjie, Hacker News commenter

      Comment on: Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash CyberHacker News comment

      The commenter finds Google's model names confusing for pricing, and Vertex, AI Studio, Gemini and Antigravity side by side too confusing to use.

      Published Jul 21, 2026self-described: Choosing among Google's AI platforms and models

    3. Negative

      jdw64, Hacker News commenter

      Comment on: Google is building a Claude Code challenger, Sergey Brin is involvedHacker News comment

      Each time the commenter weighs Vertex AI against alternatives, the different pricing models across Google's AI products leave them unsure which is the standard way to use Google's AI.

      Published Apr 25, 2026self-described: Deciding whether to build on Vertex AI

    Open them in the record
  3. Reliability vs Direct APIs5 of 10 sources on it praise itWhether requests through Agent Platform succeed more often than through the Gemini Developer API or the model vendor's own API.

    Counted for All practitioners.

    Positive, 5

    1. Positive

      verdverm, Hacker News commenter

      Comment on: Ask HN:Do people configure Claude Code to use other modelsHacker News comment

      The commenter notes that Claude Desktop can use Vertex AI for Claude models at the same price as Anthropic, and calls it more reliable.

      Published May 2, 2026self-described: Pays per token through Vertex AI

    2. Positive

      Samuel Colvin, Founder, Pydantic

      Agent Engineering with Pydantic + Graphs: with Samuel ColvinPodcast episode with transcript, Latent Space

      Pydantic's founder says the generative language API behind AI Studio returned 503 errors about 20% of the time in Pydantic AI's tests, while Vertex serves the same API and is much more reliable.

      "So like all of the models fail more often than you might expect, but like that one seems to be particularly likely to fail. But Vertex is the same API, but much more reliable."
      Transcript excerpt, Samuel Colvin, around 28:29 in the episode

      Published Feb 6, 2025Pydantic AI, an agent framework with adapters for Gemini through Vertex and the generative language API

    3. Positive

      junhee916, chatbot operator

      Google AI Studio 503 Errors? Migrated to Vertex AI and Converted 27 Files Instantly!Personal blog post, DEV Community

      After 16 HTTP 503 errors in one day on Google AI Studio, the developer moved the same Gemini model to Vertex AI for its SLA and capacity. The switch meant routing the client calls in 27 files through one factory function behind an environment flag.

      "The only change needed was to switch the genai.Client(api_key=...) calls in 27 files to a get_gemini_client() factory function."
      Excerpt, junhee916

      Published Jun 6, 2026self-described: Solo chatbot service on gemini-3.1-flash-lite

    4. Positive

      Shaurya Kethireddy, Lead Member of Technical Staff, Slack

      Slack AI: The Path to Multi-CloudEngineering blog post, Slack Engineering

      Slack added Vertex AI to Slack AI's serving stack in early 2026, for redundancy and for a broader catalog of models. After matching models to features across both clouds, Slack reports about 10% better quality metrics on complex reasoning tasks and about 67% lower latency on high-volume, low-token workloads.

      "~67% reduction in latency for high-velocity, low-token workloads."
      Excerpt, Shaurya Kethireddy

      Published May 28, 2026Slack AI serving infrastructure, a second model cloud beside Amazon Bedrock

    5. Positive

      PaulShin, builder at Markhub, Hacker News commenter

      Comment on: Ask HN: What Does Your Self-Hosted LLM Stack Look Like in 2025?Hacker News comment

      Markhub runs summarization, code generation and creative work on Gemini through Vertex AI, saying the reliability and reasoning are worth the API cost, and keeps small frequent tasks on self-hosted open models.

      Published Jun 9, 2025self-described: Markhub, an AI collaboration product with a hybrid model stack

    Mixed or negative, 5

    1. Negative

      BoxedEmpathy, Hacker News commenter

      Comment on: AlphaEvolve: Gemini-powered coding agent scaling impact across fieldsHacker News comment

      The commenter sees 429s on Vertex in their product and mostly avoids Google AI because it is unreliable.

      Published May 8, 2026self-described: Own product calling Gemini on Vertex AI

    2. Negative

      stijntonk, Hacker News commenter

      Comment on: AlphaEvolve: Gemini-powered coding agent scaling impact across fieldsHacker News comment

      The commenter wants Gemini 3.x models at general availability with enough capacity to stop the constant 429 errors, and feels Google does not want them building apps for corporate clients on the Vertex API.

      Published May 7, 2026self-described: Team building document-analysis applications for corporate clients on paid Vertex AI accounts

    3. Negative

      aenis, Hacker News commenter

      Comment on: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7Hacker News comment

      The commenter routinely runs into quotas with production workloads on Vertex or Amazon Bedrock, while Claude from Anthropic directly always works.

      Published Apr 18, 2026self-described: Production workloads on Vertex AI and Amazon Bedrock

    4. Negative

      Carlos01, Google AI Developers Forum

      Critical: Persistent 429 Resource Exhausted Error on Vertex AI After Migrating from AI StudioForum post, Google AI Developers Forum

      The developer moved an agent workflow from AI Studio to Vertex AI for production stability, then hit constant 429 Resource Exhausted errors on a paid project that left customers without service.

      Published Mar 17, 2026self-described: Agno agent app hosted on Railway, serving paying customers

    5. Negative

      dabbbulaaax, Google AI Developers Forum

      MALFORMED_FUNCTION_CALL finish reason happens too frequently with vertex AIForum post, Google AI Developers Forum

      The poster gets the MALFORMED_FUNCTION_CALL finish reason far more often on Vertex AI than on the Gemini Developer API, and wants the malformed call returned as a normal response the way other model vendors do.

      Published Jul 12, 2025self-described: Gemini 2.5 Flash function calling through the Google GenAI SDK

    Open them in the record
  4. Compliance & Data Residency4 of 7 sources on it praise itHIPAA and FedRAMP coverage, regional processing, and keeping prompts inside Google Cloud.

    Counted for All practitioners.

    Positive, 4

    1. Positive

      lenerdenator, Hacker News commenter

      Comment on: The obscure trust looming over Anthropic's IPOHacker News comment

      The commenter's employer uses a copy of Claude hosted on Vertex AI, and the commenter would find it odd if Anthropic ended up with the company's data.

      Published Oct 19, 2026self-described: Company in US healthcare IT that uses Claude at work through Vertex AI

    2. Positive

      lenerdenator, Hacker News commenter

      Comment on: Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash CyberHacker News comment

      The commenter's US healthcare IT company runs Claude on Vertex AI. Its customers accept models sourced from the US, and data with PHI or PII must stay in the US, so compliance matters more than the model itself.

      Published Jul 21, 2026self-described: US healthcare IT company running Claude on Vertex AI

    3. Positive

      NitpickLawyer, Hacker News commenter

      Comment on: The US is winning the AI race where it matters most: commercializationHacker News comment

      The commenter says Vertex hosts Claude itself, lets a team choose regions with EU traffic served from Belgium, adds encryption at rest, and keeps Claude inside Google Cloud's FedRAMP High boundary.

      Published May 13, 2026self-described: Claude hosted by Google on Vertex AI

    4. Positive

      amiroo, builder of Yari Timeline, Hacker News commenter

      Comment on: Private and HIPAA Compliant LLM Summarizer for Apple Health's Medical RecordsHacker News comment

      The builders run Gemini on Vertex AI as a HIPAA-compliant model over users' HealthKit medical records, with Gemini's caching and traffic logs turned off.

      Published Aug 3, 2025self-described: Yari Timeline team, an iOS app that summarizes HealthKit medical records

    Mixed or negative, 3

    1. Mixed

      dan000892, Hacker News commenter

      Comment on: Anthropic Subprocessor ChangesHacker News comment

      The commenter says Vertex AI is available inside a FedRAMP High assured workload but not for ITAR, which matters to defense contractors.

      Published Mar 27, 2026self-described: Defense contracting compliance

    2. Negative

      Current_Trick6380, r/googlecloud

      429s and slow responses on the EU multi-region endpoint and Priority PayGo is served as standard thereReddit post

      For about 1.5 years the team has seen frequent 429 errors and slow responses on the EU multi-region endpoint; one day gemini-3.7-flash averaged 80 seconds to first token there against 4.5 seconds on the global endpoint. Retries and model fallbacks help a little, Priority PayGo did not go through in the EU, and Provisioned Throughput is too expensive for their volume.

      Published Oct 13, 2026self-described: Team running customer-facing chat applications that need EU data processing

    3. Negative

      stijntonk, Hacker News commenter

      Comment on: AlphaEvolve: Gemini-powered coding agent scaling impact across fieldsHacker News comment

      The team often must host client workloads in an EU region, which rules out the global endpoint and its likely larger capacity. It once round-robined across several projects to get enough quota and now retries on 429s.

      Published May 7, 2026self-described: Team building document-analysis applications for corporate clients on paid Vertex AI accounts

    GILD's fact checks, which don't count as sources

    Checked Oct 28, 2026.Data at rest stays in the location the customer selects. The global endpoint gives no data residency guarantee; the US and EU multi-region endpoints keep ML processing inside that jurisdiction. Data residency

    Open them in the record

What concerns them

Every concern practitioners raise, most raised first.

  1. Quotas & 429 Errors10 of 11 sources on it raise it as a concernResource exhausted errors, low or zero default quotas, and capacity limits in the regions a team must use.

    Counted for All practitioners.

    Raised as a concern, 10

    1. Negative

      Current_Trick6380, r/googlecloud

      429s and slow responses on the EU multi-region endpoint and Priority PayGo is served as standard thereReddit post

      For about 1.5 years the team has seen frequent 429 errors and slow responses on the EU multi-region endpoint; one day gemini-3.7-flash averaged 80 seconds to first token there against 4.5 seconds on the global endpoint. Retries and model fallbacks help a little, Priority PayGo did not go through in the EU, and Provisioned Throughput is too expensive for their volume.

      Published Oct 13, 2026self-described: Team running customer-facing chat applications that need EU data processing

    2. Negative

      swe_dima, Hacker News commenter

      Comment on: Please don't discontinue Gemini 2.5 FlashHacker News comment

      The commenter says Vertex has a very low quota that cannot be adjusted.

      Published Jul 11, 2026self-described: Calling Gemini through Vertex AI and Cloudflare

    3. Negative

      BoxedEmpathy, Hacker News commenter

      Comment on: AlphaEvolve: Gemini-powered coding agent scaling impact across fieldsHacker News comment

      The commenter sees 429s on Vertex in their product and mostly avoids Google AI because it is unreliable.

      Published May 8, 2026self-described: Own product calling Gemini on Vertex AI

    4. Negative

      stijntonk, Hacker News commenter

      Comment on: AlphaEvolve: Gemini-powered coding agent scaling impact across fieldsHacker News comment

      The team often must host client workloads in an EU region, which rules out the global endpoint and its likely larger capacity. It once round-robined across several projects to get enough quota and now retries on 429s.

      Published May 7, 2026self-described: Team building document-analysis applications for corporate clients on paid Vertex AI accounts

    5. Negative

      stijntonk, Hacker News commenter

      Comment on: AlphaEvolve: Gemini-powered coding agent scaling impact across fieldsHacker News comment

      The commenter wants Gemini 3.x models at general availability with enough capacity to stop the constant 429 errors, and feels Google does not want them building apps for corporate clients on the Vertex API.

      Published May 7, 2026self-described: Team building document-analysis applications for corporate clients on paid Vertex AI accounts

    6. Negative

      aenis, Hacker News commenter

      Comment on: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7Hacker News comment

      The commenter routinely runs into quotas with production workloads on Vertex or Amazon Bedrock, while Claude from Anthropic directly always works.

      Published Apr 18, 2026self-described: Production workloads on Vertex AI and Amazon Bedrock

    7. Negative

      Carlos01, Google AI Developers Forum

      Critical: Persistent 429 Resource Exhausted Error on Vertex AI After Migrating from AI StudioForum post, Google AI Developers Forum

      The developer moved an agent workflow from AI Studio to Vertex AI for production stability, then hit constant 429 Resource Exhausted errors on a paid project that left customers without service.

      Published Mar 17, 2026self-described: Agno agent app hosted on Railway, serving paying customers

    8. Negative

      nostrebored, Hacker News commenter

      Comment on: Gemini CLIHacker News comment

      The commenter consistently gets 429s on Gemini and on Vertex while quotas show neither close to its limits.

      Published Jun 25, 2025self-described: Shipping a feature on Gemini

    9. Negative

      egamirorrim, Hacker News commenter

      Comment on: Google Gemini has the worst LLM APIHacker News comment

      The team writes code that round-robins every region on retries to get past an overloaded Vertex while staying under its quotas. Java dependency resolution through Google's BOM is painful, and the Vertex SDK has no configurable read timeout.

      Published May 4, 2025self-described: Team calling Vertex AI from Java

    10. Negative

      ukuina, Hacker News commenter

      Comment on: Nano Banana ProHacker News comment

      Signing up and getting Claude Sonnet working on Vertex AI took a long chain of steps across AI Studio and Google Cloud: billing, finding the model name and region, and provisioning in two places. The default quota for Sonnet 4.5 was 0 tokens per minute.

      Published Nov 21, 2025self-described: Trying to use Claude Sonnet on Vertex AI from Claude Code

    Discussed without concern, 1

    1. Positive

      verdverm, Hacker News commenter

      Comment on: Claudetop: htop for Claude Code sessions (see your AI spend in real-time)Hacker News comment

      The commenter pays per token through Vertex and gets higher limits and quota that grow with spend. Gemini Flash is nearly as good for their work, with less spend and latency.

      Published Mar 14, 2026self-described: Pays per token through Vertex AI for coding work

    GILD's fact checks, which don't count as sources

    Checked Oct 28, 2026.Standard pay-as-you-go places an organization in usage tiers, each with a prioritized throughput threshold in tokens per minute. Google states that a 429 signals temporary contention for a shared resource. Standard PayGo

    Open them in the record
  2. Naming & Product Sprawl6 of 7 sources on it raise it as a concernConfusion across Vertex AI, AI Studio, Gemini Enterprise, and the Agent Platform rename, including their different pricing models.

    Counted for All practitioners.

    Raised as a concern, 6

    1. Mixed

      bdashdash, Hacker News commenter

      Comment on: Gemini 4 ArgonHacker News comment

      The commenter finds Google's AI offerings scattered, citing the disconnect between AI Studio and Vertex among other overlapping products, and calls working through them as an enterprise customer confusing.

      Published Oct 1, 2026self-described: Google AI user as a consumer and as an enterprise customer

    2. Negative

      ksajadi, Hacker News commenter

      Comment on linking a Google Cloud project to an AI coding CLIHacker News comment

      Had to enable five APIs, buy a Gemini Enterprise subscription and assign it to link a CLI to a Google Cloud project; the CLI still could not find it, and the US$35 month could not be canceled.

      "…product names keep changing (Gemini, Anti-gravity, Vertex, Google AI,...)…"
      Excerpt, ksajadi

      Published Aug 13, 2026self-described: Linked an AI coding CLI to a Google Cloud project

    3. Negative

      arjie, Hacker News commenter

      Comment on: Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash CyberHacker News comment

      The commenter finds Google's model names confusing for pricing, and Vertex, AI Studio, Gemini and Antigravity side by side too confusing to use.

      Published Jul 21, 2026self-described: Choosing among Google's AI platforms and models

    4. Mixed

      derektank, Hacker News commenter

      Comment on: Gemini Code Assist will be shut down on July 17Hacker News comment

      The commenter chose Google Cloud as their organization's primary enterprise AI vendor and struggles to explain how Vertex AI Studio, Gemini Enterprise and Gemini Enterprise Code Assist differ from each other and from consumer Gemini.

      Published Jul 3, 2026self-described: Chose Google Cloud as the organization's primary enterprise AI vendor

    5. Negative

      r_lee, Hacker News commenter

      Comment on: Gemini Code Assist will be shut down on July 17Hacker News comment

      The commenter jokes about the renaming of Vertex AI to Gemini Enterprise Agent Platform, which puts a Claude model under a Gemini-branded platform name.

      Published Jul 3, 2026self-described: Reacting to the Vertex AI rename

    6. Negative

      jdw64, Hacker News commenter

      Comment on: Google is building a Claude Code challenger, Sergey Brin is involvedHacker News comment

      Each time the commenter weighs Vertex AI against alternatives, the different pricing models across Google's AI products leave them unsure which is the standard way to use Google's AI.

      Published Apr 25, 2026self-described: Deciding whether to build on Vertex AI

    Discussed without concern, 1

    1. No opinion stated

      bilarikan, Hacker News commenter

      Comment on: Gemini 3.8 Live and 3.8 Live Extended ThinkingHacker News comment

      The commenter understands the move to Gemini Enterprise Agent Platform as a new name and a focus on agent governance, with no breaking changes from what Vertex AI offered.

      Published Sep 15, 2026self-described: Following the Vertex AI rename

    Open them in the record
  3. Setup & Region ConfigurationAll 5 sources on it raise it as a concernSign-up steps, model access by region, SDK and credential setup, and the extra complexity of the Vertex AI API.

    Counted for All practitioners.

    1. Negative

      That-Preference733, r/googlecloud

      ADK Deployment major headache i faced, has anyone faced the same issueReddit post

      ADK defaults to Vertex AI, and model access then follows the region of the deployed agent: deploying in global failed and us-central1 offered only lower Gemini models. The poster switched the agent to a Gemini API key, which works everywhere.

      Published Sep 27, 2026self-described: Deploying an Agent Development Kit agent to Cloud Run or Agent Platform

    2. Negative

      ksajadi, Hacker News commenter

      Comment on linking a Google Cloud project to an AI coding CLIHacker News comment

      Had to enable five APIs, buy a Gemini Enterprise subscription and assign it to link a CLI to a Google Cloud project; the CLI still could not find it, and the US$35 month could not be canceled.

      "…product names keep changing (Gemini, Anti-gravity, Vertex, Google AI,...)…"
      Excerpt, ksajadi

      Published Aug 13, 2026self-described: Linked an AI coding CLI to a Google Cloud project

    3. Negative

      ukuina, Hacker News commenter

      Comment on: Nano Banana ProHacker News comment

      Signing up and getting Claude Sonnet working on Vertex AI took a long chain of steps across AI Studio and Google Cloud: billing, finding the model name and region, and provisioning in two places. The default quota for Sonnet 4.5 was 0 tokens per minute.

      Published Nov 21, 2025self-described: Trying to use Claude Sonnet on Vertex AI from Claude Code

    4. Negative

      egamirorrim, Hacker News commenter

      Comment on: Google Gemini has the worst LLM APIHacker News comment

      The team writes code that round-robins every region on retries to get past an overloaded Vertex while staying under its quotas. Java dependency resolution through Google's BOM is painful, and the Vertex SDK has no configurable read timeout.

      Published May 4, 2025self-described: Team calling Vertex AI from Java

    5. Mixed

      cubefox, Hacker News commenter

      Comment on: Gemini 3.7 FlashHacker News comment

      The commenter suggests the Gemini API, which is independent of the more complex Vertex AI API, though billing may still need the Google Cloud console.

      Published Aug 13, 2026self-described: Advice on which Gemini API to call

    GILD's fact checks, which don't count as sources

    Checked Oct 28, 2026.Google publishes guides for creating a LangChain agent and a LlamaIndex Query Pipeline agent on Agent Platform Runtime, and lists ecosystem integration through MCP and the Agent-to-Agent protocol. Build with Gemini Enterprise Agent Platform

    Open them in the record
  4. Function Calling FailuresAll 5 sources on it raise it as a concernGemini tool calls on Vertex AI that end with a malformed function call and produce no usable result.

    Counted for All practitioners.

    1. Negative

      swoodily, Google AI Developers Forum

      MALFORMED_FUNCTION_CALL finish reason happens too frequently with vertex AIForum reply, Google AI Developers Forum

      The poster's team gets sporadic failures from malformed function calls and has no such issue running the same workload on OpenAI or Anthropic.

      Published Aug 28, 2025self-described: Workload with function calling also run on OpenAI and Anthropic

    2. Negative

      Richard_Davey, Google AI Developers Forum

      MALFORMED_FUNCTION_CALL finish reason happens too frequently with vertex AIForum reply, Google AI Developers Forum

      The poster saw malformed function calls often for a week; the exact same API call worked about 70% of the time, which points to a server-side error.

      Published Jul 13, 2025self-described: Production app with Gemini function calling

    3. Negative

      dabbbulaaax, Google AI Developers Forum

      MALFORMED_FUNCTION_CALL finish reason happens too frequently with vertex AIForum post, Google AI Developers Forum

      The poster gets the MALFORMED_FUNCTION_CALL finish reason far more often on Vertex AI than on the Gemini Developer API, and wants the malformed call returned as a normal response the way other model vendors do.

      Published Jul 12, 2025self-described: Gemini 2.5 Flash function calling through the Google GenAI SDK

    4. Mixed

      Oren_Ahr, Google AI Developers Forum

      MALFORMED_FUNCTION_CALL finish reason happens too frequently with vertex AIForum reply, Google AI Developers Forum

      The poster lost many hours to the malformed function call error before finding that it appears when a large prompt and chat history confuse the model, with no fault in their own code.

      Published Jul 19, 2025self-described: Chat app with function calling

    5. Negative

      Tomasz_Osinski, Google AI Developers Forum

      MALFORMED_FUNCTION_CALL finish reason happens too frequently with vertex AIForum reply, Google AI Developers Forum

      An older Gemini 2.5 Flash version had avoided the malformed function call errors for the poster, until Google turned that version off.

      Published Jul 15, 2025self-described: Function calling on Gemini 2.5 Flash

    GILD's fact checks, which don't count as sources

    Checked Oct 28, 2026.Agent Registry is a central catalog for discovering, tracking and managing an organization's agents, tools and MCP servers. Gemini Enterprise Agent Platform overview

    Open them in the record
  5. Latency5 of 6 sources on it raise it as a concernSlow responses and long waits for the first token from models on Agent Platform.

    Counted for All practitioners.

    Raised as a concern, 5

    1. Negative

      jumpintheocean, r/googlecloud

      Latency above 5 mins on Gemini Enterprise Agent Platform - DeepSeek V4.1-Flash?Reddit post

      The poster gets response times above 5 minutes from DeepSeek V4.1-Flash, which runs on Agent Platform as a Model Garden model as a service.

      Published Oct 21, 2026self-described: Calls to a Model Garden model as a service

    2. Negative

      Current_Trick6380, r/googlecloud

      429s and slow responses on the EU multi-region endpoint and Priority PayGo is served as standard thereReddit post

      For about 1.5 years the team has seen frequent 429 errors and slow responses on the EU multi-region endpoint; one day gemini-3.7-flash averaged 80 seconds to first token there against 4.5 seconds on the global endpoint. Retries and model fallbacks help a little, Priority PayGo did not go through in the EU, and Provisioned Throughput is too expensive for their volume.

      Published Oct 13, 2026self-described: Team running customer-facing chat applications that need EU data processing

    3. No opinion stated

      estherarribas, GitHub repository owner

      feat(fraud): Asynchronous AI fraud evaluation via event queue and low-latency cacheGitHub issue

      The issue proposes moving fraud checks off the request path because Vertex AI response spikes of 800 ms to 2.5 seconds block client payment calls at peak traffic.

      Published Sep 29, 2026self-described: Payment fraud check that calls Gemini during each HTTP request

    4. No opinion stated

      mdproctor, casehubio/agency contributor

      feat: local LLM via MTPLX + Qwen3 32B: eliminate Vertex AI network dependencyGitHub issue

      The issue plans to replace Haiku on Vertex AI with a local model because the 1.5 to 3 second model call is 80 to 90% of the avatar pipeline's time, keeping a runtime switch between Vertex and local.

      Published Sep 4, 2026self-described: Voice avatar pipeline in the casehubio agency project

    5. Negative

      egamirorrim, Hacker News commenter

      Comment on: Google Gemini has the worst LLM APIHacker News comment

      The team writes code that round-robins every region on retries to get past an overloaded Vertex while staying under its quotas. Java dependency resolution through Google's BOM is painful, and the Vertex SDK has no configurable read timeout.

      Published May 4, 2025self-described: Team calling Vertex AI from Java

    Discussed without concern, 1

    1. Positive

      verdverm, Hacker News commenter

      Comment on: Claudetop: htop for Claude Code sessions (see your AI spend in real-time)Hacker News comment

      The commenter pays per token through Vertex and gets higher limits and quota that grow with spend. Gemini Flash is nearly as good for their work, with less spend and latency.

      Published Mar 14, 2026self-described: Pays per token through Vertex AI for coding work

    Open them in the record
  6. Surprise Bills & Billing Support4 of 5 sources on it raise it as a concernBills larger than expected from deployed endpoints, long jobs, or features billed apart from tokens, and billing support that would not adjust them.

    Counted for All practitioners.

    Raised as a concern, 4

    1. Negative

      sheep1165, cofounder, r/googlecloud

      Got a C$71K Google Cloud bill overnight. Any advice?Reddit post

      A Vertex AI job cost the startup about C$75K in 14 hours after its credits ran out mid-run. Because billing data arrived late, charges kept appearing after the team shut everything down, and billing support rejected a one-time adjustment.

      Published Oct 18, 2026self-described: Early-stage startup whose credits ran out during an overnight job

    2. Negative

      Spirited_Maximum762, student, r/googlecloud

      Google Cloud charges I did not knowingly authorize were sent to collections: how can I get a manual review?Reddit post

      A student experimenting with Vertex AI left resources provisioned and ran up about 5,974 INR, mostly from Cloud Spanner and a small amount from Vertex AI. The billing assistant would not reverse it or reach a human, and the debt went to collections.

      Published Sep 17, 2026self-described: Student experimenting with Vertex AI

    3. Negative

      Appropriate-Two-447, solo founder, r/googlecloud

      $8.8k for a Model Garden "one-click deploy" GPU endpoint that served zero requests. Billing support refused to escalate. Case 74999163.Reddit post

      Clicking Deploy on a partner model in Model Garden provisioned a dedicated GPU node with no scale to zero and no cost confirmation. It billed $8,817 over 62 days without serving a request, and billing support declined to escalate. The founder now keeps budgets and alerts and still plans to move fully to Google Cloud.

      Published Sep 11, 2026self-described: One-person company running its products on Cloud Run

    4. Negative

      junhee916, solo developer of aicoreutility.com

      Vertex AI Grounding Cost Gap: Diagnosing the Missing $1300 on My Solo VMPersonal blog post, DEV Community

      The developer's app dashboard showed about 400,000 KRW of Vertex AI spend for a month while the Google Cloud bill came to about 1,740,000 KRW. The gap was Google Search grounding, which Vertex AI bills per request apart from tokens and which the app's own usage logs did not track.

      Published Jun 7, 2026self-described: Solo AI product on one small VM, chat grounded with Google Search

    Discussed without concern, 1

    1. No opinion stated

      franciscobispo, LiteLLM proxy user

      [Bug]: Vertex AI Gemini + explicit context caching - usage.prompt_tokens intermittently reports only the fresh (non-cached) token count instead of the total, when the request body is repeated identicallyGitHub issue

      With identical repeated requests, 3 of 12 and then 1 of 12 responses through the LiteLLM proxy reported prompt tokens without the cached portion, which under-reports cost for anyone billing from that field. The author suspects the proxy, since LiteLLM reads Vertex's usage metadata directly.

      Published Sep 1, 2026self-described: LiteLLM proxy on Kubernetes in front of Vertex AI Gemini

    Open them in the record

Where the evidence agrees

Statements this group's sources agree on, then the ones close to agreement.

Close to agreement: each needs 13 supporting sources

  1. Below threshold

    Teams keep another region, project, model, or cloud ready so that 429s or slow responses on one endpoint do not stop their product.

    7 supporting sources
  2. Below threshold

    Teams move model calls onto Agent Platform for Google Cloud IAM and billing, an SLA, and compliance terms that an AI Studio API key does not give them.

    5 supporting sources, 1 contradicting
  3. Below threshold

    Builders who received bigger bills than they expected found the cost late: a deploy kept a GPU running, billing data arrived hours after a job, or a charge sat outside their token tracking.

    5 supporting sources

Where it disagrees

Questions the sources split on, with the count on each side.

  • Evidence remains mixed

    Should a team call Gemini through Agent Platform or through the Gemini Developer API?

    • Agent Platform, 2 sources

      Some moved to Vertex AI after 503 or 429 errors on AI Studio, for its reliability, SLA, IAM, and billing.

    • Gemini Developer API, 3 sources

      Others keep or return to an API key because the Vertex AI route needs more setup, ties model access to a region, or fails tool calls more often.

The evidence

Whose experience this is

The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.

Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Teams and leaders have 13 accounts; GILD prints their sentiment from 20.

  • Teams and technical leaders

    23 sources. These accounts focus on compliance, regional processing, model access, and capacity, from teams and companies running Agent Platform (formerly Vertex AI) in their products.

  • Individual builders

    41 sources. These accounts focus on quotas, setup, bills, and day-to-day reliability for developers building on Agent Platform on their own.

  • All practitioners

    64 sources. This gives the broadest read, but combines solo projects with production teams that can reach different conclusions.

64 sources from practitioners, by the context they work in. Filled rows count for this group.

  1. Individual builderDevelopers building on the platform on their own41 sources, counted here

    Emphasizes Quotas, setup friction, and surprise bills

  2. Small product team2 to 10 engineers, or an unnamed startup team8 sources, counted here

    Emphasizes Capacity in EU regions and retry workarounds

  3. Product or platform team11 to 50 engineers, or a named company's team8 sources, counted here

    Emphasizes Model choice and a second serving cloud

  4. Technical leadershipLeaders setting model and platform choices across teams3 sources, counted here

    Emphasizes Reliability against direct APIs, product naming, and large bills

  5. Organization-wideEnterprise or company-wide AI platform4 sources, counted here

    Emphasizes Running Claude inside Google Cloud for compliance

What changes with scale. Individual builders focus on 429 errors, setup across AI Studio and Google Cloud, and bills they did not expect. Team and company accounts focus on compliance, keeping data in a region, and reaching Claude and Gemini under one Google Cloud account, and newer ones on keys that run up large bills.

Where the sources come from

Where this group's sources were published.

Counted for All practitioners, from 64 sources. Change group

78 sources for this group, 14 of them documentation

  • Developer Communities55, 71% of 78 sources
  • Product Documentation14, 18% of 78 sources
  • Engineering Blogs & Reviews8, 10% of 78 sources
  • Podcasts, Talks & Videos1, 1% of 78 sources

Older evidence stays when it still applies. Accounts tied to retired models, the earlier quota system, or older function-calling behavior remain in the history with a Needs a recheck label.

See sources by origin

The record

Who each source is, how it knows, whether it still applies and what it counts toward.

Newest first, on its own page. Every count above opens its sources there.

Read all 78 sources

About this read

What changed, and how we count

What changed

  • The evidence base uses public English-language sources dated 2025 or later. Each source links to the original page and names the author and publication date.
  • The page shows a finding when at least 5 sources from 3 different authors discuss it. A disagreement needs at least 2 sources on each side.
  • Accounts about the Gemini Developer API or AI Studio alone are left out. Accounts that compare it with Vertex AI or Agent Platform stay, and form the disagreement on which route to use.
  • Google's own customer quotes in its launch post are left out, and an account from a Google employee is listed with that reason and counts toward no figure. Agent memory, grounding, and model retirement accounts are not shown as findings because none reached 5 sources from 3 authors.
  • GILD checks each documentation page against current Google Cloud documentation and pricing.
  • Oct 28, 2026: adds 16 records. From research records: a Vertex AI Memory Bank post on X, two Hacker News accounts that count (a move from Bedrock quotas to Vertex and Gemini, and a setup ordeal), a Google employee's routing advice, Rajesh Beri's three-cloud analysis and post, and the Fin and Zalando engineering write-ups, with quotes. From r/googlecloud through the Arctic Shift archive: 8 posts on EU capacity, a US$195k stolen-key bill, quota refusals, account restrictions and agent tooling. Only records with a checked author count; the rest are listed with their reason. The Hub gains 7 Operator Insights, among them Fin, Zalando and MOVILIXA.

Method

A running review of what teams building AI features on Gemini Enterprise Agent Platform report, from individual builders to company-wide platforms. Each finding links to its sources, and each conflict shows both sides.

Counts cover only the sources GILD reviewed.

Who counts

Teams and technical leaders
Small product team, Product or platform team, Technical leadership, Organization-wide
Individual builders
Individual builder
All practitioners
Everyone in the teams and leaders and individual builders groups

Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.

How the numbers work

  • Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among technical leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
  • Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all practitioners read −13 mixed (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
  • Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read −13 Mixed; with one vote per author it reads −29 Negative. No evidence changed.
  • Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
  • Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
  • Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
  • Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
  • Disagreements. The count on each side. GILD names no winner and gives no share of all users.
  • Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.

Labels on a source

A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.

Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.

Flagged for a recheck, of the sources that take a side: teams and leaders 2 of 13, individual builders 8 of 32, all practitioners 10 of 45.

Limits

  • These figures count reviewed public accounts and do not form a representative survey of Agent Platform customers. The record holds 64 practitioner records and 14 documentation pages. Hacker News supplies 30 of the practitioner records, r/googlecloud 14, the Google AI Developers Forum 6, DEV Community 4, GitHub issues 3, X 2, and Engineering at Slack, Zalando Engineering, Fin AI Research, Rajesh Beri's analysis and the Latent Space podcast 1 each. GILD searched for accounts of quotas, Claude access, moves from AI Studio, and billing, and r/googlecloud posts are help requests, which tilts the record toward problem reports. Records whose authors' ties to Google GILD has not checked are listed and count toward no figure.
  • Google renamed Vertex AI to Gemini Enterprise Agent Platform on April 22, 2026, and most accounts use the older name. Each source records the model, endpoint, and feature its author names; those details vary. Accounts tied to retired models, an earlier quota system, or older function-calling behavior carry the Needs a recheck label.

Every count, and the sources behind it

16 findings for 3 groups

Each row opens its sources for the group you are reading.

FindingTeams and technical leadersIndividual buildersAll practitionersSources
Current readCurrent sentiment7 positive, 1 mixed, 5 negative8 positive, 5 mixed, 19 negative15 positive, 6 mixed, 24 negativeSources
PraiseModel Choice & Claude Access5 of 5 positive5 of 5 positive10 of 10 positiveSources
PraiseReliability vs Direct APIs3 of 4 positive (under the minimum)2 of 6 positive5 of 10 positiveSources
PraiseCompliance & Data Residency3 of 5 positive1 of 2 positive (under the minimum)4 of 7 positiveSources
PraiseToken Pricing1 of 2 positive (under the minimum)4 of 6 positive5 of 8 positiveSources
ConcernQuotas & 429 Errors4 of 4 raise it (under the minimum)6 of 7 raise it10 of 11 raise itSources
ConcernSurprise Bills & Billing Support1 of 1 raise it (under the minimum)3 of 4 raise it (under the minimum)4 of 5 raise itSources
ConcernNaming & Product Sprawl1 of 1 raise it (under the minimum)5 of 6 raise it6 of 7 raise itSources
ConcernLatency2 of 2 raise it (under the minimum)3 of 4 raise it (under the minimum)5 of 6 raise itSources
ConcernSetup & Region Configuration1 of 1 raise it (under the minimum)4 of 4 raise it (under the minimum)5 of 5 raise itSources
ConcernFunction Calling Failures0 of 0 raise it (under the minimum)5 of 5 raise it5 of 5 raise itSources
ConsensusChosen for Google Cloud controls4 supporting (under the minimum)1 supporting, 1 contradicting (under the minimum)5 supporting, 1 contradicting (below threshold)Sources
ConsensusKeep a second route4 supporting (under the minimum)3 supporting (under the minimum)7 supporting (below threshold)Sources
ConsensusSet budgets before experiments1 supporting (under the minimum)4 supporting (under the minimum)5 supporting (below threshold)Sources
DisagreementShould a team call Gemini through Agent Platform or through the Gemini Developer API?Agent Platform 1, Gemini Developer API 0 (under the minimum)Agent Platform 1, Gemini Developer API 3 (under the minimum)Agent Platform 2, Gemini Developer API 3Sources
Current readEvidence mix37 sources55 sources78 sourcesSources

Fact checks

GILD's checks of claims against official documentation, kept apart from the source counts.