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

# Pre-check content against moderation policy

> Runs the content-moderation engine against the supplied text WITHOUT blocking. Returns structured findings (category, severity, suggestion) so buyer agents can validate input before submitting it to a campaign create or other blocking surface. Mirrors the engine that powers `POST /v2/campaigns` brief screening.



## OpenAPI

````yaml /v2/storefront-api-v2.yaml post /moderation/check
openapi: 3.0.0
info:
  title: Scope3 Storefront API
  version: 2.0.0
  description: |-
    REST API for partners to manage storefronts, 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 storefronts
  - name: AI Usage
    description: Storefront AI token usage visibility by model
  - name: MCP
    description: Model Context Protocol endpoints
paths:
  /moderation/check:
    servers:
      - url: https://api.interchange.io/api/v2
        description: Production server
    post:
      tags:
        - Moderation
      summary: Pre-check content against moderation policy
      description: >-
        Runs the content-moderation engine against the supplied text WITHOUT
        blocking. Returns structured findings (category, severity, suggestion)
        so buyer agents can validate input before submitting it to a campaign
        create or other blocking surface. Mirrors the engine that powers `POST
        /v2/campaigns` brief screening.
      operationId: checkModeration
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                text:
                  description: >-
                    The text to evaluate. Up to 10,000 characters; longer text
                    is truncated server-side.
                  type: string
                  minLength: 1
                  maxLength: 10000
                direction:
                  description: >-
                    Which pattern set to apply. "input" runs the
                    brief/jailbreak/policy patterns; "output" runs the
                    LLM-output (refusal/identity/PII) patterns.
                  default: input
                  type: string
                  enum:
                    - input
                    - output
                surface:
                  description: >-
                    Optional surface label for metric attribution. Defaults to
                    "moderation.check".
                  default: moderation.check
                  type: string
                  minLength: 1
                  maxLength: 100
              required:
                - text
      responses:
        '200':
          description: Pre-check content against moderation policy
          content:
            application/json:
              schema:
                type: object
                properties:
                  passed:
                    description: True when no moderation patterns matched.
                    type: boolean
                  wouldBlock:
                    description: >-
                      True when at least one finding would trigger a 422 if this
                      content were submitted to a blocking surface.
                    type: boolean
                  findings:
                    description: >-
                      All matching findings. Empty when `passed` is true. Both
                      blocking and non-blocking findings are reported so callers
                      can observe medium-severity signals.
                    type: array
                    items:
                      type: object
                      properties:
                        category:
                          description: >-
                            Moderation category (e.g. "jailbreak_attempt",
                            "pii_leak").
                          type: string
                        severity:
                          description: >-
                            Severity tier. "high" and above is what blocks at
                            default thresholds.
                          type: string
                          enum:
                            - low
                            - medium
                            - high
                            - critical
                        suggestion:
                          description: >-
                            Human-readable remediation guidance for the buyer
                            agent to self-correct.
                          type: string
                      required:
                        - category
                        - severity
                        - suggestion
                      additionalProperties: false
                required:
                  - passed
                  - wouldBlock
                  - findings
                additionalProperties: false
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized
          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:
    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

````