How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kairos AR Face Recognition API

Detect, enroll, verify and recognize faces in photos against galleries.

Kairos AR Face Recognition API is one of 3 APIs that Kairos AR publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Face Recognition. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 4 operations across 4 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.kairos.com.

4 operations 4 paths 11 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.kairos.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Kairos AR Face Recognition API declares 2 security schemes for authenticating requests. An API key is passed in the header as app_id (app_id). An API key is passed in the header as app_key (app_key). By default, every request must be authenticated.

  • app_id — Your Kairos APPID, from https://developer.kairos.com.
  • app_key — Your Kairos APPKEY, from https://developer.kairos.com.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 POST. Each is listed below with its method, path, parameters, and response codes.

Face Recognition 4

Detect, enroll, verify and recognize faces in photos against galleries.

POST
/enroll
Enroll a face into a gallery
enroll body → 200
POST
/verify
Verify a face against an enrolled subject
verify body → 200
POST
/recognize
Recognize faces against a gallery
recognize body → 200
POST
/detect
Detect faces and facial features
detect body → 200

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Transaction (11 properties), FaceAttributes (9 properties), EnrollRequest (5 properties), RecognizeRequest (5 properties). Each schema is shown below with its type and property counts.

Candidate
object
3 properties
VerifyRequest
object
3 properties 3 required
FaceAttributes
object
9 properties
RecognizeRequest
object
5 properties 2 required
ErrorEnvelope
object
Kairos error envelope, returned (typically with HTTP 200) on failure.
1 property
RecognitionResult
object
1 property
Transaction
object
11 properties
DetectRequest
object
3 properties 1 required
EnrollRequest
object
5 properties 3 required
DetectResult
object
1 property
EnrollResult
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kairos-ar-face-recognition-api-openapi.yml Raw ↑

Other APIs Kairos AR publishes across the network.

Kairos AR Emotion Analysis API
Kairos AR Galleries API
Where this information came from

This is an independent, third-party profile of Kairos AR Face Recognition API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.