Molmo2 Text Content Moderator API Documentation

Molmo2 Text Content Moderator API Documentation

Playground

Try it on WaveSpeedAI!

Molmo2-4B Text Content Moderator: Analyze text content for safety, appropriateness, and policy compliance. Detects hate speech, violence, sexual content, and other harmful categories. Open-source vision-language model. Ready-to-use REST API, no cold starts, affordable pricing.

Features

Automatically screen text for harmful content with Molmo2 Text Content Moderator. This AI-powered moderation tool analyzes text and returns safety classifications for harassment, hate speech, sexual content, and violence — essential for chat platforms, user-generated content, and compliance workflows.

Why It Works Great

  • Comprehensive detection: Screens for harassment, hate, sexual content, and violence.
  • Child safety: Dedicated detection for content involving minors.
  • Instant results: Near-instant processing for real-time moderation.
  • JSON output: Clean, structured results for easy integration.
  • Ultra-affordable: Just $0.003 per request — 333 requests for $1.
  • Simple integration: Single text input for straightforward API calls.

Parameters

ParameterRequiredDescription
textYesText content to analyze for harmful content.

How to Use

  1. Enter your text — paste or type the content to analyze.
  2. Run — click the button to analyze.
  3. Review results — check the JSON output for safety classifications.

Pricing

Flat rate per text analyzed.

OutputCost
Per request$0.003
100 requests$0.30
1,000 requests$3.00

Output Format

The model returns a JSON object with boolean flags for each content category:

{
 "harassment": false,
 "hate": false,
 "sexual": false,
 "sexual/minors": false,
 "violence": false
}

Detection Categories

CategoryDescription
harassmentBullying, intimidation, or targeted abuse
hateHate speech, discrimination, or prejudice
sexualAdult sexual content or explicit language
sexual/minorsAny sexual content involving minors
violenceThreats, graphic violence descriptions, or harmful content

Best Use Cases

  • Chat Platforms — Moderate messages in real-time.
  • Comments & Reviews — Screen user comments before publishing.
  • Forums & Communities — Ensure posts meet community guidelines.
  • Social Media — Filter text content at scale.
  • Customer Support — Flag abusive messages automatically.
  • Content Pipelines — Pre-screen text before human review.

Pro Tips for Best Results

  • Use as a first-pass filter before human moderation for edge cases.
  • Integrate via API for real-time chat moderation.
  • At $0.003 per request, high-volume moderation is extremely cost-effective.
  • Combine with image and video moderation for comprehensive screening.
  • Process messages as they arrive for instant feedback.

Notes

  • Processing is near-instant for real-time applications.
  • Returns boolean values — true indicates detected content.
  • Designed for automated workflows with JSON output.
  • Consider human review for flagged content or edge cases.
  • Works with any language text input.

Authentication

For authentication details, please refer to the Authentication Guide.

API Endpoints

Submit Task & Query Result

set -euo pipefail

export WAVESPEED_API_KEY="your-api-key"

REQUEST_BODY=$(cat <<'JSON'
{
  "text": "A clear example input"
}
JSON
)

# 1. Submit the prediction.
SUBMIT_RESPONSE=$(curl --silent --show-error --fail-with-body \
  -X POST "https://api.wavespeed.ai/api/v3/wavespeed-ai/molmo2/text-content-moderator" \
  -H "Authorization: Bearer ${WAVESPEED_API_KEY}" \
  -H "Content-Type: application/json" \
  -d "${REQUEST_BODY}")

TASK=$(printf '%s' "${SUBMIT_RESPONSE}" | jq 'if type == "object" and has("data") then .data else . end')
PREDICTION_ID=$(printf '%s' "${TASK}" | jq -r '.id // empty')
if [ -z "${PREDICTION_ID}" ]; then
  printf 'Submission response did not contain a prediction id
' >&2
  exit 1
fi
RESULT_URL=$(printf '%s' "${TASK}" | jq -r '.urls.get // empty')
if [ -z "${RESULT_URL}" ]; then RESULT_URL="https://api.wavespeed.ai/api/v3/predictions/${PREDICTION_ID}/result"; fi

# 2. Poll until the prediction finishes.
while true; do
  RESPONSE=$(curl --silent --show-error --fail-with-body \
    "${RESULT_URL}" \
    -H "Authorization: Bearer ${WAVESPEED_API_KEY}")
  RESULT=$(printf '%s' "${RESPONSE}" | jq 'if type == "object" and has("data") then .data else . end')
  STATUS=$(printf '%s' "${RESULT}" | jq -r '.status // empty')

  case "${STATUS}" in
    completed) printf '%s\n' "${RESULT}" | jq '.outputs'; break ;;
    failed|cancelled|timeout) printf '%s\n' "${RESULT}" | jq . >&2; exit 1 ;;
    created|processing) sleep 2 ;;
    *) printf 'Unexpected status: %s
' "${STATUS}" >&2; exit 1 ;;
  esac
done

Parameters

Task Submission Parameters

Request Parameters

ParameterTypeRequiredDefaultRangeDescription
textstringYes--Text content to moderate and analyze for safety compliance.
enable_sync_modebooleanNofalse-If set to `true`, the request attempts to wait for the generated result and return outputs in the same response. If the result is not ready within the sync wait window, the API can return a timeout body while the task continues processing. This option is only available via the API and is supported only by some models.

Response Parameters

ParameterTypeDescription
codeintegerHTTP status code (e.g., 200 for success)
messagestringStatus message (e.g., “success”)
data.idstringUnique identifier for the prediction, Task Id
data.modelstringModel ID used for the prediction
data.outputsarrayOutput values, usually URL strings; some models return text strings or structured result objects (empty when status is not completed)
data.urlsobjectObject containing related API endpoints
data.urls.getstringURL to retrieve the prediction result
data.statusstringStatus of the task: created, processing, completed, or failed
data.created_atstringISO timestamp of when the request was created (e.g., “2023-04-01T12:34:56.789Z”)
data.errorstringError message (empty if no error occurred)
data.timingsobjectObject containing timing details
data.timings.inferenceintegerInference time in milliseconds

Result Request Parameters

ParameterTypeRequiredDefaultDescription
idstringYes-Task ID

Result Response Parameters

ParameterTypeDescription
codeintegerHTTP status code (e.g., 200 for success)
messagestringStatus message (e.g., “success”)
dataobjectThe prediction data object containing all details
data.idstringUnique identifier for the prediction
data.modelstringModel ID used for the prediction
data.outputsarray<string | object>Array of generated outputs (empty when status is not completed). Items are usually URL strings, but may be text strings or structured result objects, depending on the model.
data.urlsobjectObject containing related API endpoints
data.urls.getstringURL to poll for the prediction result
data.statusstringStatus: created, processing, completed, or failed
data.created_atstringISO timestamp of when the request was created
data.errorstringError message (empty if no error occurred)
data.timingsobjectObject containing timing details
data.timings.inferenceintegerInference time in milliseconds
© 2026 WaveSpeedAI. All rights reserved.