Applied Use Cases

Applied Use Cases on Google Cloud are practical, end-to-end generative AI patterns that combine Gemini models, Vertex AI, Agent Platform, BigQuery, embeddings, search, speech, evaluation, and tuning services to solve domain workflows. The notebooks emphasize implementation mechanics: authentication, IAM, data preparation, model orchestration, evaluation, deployment, and cleanup.

Synthesized across 88 notebooks. See the source pages under Notebooks below for line-level grounding.

This area is less about isolated prompting and more about wiring generative models into real systems: agents with tools and memory, analytics agents over BigQuery or Looker, RAG over documents or code, BigQuery AI functions, vector search, speech generation, image generation, and multimodal analysis.

Most workflows start from a Google Cloud project with billing, API enablement, authentication, project and location configuration, and precise IAM. The recurring engineering pattern is to prepare trustworthy context, call Gemini or embedding models through the right surface, constrain outputs with schemas or tools, persist intermediate results, and verify behavior with evaluation or inspection.

The material repeatedly treats notebooks as prototypes, not finished production systems. Productionization requires deterministic settings where appropriate, explicit permissions, retries and polling for long-running jobs, cost cleanup, managed retrieval or indexing services at scale, and careful handling of preview, allowlisted, regional, or quota-sensitive features.

Canonical workflow

  1. Define the use case, data sources, output shape, and whether the workflow needs agents, RAG, BigQuery SQL, speech, image generation, tuning, or evaluation.
  2. Prepare the Google Cloud environment: set PROJECT_ID and LOCATION, authenticate, enable required APIs, configure billing, and grant least-privilege IAM to users, service accounts, and BigQuery connections.
  3. Prepare data and context: load documents, tables, logs, code, images, audio, examples, glossary terms, golden queries, memory topics, or tool specifications as required by the workflow.
  4. Select the appropriate model and API surface, such as Gemini through Vertex AI or google-genai, embeddings, Text-to-Speech, Vertex AI Agent Engine, Gemini Data Analytics, BigQuery AI functions, Vector Search, or Memory Bank.
  5. Prototype the core call path with structured prompts, response schemas, function declarations, retrieved context, deterministic generation settings when needed, and explicit parsing/error handling.
  6. Persist and inspect intermediate outputs such as generated fields, embeddings, memories, summaries, artifacts, evaluation rows, BigQuery tables, GCS files, or vector indexes before building downstream steps.
  7. Evaluate and iterate using task-specific metrics, row-level explanations, model comparisons, retrieval quality checks, tuned-vs-base comparisons, or manual inspection of generated outputs.
  8. Operationalize cautiously: deploy agents or indexes, poll long-running operations, add retries/backoff, preserve IAM policies, monitor logs, and clean up billable resources when finished.

Best practices

See Applied Use Cases - Best Practices for the full distilled guide.

  • Start every notebook workflow by validating project, billing, API enablement, authentication, quota project, location, and required IAM roles before making model or service calls.
  • Use explicit system instructions, domain context, examples, glossary terms, golden queries, topic descriptions, and tool instructions so the model has the business and data context needed for reliable behavior.
  • Constrain model outputs with response schemas, JSON MIME types, OpenAPI-style function parameters, typed BigQuery AI functions, or output_schema when downstream code must parse or query the result.
  • Test tool functions, retrieval calls, BigQuery queries, and local agent behavior directly before wiring them into deployed agents, graphs, or multi-step orchestration.
  • Use low temperature or fixed seeds where the workflow needs repeatable routing, classification, tool arguments, search-agent behavior, or evaluation outputs, while still accounting for possible variation.
  • Ground answers in retrieved or connected data rather than pretrained knowledge for domain-specific workflows, and keep metadata such as page, chunk, source document, filename, or table context with retrieved content.

Key models & APIs

  • gemini-2.5-flash, gemini-2.0-flash, gemini-3.5-flash, gemini-2.0-flash-live-preview-04-09, gemini-2.5-flash-image-preview, text-embedding-005, gemini-embedding-001, multimodalembedding@001, lyria-3-clip-preview, lyria-3-pro-preview, Chirp 3 Instant Custom Voice, text-bison@001, claude-3-haiku@20240307, TimesFM, Vertex AI API and Google Gen AI SDK, Vertex AI Agent Engine and Managed Agents API, Vertex AI Memory Bank, Gemini Data Analytics DataA2AService, HTTP API, and A2A SDK, Agent Platform Vector Search and Vector Search 2.0, BigQuery AI functions including AI.GENERATE, AI.GENERATE_TABLE, AI.SCORE, AI.CLASSIFY, AI.IF, AI.GENERATE_BOOL, AI.GENERATE_INT, and AI.GENERATE_DOUBLE, BigQuery ML functions including ML.GENERATE_TEXT, ML.GENERATE_EMBEDDING, VECTOR_SEARCH, ML.DESCRIBE_DATA, ML.EVALUATE, ML.CENTROIDS, and ML.PREDICT, Vertex AI Search and Discovery Engine, Cloud Text-to-Speech API, Cloud Storage, Document AI, Vertex AI EvalTask and Rapid Evaluation, LangChain, LangGraph, CrewAI, Phoenix, and Gradio

Notebooks (88)

Agents & ADK (7)

Audio (4)

Embeddings & Vector Search (4)

Gemini (60)

Open Models (5)

Vertex AI Search (7)

Vision (1)


Part of the Generative AI Google Brain · Applied Use Cases - Best Practices