Skip to main content

​
Overview

Your storefront is your buyer-facing home on Scope3 Interchange: the business presence, name, and discovery surface buyers use to understand who they are buying from. Behind it, the Interchange Merchandising Engine answers buyer briefs, composes products, and runs the AdCP media-buy workflow on your behalf, drawing from one or more inventory sources you connect. This page is the operator’s map of the storefront object. Each domain below has its own task pages; this overview explains what the pieces are and how they fit together. 
Storefront                                  (your buyer-facing surface)
  ├── Business Profile                       (identity, positioning, authorized domains)
  ├── Operating Instructions                 (versioned guidance; exactly one active)
  └── Inventory Source(s)                    (AdCP agent — discovery + execution)
        └── Buyer accounts                   (the buyers that transact through the source)
All examples use the storefront base URL and a bearer token: 
https://api.interchange.io/api/v2/storefront

curl https://api.interchange.io/api/v2/storefront/readiness \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

​
Inventory sources

An inventory source is an AdCP-compatible agent that handles product discovery (get_products) and media-buy execution (create_media_buy) for your storefront. A storefront wraps one or more sources, and the products buyers see are assembled from the sources you connect. Sources come in a few shapes:
  • External sales agents you already run, connected by endpoint and auth.
  • Managed ad servers — Google Ad Manager, FreeWheel, or SpringServe — where Scope3 runs the sales-agent plumbing in front of your ad server.
  • Other storefronts that have authorized passthrough or federation.
Each source declares its capabilities (products, createMediaBuy, updateMediaBuy, signals, wholesaleProducts) and whether it requires authentication. A composition storefront assembles products across active sources; a passthrough storefront proxies get_products to one upstream source and overlays your storefront identity and buyer instructions on the response.

​
Business profile

Your business profile is captured during storefront setup and helps the Merchandising Engine describe your business, follow the right merchandising guidance, and understand which publisher domains it is authorized to sell through the storefront.
FieldTypeDescription
agentNamestringDeprecated agent-name field, kept for legacy compatibility only. Prefer the storefront display name for buyer-facing naming. Maximum 80 characters.
agentPersonalitystringVoice and merchandising guidance for buyer-facing interactions and reports. Maximum 1000 characters.
publisherDomainsstring[]Publisher domains or properties the storefront is authorized to sell. Up to 128 valid domains; each is normalized to lowercase, deduplicated, and limited to 253 characters.
Example
{
  "businessProfile": {
    "agentPersonality": "Confident, concise, and commercially sharp.",
    "publisherDomains": ["touchline.example", "football.touchline.example"]
  }
}
Omitting publisherDomains means the authorized domains are unknown or have not been captured yet. It does not mean the storefront is authorized to sell every domain.

​
Operating instructions

Operating instructions are versioned guidance that steers how your storefront responds to demand — what to package, how to position, and how to negotiate. Exactly one version is active at a time; publishing a new version supersedes the prior one without losing history. Operating instructions are authoritative over historical analytics signals. When the Merchandising Engine composes products, your written instructions and buyer instructions win over any directional signal derived from recent outcomes.

​
Readiness diagnostics

GET /readiness tells you whether your storefront can go live. It returns blocking checks for inventory sources, agent status, and agent auth, plus a per-source sourceDiagnostics[] array used by setup surfaces. The overall status is ready or blocked; each check reports complete, partial, missing, or optional, and carries an isBlocker flag. See Get readiness for the full field reference.

​
Marketplace review and AAO gating

New storefronts start in a pending-review marketplace state. You can configure and use your storefront, and open it for known transactions, but public buyer discovery only includes storefronts that Scope3 has reviewed and listed. Marketplace listing is gated on the Agentic Advertising Organization (AAO) registry: each connected source is checked for AAO compliance, and only compliant sources surface to buyers. Use Discover agents and Resolve brand to inspect what the registry knows about your operator domain and the brands you transact with.
An admin can hide a listed storefront, which removes it from public buyer discovery without deleting the storefront or its inventory sources.

​
Storefront domains

Inventory sources

Connect and manage the AdCP agents and ad servers behind your storefront.

Operating instructions

Versioned merchandising and negotiation guidance.

Signals

The targeting and optimization inputs your sources expose.

Demand signals

Inbound expressions of buyer interest you can shape inventory around.

Media-Buy Approvals

Review and decide on incoming media buys before they go live.

Billing

Connect billing so your storefront can transact.

Analytics

Win rate, buyer asks, top products, and negotiation posture.

Buyer instructions

Per-buyer discounts, notes, and country scoping.