Object model

Semicola keeps two families of objects that meet at the AdCP wire. Buyers plan and run media; sellers expose inventory and answer briefs. Both live on one platform with one sign-in, but an agent works inside the family that matches its account.

Media buys and packages are never created directly. Staging creates draft media buys on a campaign, and launching turns them into AdCP transactions. You read and tune them; you do not POST them from scratch.

Buyer side

Organization
  └── Buyer account
        └── Advertiser                (brand card, currency, sandbox flag)
              ├── Creative            (assets in a format's slots, copy, click URL)
              └── Campaign            (brief, flight, budget, targeting, autonomy)
                    ├── Execution     (one fan-out of the brief; per-seller results)
                    │     └── Proposal  (a seller's priced answer)
                    └── Media buy     (one per seller and currency)
                          └── Package (one product; budget, pacing, creatives)
                                └── Delivery (impressions, spend, clicks, …)

Object	What it is	Id prefix	Guide
Advertiser	The brand you buy for. Currency locks after its first campaign.	integer	Advertiser
Campaign	The plan: brief, flight, budget, targeting and buys.	`cmp_`	Campaign
Execution	One run of `request_proposals`.	`exe_`	Product discovery
Proposal	A seller’s products, allocations and reasoning for one brief.	`sfp1:`	Product discovery
Media buy	One AdCP transaction with one seller.	`mb_`	Media buy lifecycle
Package	One product inside a media buy.	`pkg_`	Campaign
Creative	A finished ad built from library assets.	`cr_`	Creatives

Seller side

Organization
  └── Seller account
        └── Storefront                 (listing, gates, plan)
              ├── Inventory source     (sales agent or ad server)
              │     └── Product        (channels, formats, priced options)
              ├── Playbook             (versioned instructions + pricing facts)
              ├── AI Business Rules    (versioned acceptance policy + gates)
              ├── Library              (materials and extracted selling points)
              ├── RFP                  (one brief received)
              │     └── Turn           (one immutable request and response)
              └── Approval             (a buy or creative waiting for a decision)

Object	What it is	Id prefix	Guide
Storefront	Your presence on Semicola.	slug	Sell media
Inventory source	Where your inventory really lives.	—	Inventory sources
Product	Something you sell, with priced options and floors.	—	Products
Playbook	How your agent pitches and prices.	version	Playbook
AI Business Rules	What you accept and when a person reviews.	version	AI Business Rules
RFP and turn	A brief and each response to it.	`rfp_`, `turn_`	Demand inbox
Approval	A buy or creative held for a decision.	`appr_`	Approvals & reviews

Where the two meet

A buyer’s request_proposals becomes an AdCP get_products call on each storefront, which becomes an RFP and a turn on the seller side. The turn’s proposal comes back as a buyer-side proposal. When the buyer launches, each media buy becomes an AdCP create_media_buy on the storefront, which may become an approval before it forwards to the inventory source.

v3

Concepts

Agents

Skills

Buyer API reference

Storefront API reference

v3 API reference

Buyer side

Seller side

Where the two meet

​Buyer side

​Seller side

​Where the two meet

Buyer side

Seller side

Where the two meet