API-based Services
A face recognition API for Indonesia, plus OCR, ANPR and liveness, exposed as clean REST endpoints your developers can integrate in days rather than months.
Request a demo
Alfabeta's API-based Services turn our production computer-vision engines into a face recognition API for Indonesia and a wider toolkit your developers can call over simple REST. Send an image or video frame and receive structured JSON in return: face matches, liveness scores, plate reads or extracted text. Because you consume the engine as an API, your team ships identity, security and analytics features on top of a battle-tested system instead of building, training and hosting models from scratch.
The catalogue mirrors Alfabeta's proven products. Face recognition identifies or verifies a person by comparing their face in real time against pre-existing data. The liveness API complements it by determining whether a face belongs to a real person present at the point of capture or is a spoof artifact such as a photo, video or 3D mask. The OCR API distinguishes, recognises and extracts text from digital images such as scanned documents and ID cards, and the ANPR API reads licence-plate numbers of different colours across various vehicle types using optical character recognition. People counting and related analytics round out the interface.
Integration is designed to be fast and predictable. Every capability is reached through one consistent, language-agnostic HTTPS interface, so any stack, whether Java, Python, PHP, .NET, Node.js or mobile, can call it the same way. Clear references, sample code and sandbox keys let engineers test before they commit, while token authentication, encryption in transit and scoped keys protect every request and response. When data residency or compliance requires it, the same engines can be deployed inside your own network instead of the cloud.
Commercially, the services use a tiered pricing model calculated by monthly API calls, so cost scales with usage and adjusts to your volume, the same model that supports deployments handling well over 400,000 active users per month. Whether you are adding e-KYC to onboarding, embedding face-based access control, integrating plate recognition into a parking flow or automating document capture, the REST integration path keeps engineering effort low and lets you move from prototype to production quickly.
REST-First Endpoints
Language-agnostic HTTPS APIs accept an image or video frame and return structured JSON, so any stack, from Python and Node.js to PHP, Java, .NET or mobile, can integrate the same way in days rather than months. Predictable request and response formats keep the integration simple to build and maintain.
Full Vision Toolkit
One consistent interface exposes the face recognition API, liveness API, OCR API for documents and ID cards, ANPR API for multi-colour plates across vehicle types, and people counting. Combining several engines behind a single integration, for example OCR plus face match plus liveness for e-KYC, needs no extra plumbing.
Developer Documentation
Clear references, sample code and sandbox keys let engineers test each endpoint and validate response formats before going live. Because the APIs expose the same engines behind Alfabeta's production products, behaviour in the sandbox matches behaviour in production.
Secure by Design
Token authentication, encryption in transit and scoped keys protect every request and response, so credentials can be limited to only the endpoints a given application needs. Liveness checks add a further layer against biometric spoofing on identity calls.
Cloud or On-Premise
Consume the engines from Alfabeta's cloud, or deploy them inside your own network to meet data-residency and compliance needs, which matters for financial and government workloads handling sensitive personal data in Indonesia. The API contract stays the same in either model.
Scalable Throughput
Built to handle bursts and sustained high volume, the services already support deployments processing well over 400,000 active users per month. Tiered pricing by monthly API calls means capacity and cost scale together as your product grows.
Frequently asked questions
Which vision capabilities are available as APIs?
The catalogue includes a face recognition API for identifying or verifying a person against existing data, a liveness API to confirm a face is real rather than a spoof artifact, an OCR API for extracting text from documents and ID cards, an ANPR API for reading licence plates across vehicle types and colours, and people counting. All are reached through one consistent REST interface.
How long does integration typically take?
Because every endpoint is a language-agnostic HTTPS API that accepts an image or video frame and returns structured JSON, most teams integrate in days rather than months. Clear documentation, sample code and sandbox keys let engineers test and validate response formats before going live, and any stack, such as Python, Node.js, PHP, Java or .NET, calls the APIs the same way.
How is pricing structured?
The services use a tiered pricing model calculated by monthly API calls, with tiers you adjust to your usage, so cost scales with the volume you actually process. This is the same usage-based model that supports deployments handling well over 400,000 active users per month.
Can we keep data on our own infrastructure?
Yes. You can consume the engines from Alfabeta's cloud, or deploy them on-premise inside your own network to satisfy data-residency and compliance requirements, which is common for financial and government workloads in Indonesia. The API contract is the same in both deployment models.
How do you secure API requests and prevent spoofing?
Requests are protected with token authentication, encryption in transit and scoped keys, so an application's credentials can be restricted to only the endpoints it needs. For identity use cases, the liveness API adds protection against biometric spoofing by rejecting photos, videos and 3D masks presented in place of a real person.