With Face Comparison API, you can check if the same person appears in 2 different pictures. Our Artificial Intelligence will allow you to compare and determine if those 2 pictures are, indeed, from the same person.
The API will need you to pass a publicly accessible image URL, and our AI will handle everything. You will receive an intuitive output:
This API will allow you to compare two faces and determine if they belong to the same person. If you want to implement a face validation checkpoint in your office, you could do it with this API.
If you want to compare pictures of different ID's, this API will help you.
Also, if you have a large database of pictures and want to sort them by person, with this API you will be able to accomplish that goal.
The only limitation is the number of API calls you can make per month that support each plan.
This endpoint will receive the image URL and will provide you with the comparison results. You will be able to tell if the two pictures correspond to the same person.
The API will deliver the "is_same" that will determine if they are the same person or not. "true" means same person, "false" means different people.
Also the API will deliver "confidence_score", ranging from 0 (no confidence) to 1 (full confidence). Results with scores closer to 1 are more reliable.
Compare - Endpoint Features
| Object | Description |
|---|---|
hide_analysis |
[Required] false: provide confidence score. true: do not provide analysis scoring. |
url1 |
[Required] First image URL |
url2 |
[Required] Second Image URL |
{"output":{"success":true,"is_same":false,"url1":"https://www.planetegrandesecoles.com/wp-content/uploads/2023/08/brad.jpg","url2":"https://tmhairdesign.com/wp-content/uploads/2023/04/tm-men1_0001_TM-MEN3.jpg"}}
curl --location --request GET 'https://zylalabs.com/api/30/face+comparison+validator+api/5547/compare?hide_analysis=true&url1=https://www.planetegrandesecoles.com/wp-content/uploads/2023/08/brad.jpg&url2=https://tmhairdesign.com/wp-content/uploads/2023/04/tm-men1_0001_TM-MEN3.jpg' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Face Comparison API uses Artificial Intelligence to compare two different pictures and determine if they belong to the same person.
The API requires the publicly accessible image URLs of the two pictures you want to compare.
The API provides an intuitive output in the form of a result message and a similarity percentage.
The result message will indicate whether the two faces belong to different people or the same person.
Yes, the input pictures need to be clean, with a visible and clear face of the person to compare. Blurry images, multiple people in the same picture, and unrecognizable faces may lead to comparison errors.
No, the API only accepts publicly accessible image URLs as input.
Each endpoint returns data related to face comparison results, including whether the faces belong to the same person, a confidence score, and image URLs used in the comparison.
Key fields include "is_same" (true/false), "confidence_score" (0 to 1), and "success" (indicating if the request was processed correctly). Additional fields may include image URLs and result messages.
The response data is structured in JSON format, with a top-level object containing "output" or "data" fields, which encapsulate the results of the face comparison and relevant metadata.
Each endpoint provides information on whether the two images depict the same person, the confidence level of the comparison, and additional metadata such as image URLs and result messages.
Users can customize requests by providing different publicly accessible image URLs for comparison. The API processes these URLs to return tailored results based on the provided images.
"is_same" indicates if the faces are from the same person, "confidence_score" reflects the reliability of the comparison, and "success" shows if the API call was successful.
Data accuracy is maintained through advanced AI algorithms that analyze facial features. Continuous training on diverse datasets helps improve the model's performance and reliability.
Typical use cases include identity verification for security systems, comparing images for fraud detection, and organizing large photo databases by individual identity.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
4,566ms
Service Level:
100%
Response Time:
5,626ms
Service Level:
100%
Response Time:
12,158ms
Service Level:
100%
Response Time:
922ms
Service Level:
100%
Response Time:
280ms
Service Level:
100%
Response Time:
949ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
353ms
Service Level:
100%
Response Time:
20,002ms
Service Level:
100%
Response Time:
20,002ms