> ## 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 Product marketing counts

> How a seller account reads how many selling points are teaching its agent, how many live inventory does not back, and when a result last changed.

A seller account can read three counts about its [Product marketing](https://docs.apostra.com/v2/storefront/product-marketing/overview.md)
in one call: how many selling points are teaching the agent, how many of them your live inventory does not
back, and when a result last changed. It is opt-in. A `get` of the seller that does not ask for it returns
exactly what it returned before.

## Read it

Call `get` with `kind: "seller"`, no `id`, and `include: ["teaching"]`:

```json theme={null}
{
  "teaching": {
    "claimCount": 12,
    "gapClaimCount": 2,
    "lastVerdictChangeAt": "2026-10-20T12:00:00.000Z"
  }
}
```

The include belongs to the seller account that is reading itself. It is refused on any other kind, on a
seller read that names an `id`, and for a buyer account.

| Field | Meaning |
| - | - |
| `claimCount` | Selling points currently teaching the agent. Withdrawn ones are not counted. |
| `gapClaimCount` | Selling points your live inventory does not back. This is the number to act on. |
| `lastVerdictChangeAt` | When a selling point's result last changed, or `null` when none has ever been recorded. |

`lastVerdictChangeAt` is a change time, not a check time. It moves only when a result changes, so it says when
something last changed and nothing about how recently the counts were checked. Opening Product marketing
checks every selling point against your current inventory and shows its own checked-at time. The counts here
are the results on record, so they can lag what that page shows.

The counts cover your whole account. To read individual selling points, use the Product marketing page.

## Who can read it

Product marketing is not on for every seller yet. A seller outside the Product marketing cohort gets
`ACCESS_DENIED`, never a count of zero, because "you have taught the agent nothing" and "this is not on for
you" are different answers.

## When a read fails

| Code | When |
| - | - |
| `ACCESS_DENIED` | The seller account is not in the Product marketing cohort. |
| `NOT_FOUND` | The seller account has no live Storefront, so it has no selling points to count. |
| `SERVICE_UNAVAILABLE` | Apostra could not read the counts. Retry the same call. |

There is no "unknown" value and no partial answer: a failed read returns the error and none of the seller.

## Related

* [Product marketing](https://docs.apostra.com/v2/storefront/product-marketing/overview.md) explains what a selling point is and how it is checked against your inventory.
* [Sellers on the V3 tool surface](https://docs.apostra.com/v2/setup/v3/tool-reference.md) lists every `get` kind and include a seller account reads.


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