Food Categories Recognition API
SC DE VIS SOFTWARE SRL · Software Development
Certification per Microsoft Marketplace.
Evidence tier Source Confirmed · 8 captures on record
What the publisher says
As described on Microsoft Marketplace.
Food Categories Recognition API - Foodivisus (also known as Food Categories detection API) is a cross browsers REST API which get a JSON input with a still photo (as base64 encoded string) or an url of the image and returns a JSON string which contains predictions with certain amount of probability (filtered for output with minimum 20%), which contain the basic Organic Food Categories (breads, cereals, cheese, eggs, fat meat, fish, fruits, greens, lean meat, milk, noodles, nuts, pasta, poultry, rice, sea fruits, vegetables, yogurt) each of it based on the detected food category from the input photo. If the probability of prediction is under 20% then these info are not shown. This API is optimized for raw / fresh / frozen products as they are sold on the market.
Allthough this Food Categories Recognition API (currently we do not offer a Food Categories recognition sdk) is intended for software development and therefore developers, we have also here a Food Categories detection online application that may be used to check the input and output JSONs of the API.
Show the rest of the publisher’s description (2 more lines)
The necessary steps are written below, basically for this real time Food Categories detection or recognition 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.
This Food Categories Recognition API is useful for a large number of domains like: owners or administrators of food e-commerce websites, professionals, nutritionists, students, researchers, developers, food manufacturers and distributors, food retailers 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.