Content Moderator Image API Documentation
Playground
Try it on WaveSpeedAI!Image Content Moderator provides automated image moderation to detect and flag policy-violating or inappropriate images for automation. Ready-to-use REST inference API, best performance, no coldstarts, affordable pricing.
Features
Ensure your images meet safety and compliance standards with WaveSpeed AI’s Content Moderator. This fast, affordable moderation tool analyzes images for policy violations, inappropriate content, and safety concerns — essential for platforms, applications, and workflows that handle user-generated content.
Why It Works Well
- Fast analysis: Quick moderation results for high-volume workflows.
- Comprehensive detection: Identifies various types of inappropriate or unsafe content.
- Text context support: Optionally include associated text for more accurate moderation decisions.
- Ultra-affordable: At just $0.001 per image, scale moderation without breaking the budget.
- Simple integration: Minimal parameters make it easy to add to any pipeline.
Parameters
| Parameter | Required | Description |
|---|---|---|
| image | Yes | Image to moderate (upload or public URL). |
| text | No | Optional associated text for additional context in moderation. |
How to Use
- Upload your image — drag and drop or paste a public URL.
- Add text context (optional) — include any associated text that should be considered.
- Run — click the button to analyze.
- Review results — check the moderation output for any flagged content.
Pricing
Flat rate per moderation request.
| Output | Cost |
|---|---|
| Per image | $0.001 |
Best Use Cases
- User-Generated Content — Screen uploads before publishing to your platform.
- Social Media & Communities — Maintain safe spaces by filtering inappropriate images.
- E-commerce — Ensure product listings meet marketplace content policies.
- Content Pipelines — Add automated safety checks to media processing workflows.
- AI Output Screening — Verify generated images comply with safety guidelines before delivery.
Pro Tips for Best Results
- Include associated text when available — it helps provide context for more accurate moderation.
- Use in automated pipelines for consistent, scalable content screening.
- Combine with human review for edge cases or appeals.
- Set up batch processing for high-volume moderation needs.
- If using URLs, ensure they are publicly accessible for successful analysis.
Notes
- If using a URL for the image, ensure it is publicly accessible.
- Moderation results should be used as guidance — consider human review for borderline cases.
- Processing is typically very fast, suitable for real-time moderation workflows.
- The text field can provide valuable context for images with ambiguous content.
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/content-moderator/image" \
-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
doneParameters
Task Submission Parameters
Request Parameters
| Parameter | Type | Required | Default | Range | Description |
|---|---|---|---|---|---|
| image | string | No | - | Image to be moderated. | |
| text | string | No | - | - | Text to be moderated. |
| enable_sync_mode | boolean | No | false | - | 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
| Parameter | Type | Description |
|---|---|---|
| code | integer | HTTP status code (e.g., 200 for success) |
| message | string | Status message (e.g., “success”) |
| data.id | string | Unique identifier for the prediction, Task Id |
| data.model | string | Model ID used for the prediction |
| data.outputs | array | Output values, usually URL strings; some models return text strings or structured result objects (empty when status is not completed) |
| data.urls | object | Object containing related API endpoints |
| data.urls.get | string | URL to retrieve the prediction result |
| data.status | string | Status of the task: created, processing, completed, or failed |
| data.created_at | string | ISO timestamp of when the request was created (e.g., “2023-04-01T12:34:56.789Z”) |
| data.error | string | Error message (empty if no error occurred) |
| data.timings | object | Object containing timing details |
| data.timings.inference | integer | Inference time in milliseconds |
Result Request Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| id | string | Yes | - | Task ID |
Result Response Parameters
| Parameter | Type | Description |
|---|---|---|
| code | integer | HTTP status code (e.g., 200 for success) |
| message | string | Status message (e.g., “success”) |
| data | object | The prediction data object containing all details |
| data.id | string | Unique identifier for the prediction |
| data.model | string | Model ID used for the prediction |
| data.outputs | array<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.urls | object | Object containing related API endpoints |
| data.urls.get | string | URL to poll for the prediction result |
| data.status | string | Status: created, processing, completed, or failed |
| data.created_at | string | ISO timestamp of when the request was created |
| data.error | string | Error message (empty if no error occurred) |
| data.timings | object | Object containing timing details |
| data.timings.inference | integer | Inference time in milliseconds |