Skip to main content
A Brand Agent is a commercial entity’s service that participates in AIP - responding to ContextRequests with canonical Bid payloads, and optionally accepting session handoffs for task execution in delegate mode.
Responses must be submitted within the auction window, which is derived from the platform’s latency budget. Typically 100-200ms. Late responses are ignored.
Recommend mode: Your content is integrated into the AI response. No session transfer. Delegate mode: You receive a session handoff and execute a task on the user’s behalf. You can support one or both modes.
The Operator sends signed callbacks for lifecycle events (exposure_shown, interaction_started, delegation_started, task_completed). Brand Agents verify event hashes to track performance.
No. Brand Agents receive only anonymized intent context via ContextRequests. In delegation, context is scoped by context_scope and never includes raw user data or identifiers.
Yes. ContextRequests include the canonical upstream message_id for traceability, along with the operator-generated context_id. Brand Agents should use context_id as the auction identifier and treat message_id as the upstream per-turn trace key.
Only the highest-value event per serve_token is settled. If a user completes a task (CPA), that is the settled amount. Settlement is debited automatically from the Brand Agent’s wallet during periodic settlement.
Brand Agents that support delegation must: accept session initiation, respect context scope boundaries, provide a functional task completion experience, submit task_completed events, and handle timeouts gracefully. The Operator records delegation_started after consent and session initiation.