About the API:
This API brings the latest technology to recognize any improper images that you want to filter. It's useful to recognize any violent situations in a given image.
This API will receive an image URL as a parameter, just that. The output will be a percentage between 0.01 to 0.99, where closer to 0.99 means that the picture is unsafe or qualifies for a ban.
This API is ideal for those who want to keep their pages, blogs, or platforms free of offensive or inappropriate image content.
Be ready to dynamically filter any image that wouldn't meet your policy requirements and prepare to have an "E" rated platform.
Besides the number of API calls per month, there are no other limitations.
With a given image URL, you will be able to detect any gore content. Be able to filter the images if they have blood in them.
Also, you will be able to detect if they have any graphic violence or horrific imagery as well.
You will be getting the probability of gore content on a scale of 0.01 to 0.99, where 0.99 is the most probable and 0.01 is the less probable.
Violence Detection - Endpoint Features
| Object | Description |
|---|---|
url |
[Required] The URL of the image you want to check. |
{
"status": "success",
"request": {
"id": "req_fW5lXW2dVoP1fVAM0CIao",
"timestamp": 1711121007.016218,
"operations": 1
},
"gore": {
"prob": 0.63
},
"media": {
"id": "med_fW5lpkaik3gUEG0nXJTMu",
"uri": "https://upload.wikimedia.org/wikipedia/commons/6/69/Zombie_Walk_Cannes_2013.JPG"
}
}
curl --location --request POST 'https://zylalabs.com/api/556/violence+detection+-+image+moderation+api/396/violence+detection?url=https://upload.wikimedia.org/wikipedia/commons/6/69/Zombie_Walk_Cannes_2013.JPG' --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.
Each endpoint returns a JSON response containing the status of the request, a unique request ID, a timestamp, and specific detection results. For example, the Violence Detection endpoint returns a probability score indicating the likelihood of gore content in the image.
Key fields in the response include "status" (indicating success or failure), "request" (with ID and timestamp), and specific detection results like "gore" (with a probability score) for the Violence Detection endpoint.
The response data is structured in a JSON format with nested objects. The main object contains "status," "request," and specific detection results (e.g., "gore" for violence detection), allowing for easy parsing and access to relevant information.
Each endpoint provides information on specific content types: the Violence Detection endpoint identifies gore and graphic violence, the Nudity Detection endpoint checks for nudity, and the Alcohol Detection endpoint detects alcohol presence in images.
The primary parameter for each endpoint is the image URL, which must be provided in the request. This allows the API to analyze the specified image for the relevant content type.
Users can utilize the returned probability scores to filter content based on their policies. For instance, a score above 0.5 in the Violence Detection endpoint may trigger content moderation actions, ensuring compliance with platform standards.
Data accuracy is maintained through advanced machine learning algorithms trained on diverse datasets. Continuous updates and quality checks ensure the API adapts to new content types and improves detection capabilities over time.
Typical use cases include content moderation for social media platforms, blogs, and forums to prevent the sharing of inappropriate images. Businesses can use the API to ensure compliance with community guidelines and maintain a safe environment for users.
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.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
1,289ms
Service Level:
100%
Response Time:
1,341ms
Service Level:
100%
Response Time:
770ms
Service Level:
100%
Response Time:
1,301ms
Service Level:
100%
Response Time:
7,377ms
Service Level:
100%
Response Time:
231ms
Service Level:
100%
Response Time:
166ms
Service Level:
100%
Response Time:
1,079ms
Service Level:
100%
Response Time:
1,199ms
Service Level:
100%
Response Time:
831ms
Service Level:
100%
Response Time:
53ms
Service Level:
100%
Response Time:
148ms
Service Level:
100%
Response Time:
255ms
Service Level:
100%
Response Time:
307ms
Service Level:
100%
Response Time:
135ms
Service Level:
100%
Response Time:
215ms
Service Level:
100%
Response Time:
77ms
Service Level:
100%
Response Time:
743ms
Service Level:
100%
Response Time:
108ms
Service Level:
100%
Response Time:
48ms