Search⌘ K
AI Features

The Gemini Enterprise Agent Platform

Explore the roles and responsibilities of Gemini platform components such as Model Garden, Agent Studio, Gemini Enterprise app, and Agent Runtime. Understand how these elements support model inference, application execution, and user interaction in deploying AI-powered services. Learn to trace request flows, evaluate deployment claims, and distinguish between development and production architectures.

A deployment handoff for a document-summarization service lists Model Garden, Agent Studio, the Gemini Enterprise app, and Agent Runtime (formerly Vertex AI Agent Engine), but provides no evidence that the application is ready for deployment.

The expected workflow lets a user submit document ID D-18 and receive a summary. However, the handoff does not identify the application component responsible for retrieving the document and invoking the model.

Listing four platform products does not explain how a request moves through the application. This lesson explains the role of each platform component and traces how the user interface, application runtime, document retrieval, and model inference work together.

Who uses each surface?

First, identify the purpose of each platform component and when it is used. Model discovery, application development, user interaction, and runtime execution serve different purposes, even when the tools belong to the same platform.

In this lesson, an architectural surface refers to an interface or environment used by developers, users, or applications to perform a specific operation. A developer comparing available models uses a development interface, while a deployed application invokes a model through a runtime API. Both operations belong to the application lifecycle, but model discovery is not necessarily part of the production request path.

Before examining the proposed deployment architecture, classify the four products named in the handoff by their primary responsibilities.

Roles Before Request Hops
Handoff label or follow-up question

Agent Runtime

Model Garden

Gemini Enterprise app

Agent Studio

Custom application process

Separate question: What essential implementation fact is still missing?

Role or missing implementation fact

Enterprise end-user application

Executes the deployment's code: checks access, reads D-18, calls the model

Catalog for model discovery, testing, and deployment

Development interface

The document-summary application process and where it runs

Managed agent execution

Start with all matches empty. Match each handoff label to its role. Explicitly leave Custom application process unmatched: none of the four product labels names that process. Consider and reject these distractors: 'Model Garden → serves production inference' and 'Gemini Enterprise app → runtime host'. Then answer the separate question on the final card: Which essential implementation fact does the list still lack?

Do you find this helpful?

The missing item is the customer’s application process: the deployed code that receives D-18, checks access, reads its content, and constructs the inference request.

What the platform encloses

Gemini Enterprise Agent Platform (formerly Vertex AI) names the managed platform context spanning model and agent capabilities. It is an enclosing product context rather than the name of a particular model, end-user application, or SDK import. Its model offerings include Google first-party, partner, and open-weights models.

Resolve five placement fields for the document-summary service. The baseline answers below name the stated architecture; deployment evidence must supply its concrete service configuration and application identity.

Document Summary Placement Reference
FieldQuestionBaseline answer

host

Where does the application's code execute?

Agent Runtime.

model access

Does the selected model use a managed API or require endpoint deployment?

Gemini managed API; no customer model endpoint deployment.

inference surface

Where does the application send document text for inference?

Configured Gemini managed API.

data access

Who checks permission and reads D-18?

Application checks trusted allowed IDs before reading the document store; concrete workload identity remains to be recorded.

entry point

Which service accepts the custom UI's request?

Document-summary application on Agent Runtime.

Do you find this helpful?

A denied document read and a failed inference request involve different dependencies, even under the same platform umbrella.

Place the named surfaces

Model Garden provides a catalog for discovering, evaluating, and accessing Google, partner, and open-source models, with deployment options that depend on the selected model. Selecting a model from the catalog does not establish runtime access. Check its model card, supported interfaces, and access requirements before integrating it into the application.

Agent Studio supports agent development, while the Gemini Enterprise app provides an interface through which enterprise users can interact with available agents and AI capabilities. Agent Runtime provides managed infrastructure for running ...