This API leverages the latest advances in natural language processing and machine learning algorithms to accurately identify and score harmful comments, posts and messages. This means that organizations and websites can tailor the moderation system to their specific needs and requirements, whether it's blocking certain words or phrases, or identifying patterns of behavior that may indicate toxic, obscene, or abusive behavior. This is a great help as it allows them to effectively moderate content in multiple languages and maintain a safe and welcoming environment.
Educational platforms can use the API to monitor student discussions for any toxic or offensive language, creating a healthy learning environment. Job posting websites can use the API to monitor comments on job postings and detect any toxic or offensive language.
Overall, the Multilingual ML-based toxicity profanity moderator for user-generated content API is an essential tool for organizations and websites looking to create a safe and welcoming online environment for their users. With its advanced machine learning algorithms, it provides a powerful and effective solution for detecting toxic and offensive content, helping to create a more positive and inclusive online experience for all.
What your API receives and what your API provides (input/output)?
It will receive a parameter and provide you with a JSON.
Social Media Platforms: Social media platforms can use the API to automatically detect and remove harmful and offensive comments on posts, ensuring that users have a safe and positive experience.
Online Discussion Forums: Online discussion forums can use the API to moderate user-generated content and ensure that discussions remain respectful and on-topic.
E-commerce Websites: E-commerce websites can use the API to monitor customer reviews and feedback, ensuring that all comments are appropriate and free from toxic language.
Gaming Communities: Gaming communities can use the API to moderate in-game chat and remove any toxic or offensive language, creating a safer and more enjoyable experience for all players.
News Websites: News websites can use the API to monitor comments on articles and remove any toxic or offensive language, ensuring that readers have a positive experience.
1 request per second.
Basic Plan: 100,000 API Calls. 50 requests per second.
Pro Plan: 300,000 API Calls. 50 requests per second.
Pro Plus Plan: 900,000 API Calls. 50 requests per second.
Premium Plan: 2,300,000 API Calls. 50 requests per second.
To use this endpoint you must enter a text in the parameter.
Toxic Detection - Endpoint Features
| Object | Description |
|---|---|
text |
[Required] |
{"original": "damn it", "censored": "**** it", "has_profanity": true}
curl --location --request GET 'https://zylalabs.com/api/1364/toxic+text+detector+api/6111/toxic+detection?text=damn it' --header 'Authorization: Bearer YOUR_API_KEY'
| 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 Toxic Detection endpoint returns a JSON object containing the original text, a censored version of the text, and a boolean indicating whether the text contains profanity.
The key fields in the response data are "original" (the input text), "censored" (the text with profanity replaced by asterisks), and "has_profanity" (a boolean indicating the presence of offensive language).
The response data is structured as a JSON object with three fields: "original," "censored," and "has_profanity," allowing for easy parsing and utilization in applications.
The primary parameter for the Toxic Detection endpoint is the text input, which users must provide to analyze for toxic language.
Users can customize their requests by varying the input text to analyze different phrases or comments for toxicity, tailoring the moderation to specific content types.
Typical use cases include moderating comments on social media, filtering user-generated content in forums, and ensuring appropriate language in gaming chats.
Data accuracy is maintained through advanced machine learning algorithms that continuously learn from diverse datasets, ensuring effective detection of toxic language across various contexts.
Quality checks include regular updates to the machine learning models, validation against real-world data, and user feedback mechanisms to improve detection capabilities over time.
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:
950ms
Service Level:
100%
Response Time:
246ms
Service Level:
100%
Response Time:
61ms
Service Level:
100%
Response Time:
65ms
Service Level:
100%
Response Time:
65ms
Service Level:
100%
Response Time:
382ms
Service Level:
100%
Response Time:
74ms
Service Level:
100%
Response Time:
580ms
Service Level:
100%
Response Time:
188ms
Service Level:
100%
Response Time:
582ms
Service Level:
100%
Response Time:
249ms
Service Level:
100%
Response Time:
751ms
Service Level:
100%
Response Time:
44ms
Service Level:
100%
Response Time:
4,671ms
Service Level:
100%
Response Time:
2,001ms
Service Level:
100%
Response Time:
2,708ms
Service Level:
100%
Response Time:
4,553ms
Service Level:
100%
Response Time:
1,563ms
Service Level:
100%
Response Time:
2,921ms
Service Level:
100%
Response Time:
166ms