People Drowning Detection API
SC DE VIS SOFTWARE SRL · Software Development
Certification per Microsoft Marketplace.
Evidence tier Source Confirmed · 7 captures on record
What the publisher says
As described on Microsoft Marketplace.
People Drowning Detection API - Drownerizer (also known as People Drowning Recognition API or People Drowning Detector API) is a cross browsers REST API which get a JSON input with a still photo (as base64 encoded string), containing people in the water that might or might not be in danger to drown and returns a JSON string which contains predictions of the input photo regarding the probability of People Drowning. The recognized People Drowning have confidence score, timestamp, tagId, tagName. Of course, there are some limitations in order to get a higher accuracy. We recommend properly exposed, unobstructed JPEG photos at 1920x1080 (full HD resolution) where the People Drowning is clear and focused. If the People Drowning details are too small or blured, the accuracy is lower and the AI algorithm may not classify in a proper way. We do not store pictures. Also, the quality and the angles of the camera are very important and it contribute to a higher reading accuracy. It should has varifocal lenses, high shutter speed, good infrared lighting beam, full HD resolution.
Allthough this Automatic People Drowning Detection API (currently we do not offer a People Drowning Detection sdk) is intended for software development and therefore developers, we have also here an People Drowning Detection online application that may be used to check the input and output JSONs of the API. The necessary steps are written below, basically for this real time People Drowning Detection API you send an authorized POST request in JSON format to the API endpoint and you get as JSON response the output as described below through parameters and examples.
Show the rest of the publisher’s description (1 more line)
This People Drowning Detection API is useful for a large number of domains like apps for: security cameras for cruise ships, pontoons in ports, ships, areas with drowning danger that are not usual visited by people, etc. You own the commercial copyright of the resulted JSON with no additional fee meaning you may use it in your own apps for sale.
Preview
1 image
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Sources
Publisher resources
6 linksLinked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.