> ## 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.

# Reading your seller's operating state and plan

> How a seller account reads whether buyers can use it now, whether it is paused, archived or adapter-routed, and what its plan includes.

A seller account can read two groups of facts about itself without a second call to the status tool:
what state it is in right now, and what its plan includes. Both are opt-in. A `get` of the seller that
names neither returns exactly what it returned before.

## Read them

Call `get` with `kind: "seller"`, no `id`, and either or both of `include: ["operating"]` and
`include: ["entitlements"]`:

```json theme={null}
{
  "operating": {
    "status": "live",
    "isPaused": false,
    "archivedAt": null,
    "routingMode": "CHEF"
  },
  "entitlements": {
    "merchandising": true,
    "listingDistribution": false,
    "operatingMode": "AGENTIC_MEDIA_COMPANY",
    "customModularSources": true,
    "sellingModeChange": { "canChange": true, "to": "listing", "reason": null, "nextStep": null }
  }
}
```

Both includes belong to the seller account that is reading itself. They are refused on any other kind,
on a seller read that names an `id`, and for a buyer account.

## Operating state

| Field | Meaning |
| - | - |
| `status` | Whether buyers can use the seller now: `live`, `paused`, `blocked` or `archived`. It is the same value the status tool reports as `state` for a seller account, from the same check. |
| `isPaused` | `true` while buyer intake is on hold. A hold stops discovery, new buys and buyer edits. It does not pause delivery of buys that already exist. `false` does not by itself make the seller live. |
| `archivedAt` | When the seller was archived, or `null` if it is not archived. An archived seller is read-only. |
| `routingMode` | Where buyer requests are routed: `CHEF` for the seller's Storefront Agent, or `ADAPTER` for an expert-run adapter implementation. |

`status` is decided in this order, so the first match wins:

1. `archived` when the seller is archived.
2. `paused` when buyer intake is on hold.
3. `blocked` when it is not paused or archived but a requirement for going live is still open. The status tool lists the open requirements as `blockers`.
4. `live` when none of the above applies.

`isPaused` and `archivedAt` are the stored values behind `status`. They are shown beside it so you can see why
the seller is paused or archived. `blocked` has no stored field of its own: it means a setup requirement
is open.

This is not the same answer as the go-live state or the setup progress in
[the readiness read](https://docs.apostra.com/v3/seller-readiness.md). `status` says whether buyers can use the seller now.

## Entitlements

| Field | Meaning |
| - | - |
| `merchandising` | `true` when the seller account is entitled to the Storefront Agent: its plan includes it, or the account holds a separate Storefront Agent grant. It is a commercial fact. It does not mean a connected source is ready to supply products. |
| `listingDistribution` | `true` when the seller account's organization holds the `seller-distribution` entitlement, which grants Listing + Distribution. It is independent of `merchandising`. |
| `operatingMode` | The account type: `LISTING_ONLY` or `AGENTIC_MEDIA_COMPANY`. It is the stored type of the account, the same answer as `sellingMode` on the seller read. See [Change a Seller Account's type](https://docs.apostra.com/v3/seller-account-type.md). |
| `customModularSources` | `true` when the seller account's plan, or a grant it holds, lets it create a custom modular inventory source. It comes from the `modular-sources` entitlement the account's organization holds, granted by its plan, a contract or Apostra, and it is the same check the create runs: when it is `false`, creating a modular source is refused with `FEATURE_NOT_ENABLED`. Seller Setup offers Modular source only when it is `true`. Contact Apostra to add it to a plan. |
| `sellingModeChange` | Whether you can change the account type now, with the reason and next step when you cannot. It is `null` when the server could not work it out. See [Change a Seller Account's type](https://docs.apostra.com/v3/seller-account-type.md#read-the-type). |

The account type is stored on the account. `save_account` sets it when it creates a seller, and
`save_seller({ sellingMode })` changes it in place. Your plan and feature settings no longer decide it.

`merchandising` and `operatingMode` are two answers from two checks, and you should not infer one from the other.
An account whose type is Listing but which holds a separate Storefront Agent grant reads
`merchandising: true` with `operatingMode: "LISTING_ONLY"`.

## When a read fails

There is no "unknown" value. If Apostra cannot work out `operating` or `entitlements`, for example because a plan
lookup timed out, the call still succeeds. It leaves that field out and names it in `unavailableIncludes` with a
one-sentence reason, so you never act on a guess. The seller and every other include you asked for come back in
full. Ask again for just the include that was left out. See
[Sellers on the V3 tool surface](https://docs.apostra.com/v3/tool-reference.md).

`operating` and `readiness` come from one read. When it fails, both are left out, and each one you asked for is listed.

## Related

* [Sellers on the V3 tool surface](https://docs.apostra.com/v3/tool-reference.md) lists every `get` kind and include a seller account reads.
* [Reading your agent's webhook results](https://docs.apostra.com/v3/agent-webhook-deliveries.md) shows another opt-in `include` read on `get`.


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