Operators act as the bridge between:
- AI Platforms (who send anonymized intent)
- Brand Agents (who bid on that intent)
- The AIP Ledger (which verifies exposure, click, and conversion events)
What an Operator Does
Every operator must implement five core functions:1. Receive ContextRequests from Platforms
Operators accept anonymized user intent and create an Auction Context. They must:- validate payload
- generate a serveToken
- start or join an auction cycle
- notify bidders (Brand Agents)
2. Run AIP Auctions
Operators run a real-time auction using AIP rules:- CPA outranks CPC
- CPC outranks CPX
- CPA and CPC bids must include budgets
- Winning bid must be returned within operator-defined latency
3. Deliver AuctionResults
Operators send the winning recommendation back to the platform. This includes:- product data
- click URL (signed)
- serveToken
- billing model (CPX, CPC, CPA)
4. Verify Events (CPX, CPC, CPA)
Operators must verify:- Exposure: fired when UI SDK renders result
- Click: via signed click redirect
- Conversion: via advertiser callback or partner API
5. Maintain Wallets & Monthly Settlement
Operators:- track advertiser balances
- track spend per serveToken
- maintain signed ledger entries
- generate monthly payouts to AI platforms
Operator Responsibilities
| Responsibility | Required | Description |
|---|---|---|
| Context ingestion | Yes | Handle ContextRequests from platforms |
| Auction engine | Yes | Implement CPA > CPC > CPX logic |
| Event pipeline | Yes | Exposure, click, and conversion validation |
| Serve token system | Yes | Generate and sign immutable tokens |
| Wallet accounting | Yes | Maintain advertiser balances |
| Ledger & payouts | Yes | Monthly platform payments |
| UI SDK | Yes | Provide a frontend SDK for platforms |
| Weave SDK | Optional | Provide backend inline-weave SDK |
| Reporting dashboard | Optional | For advertisers and platforms |
SDKs Provided by Operators (AdMesh Example)
An AIP operator may publish one or more SDKs. AdMesh provides:1. UI SDK (required for platforms)
- rendering results
- exposure tracking
- click tracking
- fallback logic
- session ID + message ID tracking
2. Backend Weave SDK (optional)
Node.js:- fetching recommendations server-side
- feeding the LLM for inline weaving
- reducing follow-up fetches
Operator Architecture (High-Level)
Implementing Your Own AIP Operator
To become an AIP operator, you must implement:- ContextRequest API
- Auction API
- Bid API
- Event Verification API
- Wallets & Ledger logic
- UI SDK for platforms
- Click redirect system
- Platform authentication
- Advertiser authentication
Your operator defines the implementation.
Why Become an Operator?
- Own the ad marketplace in your ecosystem
- Monetize intent from AI platforms
- Create your own advertiser marketplace
- Maintain full transparency with AIP
- Attract brand agents with performance-first bidding
- Enable new revenue streams (CPX, CPC, CPA)
AdMesh as an Operator (Reference Implementation)
AdMesh is the first operator built on AIP. It provides:- UI SDK (admesh-ui-sdk)
- Weave backend SDKs
- Wallet system
- Real-time ledger
- Advertiser dashboard
- Platform dashboard
How to Integrate an Operator
Platforms must:- Sign up with the operator
- Get API key
- Install operator UI SDK
- Render results via UI SDK or Weave
- Post events (exposures, clicks)
- Receive monthly payouts
- Register with operator
- Create offers
- Bid programmatically
- Track spend
- Track conversions