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

# Demo Storefront

> Try the whole seller journey on a temporary Seller Account with synthetic inventory: how to get one, what it contains, how it expires, how to extend it and choose its sample sources, and what a buyer's agent sees.

A Demo Storefront is a Seller Account's time-limited stand-in made of synthetic
sample inventory. Use it to explore or present the complete seller journey
without connecting a production system. It uses the same products, readiness,
policy and approval surfaces as a live Storefront, and its Seller Dashboard has
a separate, clearly labelled evaluation view instead of live analytics.

> [!WARNING]
>
> Demo Storefront data is synthetic. A sample source may be shaped like a
> vendor's inventory, but it never connects to or emulates Google Ad Manager,
> FreeWheel, Epsilon, Cadent or another vendor API, and it never uses vendor
> credentials.

A Demo Storefront is never charged. Nothing it does counts as billable
activity on your plan: not a brief answered on it, not a practice brief you run
on it, and not a media buy placed against it. A media buy that also holds a
package from a real Storefront is charged for that real activity as usual. It
needs no accepted plan or payment details to respond. This belongs to the Demo Storefront, not to its
account. When the Demo Storefront expires or is deleted, the account stays
active but the Demo Storefront and its synthetic data are gone, and a real
Storefront you set up on that account later is billed as usual, like any other.

A Demo Storefront never becomes a live Storefront and never holds real
inventory. Attaching a real source to one is refused. To sell real inventory,
use a separate Seller Account. A Demo Storefront is different from the
[intake hold](https://docs.apostra.com/v3/seller-intake-hold.md), which stops new buyer business on a live
Seller Account.

`get` with `kind: "seller"` returns `mode: "demo"` while the Demo Storefront is
active, and the lease as `demo.status`, `demo.expiresAt`, `demo.disclosure` and
`demo.sourceRecipeIds`. A Seller Account with no Demo Storefront has no `demo`
object.

## Get a Demo Storefront

An Apostra platform administrator creates a Demo Storefront as a separate Seller
Account under your organization. Creating one is a platform permission, not an
account role: you cannot create one yourself, even as an administrator of your
organization, and ordinary accounts show no demo-creation controls.

To get one, contact your Apostra representative, or ask your agent to file a
support request with `save_ask`. An Apostra platform administrator then creates
it for you.

The administrator creates it with **Add account** in the organization's accounts
list under **Settings** or **Plan & Billing**, from a browser tab that has not
switched accounts. They choose:

| Choice | Options |
| - | - |
| Name | The name of the Demo Storefront. |
| Capabilities | Listing, Listing + Distribution, Storefront agent, or Storefront agent + Distribution. The default is Storefront agent + Distribution. |
| Inventory profile | Display, Display + CTV, Display + retail media, or Mixed publisher. The default is Display. |

The capabilities apply only to that Demo Storefront while it is active. They do
not change the organization's paid plan. An Apostra platform operator's agent
can also create one with `save_account` and `demoStorefront: true`, which uses
the default capabilities and inventory profile and is recorded for website
approval first; see [Account access](https://docs.apostra.com/v3/account-access.md). Any other caller is
refused.

## What a new Demo Storefront contains

Every Demo Storefront starts with **Sample Publisher Display**. The Demo
Storefront Page shows the profile and sample-data versions, so a presenter can
confirm exactly which scenario is open. The profile includes:

* a synthetic modular inventory source;
* two display products, **Homepage Impact Display** at a USD 18.00 CPM and
  **Contextual Article Display** at a USD 12.50 CPM, each with audience,
  context, device and country targeting and a deterministic availability;
* a fictional sustainable-travel buyer's brief for USD 75,000 of United States
  display, with the response, a sample confirmed booking and a sample delivery;
* a sample acceptance policy and a sample team to route approvals to; and
* two pending approvals: one media buy and one creative review.

The sample brief and its booking are examples. They are not buyer demand,
revenue, attribution or real delivery.

### Other sample sources

The other inventory profiles add these sample sources to Sample Publisher
Display:

| Sample source | Recipe id | Products |
| - | - | - |
| Sample Publisher CTV | `sample-publisher-ctv` | Prime Time Streaming Video and Live Sports CTV |
| Sample Retail Media | `sample-retail-media` | Sponsored Search Results and Retail Category Display |

**Mixed publisher** attaches all three. Each source is a code-owned synthetic
recipe, not a vendor adapter. To add or remove sources later, see "Choose the
sample sources" below.

### Review the sample approvals

Open **Approvals & operations** to review the two pending items. The creative is
a clearly labelled, fictional 300×250 display example for the sample campaign,
assembled as static text inside Apostra. It contains no customer data,
credentials, trackers or calls to an external service.

Both items follow the same review queue, assignment, approval and rejection
workflow as a real one. The media-buy approval starts assigned to Maya Chen
(Sales Operations); reassign it to Jordan Ellis (Revenue Lead) or Priya Shah
(Ad Operations) and decide it in Approvals. Reset returns both items to pending
and restores the team routing without adding duplicate queue items.

### Find the synthetic products

Your agent finds a Demo Storefront's products the same way it finds any
Storefront's. `search({ "kind": "wholesale_product" })` returns them from the
same catalogue a proposal uses. Each one carries `synthetic` with the
synthetic-inventory disclosure and the recipe that generated it, so it is never
presented as a real publisher's product. See
[Seller and product filters](https://docs.apostra.com/v3/tool-reference.md#seller-and-product-filters).

A Demo Storefront has no buyers, so its Media Buys page lists generated buys
instead; see [Seller Media Buys page](https://docs.apostra.com/v3/seller-media-buys-page.md). To rehearse
answering a brief from the Library, see [Library](https://docs.apostra.com/v3/seller-library.md).

## Readiness and go-live status

A Demo Storefront's sample sources need no vendor credentials or external source
tests. While its lease is active and unexpired:

* Seller Setup shows each sample source's **Local synthetic readiness**, and
  Source Diagnostics labels the source **Local synthetic**. The label means the
  source is verified from its code-owned recipe and the current lease, with no
  external call. Source health and catalog readiness remain separate checks.
* A synthetic managed source's ad-server connection step counts as complete, so
  neither the seller navigation nor the source reports an ad-server blocker.
  Every other setup task keeps its normal result.
* The Storefront's `publish_validation` readiness requirement reports complete
  with `method: "demo_mode"`, because there is no real seller-side transaction
  to prove.

If the lease is missing or expired, Apostra uses the ordinary live-source
checks.

A Demo Storefront is created paused, and its sample confirmed booking is
synthetic, so it does not count as a real transaction when Apostra decides
whether a Storefront has gone live. A fresh demo therefore reads **Paused before
going live** in the seller navigation and the account switcher. The sample
booking and its delivery still appear on Media Buys, Demand and the Demo
Storefront Page.

## Expiry and controls

A new Demo Storefront expires seven days after it is created. The Demo
Storefront Page shows its expiry and offers three controls:

| Control | What it does |
| - | - |
| **Reset** | Rebuilds the selected synthetic inventory, keeps the selected capabilities, and does not change the expiry. |
| **Extend 7 days** | Moves the expiry seven days past the later of the current expiry and now. |
| **Delete now** | Removes the Demo Storefront and its synthetic resources immediately, then archives its Demo account. |

Reset and Delete now ask for confirmation first.

**Delete now** archives the Demo account the Demo Storefront was created in. The
archived account leaves the account switcher and the active **Settings →
Organization → Accounts** list, and keeps its history and members. It stays in
that list under the **Archived** status filter, where an organization
administrator can restore it. Archiving needs no open campaigns or media buys on
the account, and an Apostra staff member or an administrator of the organization
can do it. If the account cannot be archived, the Demo Storefront is still
deleted and the Page says why; archive the account from the organization's
Accounts list instead. A Demo Storefront added to any other kind of account
never archives that account.

When a Demo Storefront expires, Apostra removes the Demo Storefront and its
synthetic data and leaves the account active. If that cleanup fails, `status`
becomes `CLEANUP_FAILED`, the Page shows the reason, and Apostra retries. After
five failed attempts the retries stop, `status` stays `CLEANUP_FAILED`, and the
reason says that automatic retries have stopped. **Delete now** tries the
cleanup again straight away. **Reset** or **Extend 7 days** returns the Demo
Storefront to `ACTIVE`. Any of the three gives automatic cleanup five new
attempts.

## Extend the Demo Storefront

Send `demo.expiresAt` to `save_seller`, the instant you want the Demo Storefront
to expire.

```json theme={null}
{
  "demo": { "expiresAt": "2026-11-10T12:00:00Z" }
}
```

| Rule | What it means |
| - | - |
| Later than now and the current expiry | A Demo Storefront is only ever extended. To end one, delete it from the Demo Storefront Page. |
| At most seven days past that | The limit is measured from the later of the current expiry and now, so an expired Demo Storefront can be extended to seven days from now. Extend again for longer. |
| Already that expiry | The call succeeds and changes nothing; the result reports `unchanged`. |

A request that is a few minutes beyond the seven-day limit, because your clock
runs ahead of ours, is held to the limit. Read `demo.expiresAt` in the result
for the instant that was saved.

## Choose the sample sources

Send `demo.sourceRecipeIds` to `save_seller`, the complete set of sample sources
you want.

```json theme={null}
{
  "demo": {
    "sourceRecipeIds": ["sample-publisher-display", "sample-publisher-ctv"]
  }
}
```

The three sample sources are `sample-publisher-display`, `sample-publisher-ctv`
and `sample-retail-media`. The Demo Storefront gains the ones it lacks and drops
the optional ones you leave out, with the products they generated. The set must
list each source once and must keep `sample-publisher-display`, which supplies
the sample brief; a set without it is refused with `VALIDATION_ERROR`.

To add one source, read `demo.sourceRecipeIds`, add it, and send the whole set.

## Rules for changing a Demo Storefront

* **Send `demo` alone.** It changes the Demo Storefront, not the Seller
  Account's own configuration. `demo` together with any other `save_seller`
  field is refused with [`VALIDATION_ERROR`](https://docs.apostra.com/v3/errors).
* **You need the same access as for the Demo Storefront Page.** A Seller Account
  with no Demo Storefront and no modular-source entitlement is refused with
  `FEATURE_NOT_ENABLED`, and one with no Demo Storefront is `NOT_FOUND`.
  A Demo Storefront that is being deleted is refused with `CONFLICT`. So is a
  sources change made from sources that have since changed, for example by
  another save at the same moment: read `demo.sourceRecipeIds` again and retry.
* **`expiresAt` and `sourceRecipeIds` can be sent together.** The expiry is
  saved first. If the sources are then refused, the error says the expiry was
  saved, and you retry with only the sources.
* **The `write` role is required**, the same role `save_seller` needs for every
  other change.

## Open the management Page

An agent on the V3 Seller surface opens an existing Demo Storefront's Page with
`open_page({ "page": "demo_seller" })`. The Page lets an authorized seller
inspect the lease and its sample sources, add or remove optional sources, reset
the Demo Storefront, extend it, or delete it. It works through the shared MCP
app contract, so any host that renders MCP apps shows the same Page.

A seller with a Demo Storefront can open the Page, and the Demo Storefront card
under **Your storefront** in the seller navigation, without a modular
inventory-source entitlement. That changes seller-side access to the Page only;
it does not change what buyers can discover, call or see.

Opening the Page grants no new permission and does not create a Demo
Storefront. Creation stays an Apostra platform-administrator action, and the
legal terms stay accepted by the authorized person for the organization.

## Evaluation analytics in Seller Dashboard

While the Demo Storefront's lease is active, its signed-in seller can open
Seller Dashboard to read a **Synthetic evaluation data** view. It reports the
current lease generation's finished practice runs through the same RFP
performance calculation Seller Dashboard uses: the number of RFPs, the
response-ready rate, the pass rate, the average grade, the truth-drop rate and
the average processing latency. It also lists up to eight recent runs, each with
its RFP and turn id and response state, plus the profile disclosure and the
lease expiry.

To open it, choose **Seller analytics** under **Operate** in the seller
navigation, or ask your agent to open the dashboard. An agent calls
[`open_seller_dashboard`](https://docs.apostra.com/v3/tool-reference#open-seller-dashboard). Opening
Seller analytics does not make the Demo Storefront live: it still reads **Paused
before going live**.

The view is rehearsal evidence only. It does not report or imply buyer demand,
bookings, revenue, attribution, learned posture or delivery, and standard Seller
Dashboard analytics stay live-only. An evaluation run is never relabelled as
live data.

Only the authenticated owner of the exact active Demo Storefront lease can read
it. It excludes other Storefronts and tenants, live and draft RFPs, earlier
lease generations, and runs from before the last reset. If the lease expires,
resets, is missing, or cannot be resolved unambiguously, the view is not
returned. An empty view means no finished evaluation runs exist for the current
lease generation. It says nothing about buyer demand.

## Ask Apostra in a Demo Storefront

Apostra knows when the selected account is a Demo Storefront. It treats the
account's sources, products, briefs and approvals as synthetic sample data, says
so using the profile's disclosure, and labels synthetic products as synthetic. A
Demo Storefront never goes live, so Apostra does not open a conversation with
go-live onboarding and does not ask you to connect a real ad server.

## What a buyer's agent sees

A Demo Storefront is a real, callable AdCP seller. A buyer's agent can call
`get_products` on it and reach it through ordinary discovery, like any other
Storefront. Because its inventory is synthetic, the `get_products` response
says so, so an agent never mistakes it for a real seller:

| Field | Type | Meaning |
| - | - | - |
| `ext.scope3.storefront.demo` | `boolean` | Present and `true` only on a response from a synthetic seller, which includes a Demo Storefront. Absent for a real Storefront, never `false`. |
| `ext.scope3.storefront.demo_disclosure` | `string` | The disclosure sentence for the active profile, for example "Synthetic sample data for demonstration only. This profile does not connect to or emulate a publisher or ad-server API." Present whenever `demo` is `true` and the profile resolves. |

Both fields sit in the namespaced `ext` object beside the normal `products` and
`proposals` in the same response. An agent that does not recognize the
namespace can ignore it. One that does should treat any product or proposal from
a response where `ext.scope3.storefront.demo` is `true` as a demonstration, not
a real offer. The same disclosure sentence appears in the response's
human-readable summary text.

For how buyer agents read synthetic sellers and run sandbox briefs against them,
see [Build an agent](https://docs.apostra.com/v3/build-an-agent.md).

## What is real and what is synthetic

Account permissions, the Storefront, its products and availability, its
policy, and its expiry use normal platform behavior. The inventory facts, the
fictional buyer and campaign, the evaluation evidence, the delivery examples and
the upstream references are synthetic. The evaluation view is disclosed as
synthetic, and ordinary Seller Dashboard analytics stay live-only.

A Demo Storefront uses the real account permissions and terms of the
organization it belongs to. Apostra cannot accept terms for a presenter, a
prospect or another person.

## Related

* [Seller Account type](https://docs.apostra.com/v3/seller-account-type.md): a Demo Storefront has a fixed
  type.
* [Seller readiness](https://docs.apostra.com/v3/seller-readiness.md): how setup and go-live status are
  reported.
* [Seller modular source pages](https://docs.apostra.com/v3/seller-modular-source-pages.md): the sources a
  Demo Storefront's sample sources are built on.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.