open_seller_buyers (filter: all
or awaiting).
What each buyer shows
The filter switches between All and Awaiting you, which shows the
pending buyers.
Status
A buyer’s first call creates the relationship as
pending. Pending doesn’t block anything: it marks
the buyer for your review. A suspended buyer’s new media buys are refused with ACCOUNT_SUSPENDED
(”… has paused media buys from this account. Contact the seller.”). Suspending doesn’t stop delivery
on buys that are already running, and doesn’t block changes to them.
Allowed changes:
- Approve
pending → active, optionally setting theposture. - Suspend
pendingoractive → suspended. - Reactivate
suspended → active. Reactivating anything else returnsCONFLICT(“Only a suspended buyer can be reactivated.”); approving a buyer that isn’t pending returns “This buyer is already …”.
MCP and REST
The three MCP writes always ask the person to confirm. The REST path
POST /sponsored-buyers/{buyerCustomerId}/{action} also works, keyed by the buyer’s customer id
instead of the relationship id. Every change is recorded in your storefront
Activity.
Not available yet
Posture is recorded for your records only: Semicola doesn’t clear media payments for sellers yet, soprepay and credit don’t change how money moves. Buyer accounts confined to a single storefront,
and invitations for new buyers, aren’t available.
Buyer account mapping isn’t available either: there’s no per-inventory-source coverage view
(Mapped, Not set up, Stale…), no source account roster search, no mapping CSV import or export,
and no get_seller_accounts tool. A buyer relationship is one record per buyer account, not per
operator and brand.