FaceCoreFacial recognition API
Face verification for any system through a REST API. FaceCore checks that a real person is in front of the camera, blocks photos and screens, and confirms their identity. Processing time is logged for every verification.
1:1 · 1:N
1:1 verification and 1:N identification
20
Matches per 1:N search
50
People per enrollment request
- Face detection
- Liveness check
- Anti-spoofing
- Comparison with the enrolled face
From enrollment to a verified match.
Four stages in a single API. The application captures the images and FaceCore returns a conclusive result.
Enrollment
One-time registration of each person with 1 to 3 frontal photos, or up to 50 people per request.
Liveness challenge
Optionally, a random action: blink, turn left or right, or smile.
Verification
Liveness confirmation, blocking of photos and screens, and face comparison.
Result
A JSON response with scores and a conclusive result: approved or rejected.
Liveness detection
Confirms in real time that the person is physically present.
Anti-spoofing
Blocks presentation attacks with printed photos and screens.
REST API
Simple JSON endpoints, protected with an API key per client.
Attendance control
Clock-in and clock-out validated with face verification.
Access control
A verification result your access system uses to admit only the right person.
Runs on CPU only
No GPU required. ATSC hosts and operates the service, and your system only calls the API.
One request, a conclusive result.
The request includes the images and the challenge. FaceCore responds with the match, liveness and anti-spoofing results.
POST /api/v1/verifyX-API-Key: <your_api_key>Content-Type: application/json{ "external_id": "emp_10482", "frames": ["<base64>", "<base64>", "<base64>"], "challenge_id": "ch_7f3a"}{ "verified": true, "similarity_score": 0.91, "liveness_score": 0.88, "anti_spoof_score": 0.97, "liveness_passed": true, "anti_spoof_passed": true}Integration
Endpoints that do the heavy lifting.
Enterprise use cases.
FaceCore integrates with the systems the organization already uses.
Attendance and shifts
Facial clock-in that eliminates buddy punching and shared cards.
Access control
Doors, turnstiles and restricted areas open only for enrolled people.
1:N identification
Search for the closest matches across every enrolled person.
Integration with your platforms
Any web or mobile application can call the REST API with its own key.
Control over every integration.
FaceCore runs on CPU on infrastructure that ATSC hosts and operates. The organization controls who uses the API and what each key can do.
Scoped keys
Independent permissions per API key: enroll, verify, liveness or admin. Optional expiration and revocation at any time.
Per-key limits
Per-endpoint limits for each key. When exceeded, the API responds 429 with Retry-After.
Complete audit log
Every verification is logged with its result, scores and key. Every response includes a request_id.
Deletion on request
When a person is deleted, their template is removed from search and their stored images are erased.
FaceCore FAQ.
Answers about scope, services and how we work.
Integrate face verification into your system.
Share your use case and receive API access, with technical guidance for the first integration.
More from ATSC
Complementary platforms
More services