Skip to main content
Start a conversational session with a brand agent. The host platform invokes this task when a user expresses interest in engaging with a brand.

Request

Offering Token

If a host performed a si_get_offering lookup before initiating, include the token for session continuity:
The token lets the brand agent know exactly what products were shown to the user (and in what order). This enables natural conversation flow:
  • User sees: “Nike Pegasus (89),AirMax(89), Air Max (129), Vomero ($139)”
  • User says: “Tell me more about the middle one”
  • Brand agent resolves “middle one” → Air Max via the token’s stored context

Identity Object

When consent_granted is true: When consent_granted is false:

Supported Capabilities Object

Declares what the host platform can render:

Response

Response Object

Example

Request

Response

Key Points

  1. Context is a conversation handoff - The host tells the brand agent what the user needs. The brand agent responds naturally, continuing the conversation.
  2. Brand looks up loyalty data - If Jane’s email is recognized, Delta retrieves her SkyMiles status automatically. Hosts don’t store loyalty numbers.
  3. offering_id is brand-specific - The brand interprets this reference to apply promotions, discounts, or loyalty rewards. Hosts pass it through without needing to understand offering semantics.
  4. Capability negotiation - The response includes negotiated_capabilities showing what features this session can use (intersection of brand and host capabilities).
  5. Clear PII with explicit consent - When consent_granted is true, actual email/name are passed (not hashed). This is a direct, consented handoff.