back to library
UCP GOOGLE RETAIL ACP overview →

UCP gateway — interactive walkthrough

Google Search (or any UCP-speaking agent) calls a grocer endpoint. The endpoint is hosted in the grocer's own GCP project; Vertex AI inference, Vector Search lookups, and BigQuery scans bill to them. Step through the five exchanges below — watch which services light up, inspect the UCP envelope, and notice the intelligence_source metadata field that attributes the brains back to Delectable's food graph.

Step
auto-play
Live request flow
Calling agent (off-tenant)

Google Search agent

UCP/1.0 client · sends POST /ucp/v1/agent
Customer GCP project · "giant-eagle-commerce"
GCP CONSUMPTION

UCP gateway (Cloud Run)

/ucp/v1/agent · /.well-known/ucp
RUNNING

BigQuery

inventory · prices · products · embeddings

Vertex AI Gemini

inference for ranking, cart build, meal plan

Vector Search

product + shopper context embeddings

Secret Manager

UCP bearer · Delectable SaaS API key
Delectable SaaS callback (separate tenant)

Delectable food-graph API

global food intelligence · dietary equivalents · meal templates
BRAINS
No shopper PII crosses this boundary — only product-level intelligence queries.
Step 1 of 6
find_products

Google Search agent looks up products

UCP REQUEST POST /ucp/v1/agent 

      


      

        

          UCP RESPONSE
          200 ok
        

        

        

          result payload
          

        

      

    

  


  
  

    

      
FSR magnet — cumulative GCP consumption (customer billing)

      Updates as you step through the demo
    

    

      

        
BigQuery scans

        
0

        
 

      

      

        
Vertex AI calls

        
0

        
 

      

      

        
Vector Search queries

        
0

        
 

      

      

        
Cloud Run requests

        
0

        
 

      

      

        
Delectable SaaS callbacks

        
0

        
 

      

    

    

      Each request can fan out to multiple GCP services in the grocer's project — that's the FSR consumption pattern.
      Cloud Run + BigQuery + Vertex AI + Vector Search + Secret Manager + Cloud SQL all line up under the customer's billing account.
    

  


  
  

    

      

        
Beyond Google — one gateway, every agentic channel

        
Shoppers buy from more than Google.

      

      CHANNEL EXTENSION
    

    

      Google Search is the loudest UCP caller, but agentic purchase intent is fragmenting across surfaces.
      The same hybrid-tenant gateway answers any UCP-speaking client — LLM chats, social-platform agents,
      a grocer's own composable storefront. Same code, same Terraform bundle, same GCP consumption attribution.
    


    

      

        
🔍

        
Google Search

        
UCP/1.0 client · channel:google-search

      

      

        
💬

        
LLM chat (Claude, Gemini, ChatGPT)

        
MCP tools · channel:llm-chat

      

      

        
🎞️

        
Social platforms
(TikTok, Instagram, YouTube)

        
Shop-this-video agents · channel:tiktok-shop, ig-shop, yt-shop

      

      

        
🛒

        
Grocer's own storefront

        
Composable social experience · channel:owned-web

      

    


    

      

        
What's the same

        
    
          
  • Same Cloud Run gateway service, deployed once per grocer.
    • 
          
  • Same UCP request/response envelope — just a different channel attribution field.
    • 
          
  • Same Vertex AI + BigQuery + Vector Search fan-out — all bills the grocer's project.
    • 
          
  • Same privacy boundary — shopper PII stays in the customer tenant.
    • 
        

      

      

        
What's new for social channels

        
    
          
  • Three new UCP intents: shop_creator_post, surface_trending, video_to_products.
    • 
          
  • UCPRequest carries a channel + creator_id + content_id for attribution.
    • 
          
  • A commission webhook fires when a UCP-driven cart converts — payout flows back to the originating channel/creator.
    • 
          
  • The grocer's composable social storefront becomes a first-party UCP caller, not just a third-party one.
    • 
        

      

    


    

      
        

          
👟

          

            
SHOPPER VIEW

            
Social Shopper journey →

            
Open Persona Studio with the Social Shopper preselected. Watch every tab (home, category, product, cart) fire its real UCP payload alongside the shopper UI.

          

        

      
      
        

          
📱

          

            
LIVE PRODUCT

            
Composable Social Experience →

            
Walk through the actual shopper-facing storefront — shoppable videos, creator spotlights, trending signals, AI assistant, CMS slot composition.

          

        

      
      

        
SHIPPED

        
Social-channel A2A extension

        
3 new UCP intents, channel attribution on the request envelope, attribution ledger (Postgres-backed), commission webhook (push + pull, HMAC-signed). 212 tests passing. See commerce/intake/SOCIAL-COMMERCE-CHANNELS.md.

      

    

  


  
  

    

      
PROTOCOL

      
Five UCP exchanges

      
Typed request/response over a stable envelope. Discovery at /.well-known/ucp. Calling agent never sees the underlying service shapes.

    

    

      
FSR MAGNET

      
All consumption in the customer's billing

      
Cloud Run, BigQuery, Vertex AI, Vector Search, Secret Manager, Cloud SQL — every box that lit up bills the grocer's project, not Delectable.

    

    

      
PRIVACY

      
Shopper data never leaves the VPC

      
Only product-level intelligence queries cross to Delectable SaaS — loyalty IDs, transactions, and store-level inventory stay in the grocer's tenant.

    

  


  
  

    
What's behind this demo

    

      

        code
        
UCP gateway + dispatcher + tests

        commerce/src/commerce/protocols/ucp.py
      

      

        reference app
        
Cloud Run image that hosts the gateway

        commerce/examples/ucp_gateway/
      

      

        terraform
        
Hybrid-tenant deploy: Cloud Run + BQ + Vector Search + pgvector

        commerce/deploy/customer-tenant/
      

      

        payouts
        
Attribution ledger + commission webhook (push + pull, HMAC-signed, Postgres-backed)

        commerce/src/commerce/payouts/
      

      

        merchant center
        
PIM → conversational-attributes feed transform

        commerce/src/commerce/merchant_center/
      

      

        fsr materials
        
One-pager + pitch deck outline

        commerce/intake/google-retail-pitch/
      

      

        acp context
        
The full ACP protocol surface (A2A + MCP + A2UI)

        acp-overview.html →