About the API:
Object detection is a computer vision technique that allows us to identify and locate objects in an image or video. With this kind of identification and localization, object detection can be used to count objects in a scene and determine and track their precise locations, all while accurately labeling them.
This API will receive an image URL and it will be delivering the position of the object it recognizes and, also, a label of the object. Ex "Chair", or "Car".
Also, this API has the ability to retrieve a new modified image with all the located objects and it's positions.
Object Recognition APIs are vastly used in different places such as:
Because state-of-the-art object detection techniques can accurately identify and track multiple instances of a given object in a scene, these techniques naturally lend themselves to automated video surveillance systems.
For instance, object detection models are capable of tracking multiple people at once, in real-time, as they move through a given scene or across video frames. From retail stores to industrial factory floors, this kind of granular tracking could provide invaluable insights into security, worker performance and safety, retail foot traffic, and more.
Crowd counting is another valuable application of object detection. For densely populated areas like theme parks, malls, and city squares, object detection can help businesses and municipalities more effectively measure different kinds of traffic—whether on foot, in vehicles, or otherwise.
This ability to localize and track people as they maneuver through various spaces could help businesses optimize anything from logistics pipelines and inventory management, to store hours, to shift scheduling, and more. Similarly, object detection could help cities plan events, dedicate municipal resources, etc.
Real-time car detection models are key to the success of autonomous vehicle systems. These systems need to be able to identify, locate, and track objects around them in order to move through the world safely and efficiently.
And while tasks like image segmentation can be (and often are) applied to autonomous vehicles, object detection remains a foundational task that underpins current work on making self-driving cars a reality.
Besides the number of API calls per month, there are no other limitations.
Retrieve the positions of the detected objects and their labels.
Object | Description |
---|---|
url |
[Required] The image URL that you want to extract the objects and their positions from. |
{"number-of-objects":2,"detected-objects":[{"label":"chair","confidence":85.10388135910034,"bounding-box":[{"x":0.008685767650604248,"y":0.5896903872489929},{"x":0.2699936330318451,"y":0.5896903872489929},{"x":0.2699936330318451,"y":0.9812138676643372},{"x":0.008685767650604248,"y":0.9812138676643372}]},{"label":"pottedplant","confidence":67.13606715202332,"bounding-box":[{"x":0.8753650784492493,"y":0.4638286232948303},{"x":0.9942767024040222,"y":0.4638286232948303},{"x":0.9942767024040222,"y":0.8214828372001648},{"x":0.8753650784492493,"y":0.8214828372001648}]}]}
curl --location --request POST 'https://zylalabs.com/api/130/object+recognition+api/173/get+coordenates?url=https://www.cinch.co.uk/static/33916de99a6cf53e7a430f9f862a3296/99791/home-hero.png' --header 'Authorization: Bearer YOUR_API_KEY'
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 Object Recognition API REST API, simply include your bearer token in the Authorization header.
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
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,165ms
Service Level:
43%
Response Time:
1,666ms
Service Level:
100%
Response Time:
4,162ms
Service Level:
67%
Response Time:
4,757ms
Service Level:
100%
Response Time:
3,841ms
Service Level:
75%
Response Time:
2,864ms
Service Level:
100%
Response Time:
717ms
Service Level:
98%
Response Time:
1,294ms