Closed MadelineRitchie closed 4 years ago
@JasonRitchie Thanks for the feedback. We are looking into this and will get back to you soon.
@PatrickFarley @tburns10 FYI. It looks like the API response does not have the gory fields. I have used this image for testing with analyze API and visualFeatures set to Adult.
{
"adult": {
"isAdultContent": false,
"isRacyContent": false,
"adultScore": 0.0069781490601599216,
"racyScore": 0.010386745445430279
},
"requestId": "<request_id>",
"metadata": {
"height": 600,
"width": 519,
"format": "Png"
}
}
@JasonRitchie With the latest version of the API the gory score is returned in the response. Could you please check again with v3.0?
{
"adult": {
"isAdultContent": false,
"isRacyContent": false,
"isGoryContent": false,
"adultScore": 0.0069781490601599216,
"racyScore": 0.010386745445430279,
"goreScore": 9.2131758719915524E-06
},
"requestId": "b833c992-f2f9-4a6d-9138-1cac7d5524a4",
"metadata": {
"height": 600,
"width": 519,
"format": "Png"
}
}
Excellent. Btw the documentation links V2 of the API definition.
How can I find which versions of the API are available? How about upcoming versions?
nevermind I found it. Thanks this resolves my concerns.
The linked page describes the output from the Adult content tagging as also including isGory and a gory confidence score. This feature does not exist as far as I can find in testing or in the API documentation.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.