Content Safety Moderator API uses AI to detect and classify harmful content in text.
Built for social platforms, forums, chat applications, comment systems, and any app that needs to moderate user-generated content.
Analyzes text content for safety and returns toxicity scores and category classifications.
Moderate Content - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"safe":true,"riskScore":0,"riskLevel":"none","categories":{"violence":{"detected":false,"confidence":0},"hate":{"detected":false,"confidence":0},"sexual":{"detected":false,"confidence":0},"selfHarm":{"detected":false,"confidence":0},"profanity":{"detected":false,"confidence":0},"harassment":{"detected":false,"confidence":0},"criminal":{"detected":false,"confidence":0},"childExploitation":{"detected":false,"confidence":0},"weapons":{"detected":false,"confidence":0},"privacy":{"detected":false,"confidence":0}},"flaggedCategories":[],"summary":"The message is safe and contains no harmful content.","language":"en"}
curl --location --request POST 'https://zylalabs.com/api/12320/content+safety+moderator+api/23139/moderate+content' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"text":"Hello, this is a friendly test message."}'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Content Safety Moderator API can detect various types of harmful content including toxic, offensive, hateful, threatening, and inappropriate text.
The API classifies content into several categories such as hate speech, harassment, self-harm, violence, and sexual content, providing a clear understanding of the nature of the detected harmful content.
The API returns confidence scores for each category of harmful content detected, along with an overall safety verdict indicating whether the content is safe or unsafe.
The API is designed for use in social platforms, forums, chat applications, comment systems, and any application that requires moderation of user-generated content to ensure a safe environment.
The API accepts text input for analysis and returns structured output in a format that includes category classifications, confidence scores, and an overall safety verdict.
The Moderate Content endpoint returns structured data that includes an overall safety verdict, risk scores, category classifications, and confidence levels for various types of harmful content detected in the analyzed text.
Key fields in the response include "safe" (boolean), "riskScore" (numeric), "riskLevel" (string), "categories" (object with detected content types), "flaggedCategories" (array), and "summary" (string describing the content's safety).
The response data is organized into a JSON structure, with top-level fields for safety verdicts and risk assessments, followed by a detailed breakdown of category classifications and their respective confidence scores.
The Moderate Content endpoint primarily accepts a single parameter: the text content to be analyzed. Users can customize their requests by providing different text inputs for moderation.
Users can utilize the returned data by interpreting the "safe" field to determine content safety, using "riskScore" for severity assessment, and referring to "categories" for specific harmful content types to inform moderation actions.
Typical use cases include moderating user comments on social media, filtering chat messages in forums, and ensuring safe content in online communities by automatically flagging harmful text for review.
Data accuracy is maintained through continuous training of the AI model on diverse datasets, regular updates to improve detection capabilities, and validation against real-world examples of harmful content.
Standard data patterns include a clear indication of whether content is safe or unsafe, detailed confidence scores for each category, and a summary that succinctly describes the analysis outcome, aiding in quick decision-making.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
642ms
Service Level:
100%
Response Time:
349ms
Service Level:
100%
Response Time:
166ms
Service Level:
100%
Response Time:
1,301ms
Service Level:
100%
Response Time:
5,730ms
Service Level:
100%
Response Time:
1,377ms
Service Level:
100%
Response Time:
2,201ms
Service Level:
100%
Response Time:
1,402ms
Service Level:
100%
Response Time:
1,373ms
Service Level:
100%
Response Time:
752ms
Service Level:
100%
Response Time:
3,408ms
Service Level:
100%
Response Time:
2,239ms
Service Level:
100%
Response Time:
839ms
Service Level:
100%
Response Time:
426ms
Service Level:
100%
Response Time:
524ms
Service Level:
100%
Response Time:
57ms
Service Level:
100%
Response Time:
149ms
Service Level:
100%
Response Time:
118ms
Service Level:
100%
Response Time:
32ms
Service Level:
100%
Response Time:
784ms