APIs

FaceR API

The Animetrics Face Recognition API can be used to find human faces, detect feature points, correct for off angle photographs, and ultimately perform facial recognition. Information on facial features, including ears, nose, eyebrows, lips, chin are returned as coordinates on the image. The Animetrics Face Recognition API will also detect and return the gender and orientation, or "pose" of faces along 3 axes.

A special capability called "SetPose" is also available which allows the face to be re-rendered at a desired pose that is different than the captured pose. I.e. as if the photo was taken with respect to any desired angle relative to the camera. This is typically used when the facial photo is captured off angle and a zero-corrected fully frontal image (0 degrees pitch, yaw, and roll) is required.

Detected facial features may be corrected or modified to improve the final results of subsequent steps. For example, an eye in the picture may be hidden or obscured; requesting just eye feature points, manually correcting their locations, and feeding this data into a more detailed request will help improve the accuracy of additional feature point and pose detection.
 

VFES API


VFES::processFrame

VFES is a cloud enabled sever supporting a Web Service API for finding, indexing, quality filtering (saliency), and clustering faces from video. It will process video submission requests in parallel--thereby supporting parallel throughput loads--and can process individual videos in parallel.

The API is a RESTful web service supporting two modes of operation, frame by frame and full video. Frame by frame operation allows for the client to parse the video and submit video frames individually, each of which will get processed synchronously. Frames may be submitted in parallel, in which case they will also be processed in parallel by the server. In this way, the client controls the level of parallelization. Full video allows the client to submit an encoded video file. The video is then processed asynchronously and results are pushed to a web service that the client provides.

Additional web services are available to poll the server for processed results. In particular, the client need not provide a web service to receive results but may poll the server instead.