Face Comparison Validator API

With this API you will be able to recognize if in 2 pictures the same person appears or not.

About the API:

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. 

What your API receives and what your API provides (input/output)?

The API will need you to pass a  publicly accessible image URL, and our AI will handle everything. You will receive an intuitive output: 

  • is_same: this object will say either "true" or "false. Where "true" informs that the two faces belongs to the same person and "false" informing that there are different people. 
  • confidence_score: this score will go from 0 to 1. Determining the condifence of the analysis.

 

{
    "output": {
        "success": true,
        "is_same": true,
        "confidence_score": 0.8072144555914527,
        "url1": "https://e00-telva.uecdn.es/assets/multimedia/imagenes/2023/07/04/16884784570312.jpg",
        "url2": "https://www.planetegrandesecoles.com/wp-content/uploads/2023/08/brad.jpg"
    }
}

 

What are the most common uses cases of this API?

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. 

Are there any limitations with your plans?

The only limitation is the number of API calls you can make per month that support each plan. 

API Documentation

Endpoints


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.



                                                                            
GET https://www.zylalabs.com/api/30/face+comparison+validator+api/5547/compare
                                                                            
                                                                        

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
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"output":{"success":true,"is_same":true,"confidence_score":0.8072144555914527,"url1":"https://www.planetegrandesecoles.com/wp-content/uploads/2023/08/brad.jpg","url2":"https://e00-telva.uecdn.es/assets/multimedia/imagenes/2023/07/04/16884784570312.jpg"}}
                                                                                                                                                                                                                    
                                                                                                    

Compare - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/30/face+comparison+validator+api/5547/compare?hide_analysis=false&url1=https://www.planetegrandesecoles.com/wp-content/uploads/2023/08/brad.jpg&url2=https://e00-telva.uecdn.es/assets/multimedia/imagenes/2023/07/04/16884784570312.jpg' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Face Comparison Validator API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

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.

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, look at the β€˜X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.

To see the maximum number of API requests your plan allows, check the β€˜X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.

The β€˜X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

 Service Level
98%
 Response Time
1,043ms

Category:


Related APIs