Protective Equipment Detection API

Protective Equipment Detection API

Protective Equipment Detection API uses computer vision to detect and identify protective equipment (PE) on individuals in images. It provides information about bounding boxes, confidence scores, and boolean values for whether PE covers specific body parts such as the face, hands, and head. It can be used for compliance monitoring, safety assessments, and other applications.

API description

About the API:

The Protective Equipment Detection API is a computer vision tool that can detect and identify protective equipment (PE) on individuals in images or videos. The API provides a wealth of information about the detected PE, including bounding boxes and confidence scores for persons and PE, as well as boolean values and confidence scores for whether PE covers specific body parts such as the face, hands, and head.

This API can be used in a variety of applications, including compliance monitoring, safety assessments, and more. For example, organizations can use it to monitor compliance with safety regulations, such as ensuring that employees are wearing the required PPE in a factory or construction site. It can also be used in public spaces to ensure that individuals are wearing the required face coverings.

The API is easy to use and can be integrated into a wide range of systems and platforms. It can process images and videos in real time, making it useful for live monitoring, surveillance, and other applications. Additionally, the API can be configured to work with different types of PE, such as face masks, goggles, hard hats, and more.

Overall, the Protective Equipment Detection API is a powerful tool for organizations looking to ensure compliance with safety regulations and protect the health and well-being of employees and the public. With its ability to detect and identify a wide range of PE, it can help organizations quickly and easily identify individuals who are not wearing the required PPE.

 

API Documentation

Endpoints


Provides information about bounding boxes and confidence for persons and PE detected, scores for the body parts detected, and boolean values and confidence for whether the PE covers the corresponding body part. PE detected are: Face cover, Hand cover, Head cover.



                                                                            
POST https://zylalabs.com/api/1061/protective+equipment+detection+api/931/pe+detection
                                                                            
                                                                        

PE Detection - Endpoint Features
Object Description
Request Body [Required] Json
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"ProtectiveEquipmentModelVersion": "1.0", "Persons": [{"BodyParts": [{"Name": "FACE", "Confidence": 99.94153594970703, "EquipmentDetections": []}, {"Name": "LEFT_HAND", "Confidence": 98.54450988769531, "EquipmentDetections": []}, {"Name": "RIGHT_HAND", "Confidence": 92.44161224365234, "EquipmentDetections": []}, {"Name": "HEAD", "Confidence": 99.99492645263672, "EquipmentDetections": [{"BoundingBox": {"Width": 0.15085314214229584, "Height": 0.1711052507162094, "Left": 0.31052398681640625, "Top": 0.11813429743051529}, "Confidence": 99.52413177490234, "Type": "HEAD_COVER", "CoversBodyPart": {"Confidence": 99.99185943603516, "Value": true}}]}], "BoundingBox": {"Width": 0.38950276374816895, "Height": 0.8426501154899597, "Left": 0.19751381874084473, "Top": 0.11180124431848526}, "Confidence": 99.95264434814453, "Id": 0}], "Summary": {"PersonsWithRequiredEquipment": [0], "PersonsWithoutRequiredEquipment": [], "PersonsIndeterminate": []}}
                                                                                                                                                                                                                    
                                                                                                    

PE Detection - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/1061/protective+equipment+detection+api/931/pe+detection' --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 Protective Equipment Detection API REST 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 commitments. One click upgrade/downgrade or cancellation. No questions asked.

🚀 Enterprise
Starts at $10,000/Year

  • Custom Volume
  • Dedicated account manager
  • Service-level agreement (SLA)

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

Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.

Prices are listed in USD. 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 with paying by card, just contact us at [email protected]

Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further

Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.

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.

Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.

Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.

You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]

 Service Level
100%
 Response Time
1,664ms

Useful links:


Category:


Tags:


Related APIs