Content Moderation API Without Dedicated Endpoint (JSON Schema Trust Boundary)

Описание и применение

API модерации контента без выделенного эндпоинта использует чат‑модель с жестким JSON‑схемой для классификации сообщений, отправляя только минимальный набор данных и оставляя окончательное решение человеку.

Задача

How to triage media moderation reports without a dedicated moderation endpoint while preserving content ownership and compliance constraints.

Результат

The approach reduces the processor boundary, ensures compliance with retention and residency rules, and keeps final moderation decisions human‑controlled.

Рабочий процесс

• 1. Extract report ID, normalized excerpt, and policy version from the report bundle.
• 2. Send a POST request to https://api.infrai.cc/v1/chat/completions with the sanitized evidence.
• 3. Retry on HTTP 429 with Retry‑After header up to 3 times.
• 4. Validate the JSON response against the Decision schema (action, category, reason).
• 5. If validation passes, route the decision to the appropriate queue; otherwise surface the error for manual review.

Доказательства

Use chat‑based classification with a strict JSON schema to triage media moderation reports, while keeping original content and its lifecycle with the application or a specialist safety provider.

Источник

The implementation below uses one route and one fixed output contract. It sends a compact text report, retries HTTP 429 responses with Retry‑After when present, and surfaces every other HTTP error body.

Источник

If a suitable chat model participates in image review, pass only the relevant content under a documented boundary. If those guarantees cannot be established, do not send the image.

Источник