Toxicity Detection API API ID: 2260

Safeguard Your Community with our Toxicity Detection API! Harness the power of our Language Understanding API to automatically detect and filter out profanities, toxic content, insults, and more from user-generated content. Prioritize a positive and respectful online environment with our seamless and efficient Toxicity Detection API.
Use this API from your AI agent via MCP
Works with OpenClaw, Claude Code/Desktop, Cursor, Windsurf, Cline and any MCP-compatible AI client.
Docs & setup
Create a skill by wrapping this MCP: https://mcp.zylalabs.com/mcp?apikey=YOUR_ZYLA_API_KEY

About the API: 

 

The Toxicity Detection API is a crucial tool for maintaining a safe and respectful online environment. Specifically designed to analyze user-generated content, this Language Understanding API is dedicated to identifying and filtering out various forms of toxicity. From profanities and insults to severe toxicities, obscene texts, threats, and identity hate, the API employs advanced algorithms to accurately detect harmful content and prevent its dissemination.

For online platforms, social media networks, and community-driven websites, the presence of toxic content can lead to severe consequences, including damaged reputations, decreased user engagement, and potential legal issues. The Toxicity Detection API addresses these concerns by automatically scanning and evaluating user comments, posts, and messages in real-time.

Implementing this API not only helps protect the community members from offensive and harmful content but also empowers platform administrators to take proactive measures to moderate discussions and preserve a positive user experience. By swiftly detecting toxic language, moderators can intervene promptly, mitigate conflicts, and foster a healthy and respectful online community.

The versatility of the Toxicity Detection API extends beyond mere keyword filtering. Employing natural language processing and machine learning techniques, it discerns context and nuances, leading to more accurate assessments. This enables the API to differentiate between harmless banter and genuinely harmful content, minimizing false positives and ensuring that legitimate user interactions are not inadvertently flagged.

Moreover, the API can be seamlessly integrated into existing platforms, applications, and content moderation workflows. Its easy-to-use endpoints and clear documentation facilitate smooth implementation, while its scalable architecture ensures high performance even under heavy loads.

The importance of toxicity detection goes beyond social media and community websites. E-commerce platforms can benefit by filtering product reviews and comments, ensuring that their customers' experiences are not tainted by harmful content. Educational platforms can also utilize the API to maintain a safe learning environment, where students and educators can engage in meaningful discussions without fear of harassment or bullying.

In conclusion, the Toxicity Detection API is an indispensable asset for any online platform or application that values user safety and community well-being. With its comprehensive coverage of profanity and toxicity detection, it equips businesses and organizations with the means to foster respectful online interactions, build trust, and protect their users from harmful content. By implementing this powerful Language Understanding API, developers and administrators can take proactive steps toward creating a positive digital space for everyone.

 

What this API receives and what your API provides (input/output)?

Pass the text that you want to analyze. The API will run an analysis and it will detect the different toxicity entities. 

 

What are the most common uses cases of this API?

  1. Social Media Content Moderation: Social media platforms can integrate the Toxicity Detection API to automatically detect and filter out toxic, offensive, and hateful content in user comments, posts, and messages. This ensures a safer and more welcoming environment for users, promoting healthy discussions and reducing the risk of online harassment.

  2. Community Forum Moderation: Online community forums can utilize the API to moderate user-generated content, flagging and removing toxic language, insults, and threats. By maintaining a respectful and supportive atmosphere, community administrators can encourage more active participation and foster a sense of belonging among members.

  3. E-commerce Product Reviews Filtering: E-commerce websites can employ the Toxicity Detection API to scan and filter product reviews for toxic content or fake reviews. This ensures that the product rating system remains reliable and trustworthy, leading to improved customer trust and informed purchasing decisions.

  4. Educational Platform Content Moderation: Educational platforms and e-learning websites can utilize the API to ensure a safe and inclusive learning environment. By detecting and filtering toxic language in student discussions and comments, educators can foster a positive atmosphere for knowledge sharing and collaboration.

  5. Content Publishing Platforms: Content publishing platforms, including blogs and news websites, can implement the API to moderate user comments and ensure that discussions remain civil and constructive. By curbing toxic behavior, these platforms can enhance reader engagement and cultivate a more respectful online community.

 

Are there any limitations to your plans?

Besides the number of API calls, there is no other limitation

API Documentation

Endpoints


This endpoint detects profanities, toxicities, severe toxicities, obscene texts, insults, threats, and identity hate in a given text.



                                                                            
POST https://zylalabs.com/api/2260/toxicity+detection+api/2126/analyzer
                                                                            
                                                                        

Analyzer - Endpoint Features

Object Description
text [Required]

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

text

API EXAMPLE RESPONSE

{"semantic_analysis":{"0":{"id_semantic_model":2,"name_semantic_model":"toxic","segment":"You idiot!"},"1":{"id_semantic_model":6,"name_semantic_model":"insult","segment":"You idiot!"},"2":{"id_semantic_model":7,"name_semantic_model":"identity_hate","segment":"You idiot!"},"3":{"id_semantic_model":6,"name_semantic_model":"insult","segment":"I will find where you live and kick you ass!"},"4":{"id_semantic_model":5,"name_semantic_model":"threat","segment":"I will find where you live and kick you ass!"}}}

Analyzer - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/2260/toxicity+detection+api/2126/analyzer?text=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Toxicity Detection API simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

🚀 Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

Toxicity Detection API FAQs

Yes, the Toxicity Detection API is designed to handle multiple languages. It employs natural language processing and machine learning models to detect toxic content in text across various languages, making it versatile for global applications.

The API can detect a wide range of toxic content, including profanity, insults, threats, identity hate, severe toxicities, and obscene language. Its comprehensive detection capabilities ensure robust content moderation for different platforms.

The API's accuracy is continually improved through advanced machine learning techniques and regular model updates. However, as with any natural language processing system, occasional false positives or negatives may occur. It is recommended to monitor the API's performance and adjust moderation thresholds based on specific requirements.

Yes, the API is suitable for real-time content moderation due to its low latency and quick response times. Developers can integrate it into chat applications, social media platforms, and live streaming platforms to identify and address toxic content in real-time.

Yes, the Toxicity Detection API can complement existing content moderation systems. Developers can integrate it as an additional layer of defense to enhance the accuracy and efficiency of their moderation efforts, especially when dealing with complex or multilingual content.

The Analyzer endpoint returns a JSON object containing detected toxicities in the input text. It includes segments of text identified as toxic, along with their corresponding toxicity categories such as insults, threats, and identity hate.

The key fields in the response include "semantic_analysis," which contains an array of detected segments. Each segment includes an "id_semantic_model," "name_semantic_model," and the "segment" of text identified as toxic.

The response data is organized in a JSON format. It contains a main object with a "semantic_analysis" field, which is an array of objects, each representing a detected toxic segment with its category and text.

The Analyzer endpoint primarily accepts a single parameter: the text to be analyzed. Users can customize their requests by providing different text inputs to evaluate various user-generated content for toxicity.

Users can utilize the returned data by reviewing the segments flagged as toxic. Each segment can be processed to take appropriate moderation actions, such as removing, flagging, or reviewing the content based on its toxicity level.

Typical use cases include moderating comments on social media, filtering product reviews on e-commerce sites, and ensuring respectful discussions in educational platforms. The data helps maintain a positive online environment.

Data accuracy is maintained through continuous training of machine learning models using diverse datasets. Regular updates and feedback loops help refine the detection algorithms, minimizing false positives and enhancing reliability.

The API employs quality checks such as model validation, performance monitoring, and user feedback analysis. These checks ensure that the toxicity detection remains effective and adapts to evolving language use and context.

General FAQs

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

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.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

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.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs