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.
{"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.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
642ms
Service Level:
100%
Response Time:
349ms
Service Level:
100%
Response Time:
1,301ms
Service Level:
100%
Response Time:
166ms
Service Level:
100%
Response Time:
5,730ms
Service Level:
100%
Response Time:
1,377ms
Service Level:
100%
Response Time:
1,402ms
Service Level:
100%
Response Time:
2,201ms
Service Level:
100%
Response Time:
1,373ms
Service Level:
100%
Response Time:
709ms