> ## Documentation Index
> Fetch the complete documentation index at: https://agenticintentprotocol.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Platforms

> How AI platforms integrate with AIP to govern commercial participation and deliver outcomes.

AI Platforms are user-facing applications or interfaces where natural language intent is expressed. AI Platforms submit this intent to an AIP Operator, render recommendations, manage delegation consent, and track lifecycle events.

In the canonical wire contract, platforms send `message_id` as the canonical per-message auction identifier.

Within AIP, AI Platforms are the protocol's entry point  -  they surface intent and deliver outcomes, while all governance, selection, and settlement processes are handled by the Operator.

***

## What is a platform?

A **Platform** is an application, interface, or agentic environment that:

1. **Receives user intent**
   AI Platforms capture user queries, commands, or questions expressed in natural language.

2. **Emits a `PlatformRequest` (AIP canonical request format) to an AIP Operator**
   The Operator evaluates participation eligibility, derives a ContextRequest, then handles selection and mode determination.

3. **Renders recommendations (recommend mode)**
   AI Platforms display operator-returned recommendations using protocol-standard formats (weave, tail, or product card).

4. **Manages delegation consent (delegate mode)**
   AI Platforms present delegation offers to users, collect consent, and relay that consent to the Operator for delegated session initiation.

5. **Tracks and forwards signed events**
   AI Platforms report participation and interaction events using the operator SDK, ensuring serve-token integrity and attribution.

6. **Receives payouts for verified events**
   Operators credit platforms for valid outcomes based on AIP settlement rules.

***

## Examples of platforms

Examples of platforms include:

* AI assistants and copilots
* Chat-based search interfaces
* Browsers with conversational or agentic UI
* Voice assistants
* Productivity applications with embedded AI
* Messaging applications with AI features
* Browser extensions or agent runtimes
* Augmented reality (AR) and virtual reality (VR) environments with conversational interfaces
* Autonomous multi-agent environments

If a system can detect a user request and deliver a participation outcome, it can be a Platform in AIP.

***

## Platform responsibilities

### AI Platforms MUST

* Integrate with an operator through the canonical AIP APIs and event contracts
* Maintain a session identifier for each user conversation
* Display transparency labels for commercial participation
* Ensure accurate event propagation
* Provide `latency_budget_ms` in PlatformRequest to specify the selection timing window
* Present delegation offers clearly and collect explicit user consent before handoff
* Make clear when the user is entering a brand-agent-managed delegated task flow

### AI Platforms MAY

* Use operator-provided SDKs or backend libraries when convenient
* Add platform-specific UI or UX layers around recommendations
* Surface recommendations inside various modalities (text, voice, multimodal)
* Implement custom delegation consent UI

***

## Selection interaction

The AIP selection model uses a **time-bounded asynchronous selection window**.

### How it works

1. Platform sends a `PlatformRequest` with `latency_budget_ms` to the Operator
2. Operator evaluates participation eligibility
3. Operator derives a `ContextRequest` and filters brand agents that match the context and governance constraints
4. Operator distributes (broadcasts) the `ContextRequest` to **all matching** brand agents
5. Operator computes the available response window from the platform's `latency_budget_ms`
6. Brand agents submit signed responses within the computed window (auction-style participation)
7. Operator runs selection, determines interaction mode, and returns the `PlatformResponse`
8. If no responses are received before the window expires, Operator returns a valid `no_match` response

### AI Platform implications

* Always handle `no_match` responses gracefully (render a fallback or continue the user workflow)
* Record participation attempts in your telemetry even when no match is returned
* Specify `latency_budget_ms` in PlatformRequest to control selection timing

***

## Delegation responsibilities

When the Operator returns a PlatformResponse with delegate mode:

1. **Present the offer (exposure)**  -  Show the user which Brand Agent is available and what it will do. Fire `exposure_shown` when the offer is displayed.
2. **Collect consent**  -  The user must explicitly agree before any session is initiated.
3. **Confirm consent to the Operator**  -  Send the user's consent to the Operator. The Operator checks brand-agent availability, initiates the delegation session, and records `delegation_started`.
4. **Run the delegated session (multi-turn)**  -  After the operator-mediated session start, the live task flow may continue directly between the Platform and Brand Agent. The Platform may host or relay that session, while the Operator remains the governance, audit, and settlement layer.
5. **Track outcomes and expiration**  -  The Platform fires `exposure_shown`, any applicable `interaction_started`, and delegated-session `delegation_activity` events while the session remains active. The Operator records `delegation_started`, resets inactivity state from verified activity, and records `delegation_expired` if the timeout elapses before the Brand Agent submits `task_completed`.

During the delegated session:

* The Platform should make clear that the user is interacting with the selected Brand Agent
* Additional task information may be collected inside the delegated session itself
* The Platform should emit delegated-session activity or keepalive events while the user is still active in the session
* That new information is session-bound by default and is not automatically part of the original operator handoff scope

If the user declines:

* No session is initiated
* The interaction falls back to recommend mode if content is available
* `exposure_shown` may still be tracked

***

## Role within the protocol

AI Platforms are the entry point for user intent.
Operators manage the governance and economic layer.
Brand Agents participate in selection and execute tasks.

**Intent → Platform → Operator → Participation → Events → Settlement**

The Platform is the surface where intent is captured and value is created.