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

# Get product-marketing corpus health

> Counts for the calling storefront's product-marketing corpus: material ingested, live claims teaching the agent, how many of those the storefront's live inventory backs, how many it does not (the gaps), how many carry no verdict, and when a verdict last changed. Reports persisted verdicts and does not re-run reconciliation, so it makes no claim about when the corpus was last checked; opening the corpus Page re-derives verdicts against current inventory and reports its own checked-at. Requires the product-marketing corpus to be enabled for the account.



## OpenAPI

````yaml /v2/storefront-api-v2.yaml get /product-marketing/health
openapi: 3.0.0
info:
  title: Scope3 Storefront API
  version: 2.0.0
  description: >-
    REST API for partners to manage Seller Accounts, inventory sources, and
    billing.


    ## Authentication


    All endpoints require a Bearer token in the Authorization header:

    ```

    Authorization: Bearer your-api-key

    ```


    ## Base URL


    `https://api.interchange.io/api/v2/storefront`


    ## For AI Agents


    AI agents can use the MCP endpoint at `/mcp/v2/storefront` with three tools:

    - `initialize`: Start an MCP session

    - `api_call`: Make REST API calls

    - `ask_about_capability`: Learn about API features
servers:
  - url: https://api.interchange.io/api/v2/storefront
    description: Production server
security: []
tags:
  - name: Account
    description: Account management, service tokens, and preferences
  - name: Asks
    description: >-
      What you are waiting on Scope3 for — support, product, and supply asks in
      one list
  - name: Storefront
    description: Manage storefront and inventory sources
  - name: Storefront Agents
    description: List and manage registered sales, signals, and outcomes agents
  - name: Storefront Activity
    description: Audit log of configuration and inventory changes on the storefront
  - name: Storefront Billing
    description: Payout bank details and billing configuration for Seller Accounts
  - name: AI Usage
    description: Seller Account AI token usage visibility by model
  - name: MCP
    description: Model Context Protocol endpoints
paths:
  /product-marketing/health:
    get:
      tags:
        - Storefront
      summary: Get product-marketing corpus health
      description: >-
        Counts for the calling storefront's product-marketing corpus: material
        ingested, live claims teaching the agent, how many of those the
        storefront's live inventory backs, how many it does not (the gaps), how
        many carry no verdict, and when a verdict last changed. Reports
        persisted verdicts and does not re-run reconciliation, so it makes no
        claim about when the corpus was last checked; opening the corpus Page
        re-derives verdicts against current inventory and reports its own
        checked-at. Requires the product-marketing corpus to be enabled for the
        account.
      operationId: getProductMarketingHealth
      responses:
        '200':
          description: Get product-marketing corpus health
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ProductMarketingHealth'
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: The product-marketing corpus is not enabled for this account.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: No live storefront exists for the calling operator.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - bearerAuth: []
components:
  schemas:
    ProductMarketingHealth:
      description: >-
        Counts for the seller rail’s Product marketing row: how much the corpus
        is teaching, how much of it live inventory backs, and when a verdict
        last changed.
      type: object
      properties:
        entryCount:
          description: Pieces of marketing material in the corpus.
          type: integer
          minimum: 0
          maximum: 9007199254740991
        claimCount:
          description: Live claims currently teaching the agent.
          type: integer
          minimum: 0
          maximum: 9007199254740991
        backedClaimCount:
          description: Claims the storefront’s live inventory backs.
          type: integer
          minimum: 0
          maximum: 9007199254740991
        gapClaimCount:
          description: >-
            Claims live inventory does not back. This is the rail’s attention
            signal.
          type: integer
          minimum: 0
          maximum: 9007199254740991
        unreconciledClaimCount:
          description: >-
            Claims with no verdict — nothing checkable in them, or never
            checked. Counted as its own bucket rather than folded into either
            verdict.
          type: integer
          minimum: 0
          maximum: 9007199254740991
        lastVerdictChangeAt:
          description: >-
            When a verdict last CHANGED, or null when none has ever been
            recorded. Deliberately not a measurement time: a claim’s
            reconciliation timestamp is only rewritten when its verdict moves,
            so this answers "when did this last change", never "when was this
            last checked". The rail renders it as a change time and makes no
            freshness claim; opening the corpus page re-derives verdicts against
            current inventory and reports its own checked-at.
          nullable: true
          type: string
      required:
        - entryCount
        - claimCount
        - backedClaimCount
        - gapClaimCount
        - unreconciledClaimCount
        - lastVerdictChangeAt
      additionalProperties: false
    ErrorResponse:
      description: Standard error response
      type: object
      properties:
        data:
          type: string
          nullable: true
          enum:
            - null
        error:
          $ref: '#/components/schemas/ApiError'
      required:
        - data
        - error
      additionalProperties: false
    ApiError:
      description: Structured error object
      type: object
      properties:
        code:
          description: Machine-readable error code
          type: string
        message:
          description: Human-readable error message
          type: string
        field:
          description: Field path associated with the error
          type: string
        details:
          description: Additional error context
          type: object
          additionalProperties: {}
      required:
        - code
        - message
      additionalProperties: false
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: API key or access token

````