|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Mercury Face OpenAPI (ranked 3179 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/obz45YkzfmpoTdtWFF9eE_mercury_face_openapi_json.jsonGENERAL INFORMATION
Mercury Face Open API offers AI algorithms that detect, recognize, and analyze faces in images through the Mercury platform to empower business for customers. The service provides several different facial analysis functions, which are illustrated in the following sections.
- Face detection: API detects faces in images and returns the rectangle coordinates of faces' locations.
- Face verification: API detects the largest face in 2 images and addresses whether 2 faces are the same person. Verification is also called "one-to-one" or "1:1" matching. Verification can be used in identity verification.
- Face identification: API answers if the detected face can be matched to any enrolled face in feature databases. Because it is like a face recognition search, it is also called "one-to-many" or "1:N" matching.
The API base path is at https://{domain}.japancv.co.jp/openapi/face/v1. Provisioned app_id, access_key, and secret_key are necessary while calling APIs and TLS 1.2 is enforced for al
...
SECURITY 4/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP issues detected: A05:2021
PERFORMANCE 1/5
The performance score is derived from the median response time of the API, sometimes referred as p50. The median is the value separating the higher half from the lower half of a data sample, here the response times of the API.
- The median response time of the API is 1,050 ms .
Get p50 under 220 ms to get a 4/5 score.
RELIABILITY 5/5
The reliability score is derived from the number of inconsistent server responses, either server errors or non-conforming return values.
- Self compliance: response objects matched the declared response types.
- Server errors: the server did not return any 5xx error.
DESIGN 4/5
The design score reflects the quality of the specification file (usually named openapi.json or swagger.json). Having a high-quality specification file (with up-to-date types and examples) help developers understand the API and tools produce relevant documentation.
- Respects OpenAPI 3.0.2 schema specification.
- Contains comments and summaries.
- Contains examples.
- Does not contain duplicated objects.
Popularity 0/5
The popularity score is computed from the number of references to the API found on the internet. Have your API used by many developers to get a higher score!