Now Live — Works with Claude, ChatGPT, Gemini

The Biometric Gateway

One API that streams real-time biometric events from any device brand to any AI workflow, ERP, or application — instantly. No SDK. No vendor lock-in.

FREE Sandbox API key in 30 seconds — no credit card, no time limit.

80000+
Machines
1000+
Partners
11000+
Clients
104+
Countries

Live active customer base · refreshed monthly

ISO 9001 certified ISO 27001 certified GDPR & DPDP aligned No raw biometric data on Cams servers TLS in transit · AES-256 at rest Full policy →

100% Global Device Compatibility — Works with every major brand

Why Biometric Gateway

One gateway ends the integration chaos

Every biometric vendor ships a different SDK, protocol, and data format. Integrating even two brands is months of work. Cams Biometric Gateway solves this at the infrastructure layer.

Without a Gateway

  • A different SDK per vendor — ZKTeco, Suprema, Hikvision each require separate integration code
  • Proprietary binary protocols — impossible to standardize without deep reverse-engineering
  • Vendor lock-in — switching hardware means rewriting your entire attendance stack
  • No AI access — biometric data stays trapped inside legacy middleware
  • On-premise only — no cloud streaming, no real-time webhooks, no REST API

With Cams Biometric Gateway

  • One REST API for all devices — ZKTeco, Suprema, Hikvision, and 100+ brands unified
  • Standardised JSON payloads — every punch, enrollment, and command in the same schema
  • Hardware-agnostic architecture — swap devices without touching your application code
  • MCP-ready — connect Claude, GPT-4o, Gemini directly to your biometric infrastructure
  • Cloud-native real-time streaming — sub-second push events, no polling required
Now Available — AI & MCP

Your AI agents can now control biometric machines

Connect Claude, GPT-4o, Gemini, or any MCP-compatible AI agent to the Biometric Gateway. Manage thousands of devices, enroll users, and stream attendance — all through natural language.

MCP Endpoint

https://mcp.camsbiometrics.com/mcp

n8n / Make / Zapier workflows

Trigger biometric operations from any automation platform

50 devices in 10 seconds

Mass enroll, block, or sync users across your entire fleet instantly

Claude (MCP) GPT-4o Gemini n8n Make Zapier
mcp.camsbiometrics.com/mcp
$ mcp connect https://mcp.camsbiometrics.com/mcp
✓ Connected to Biometric Gateway (v2.4.1)
✓ 847 devices online · 104 countries · 500M+ punches/day
AI> "Show all offline devices in Dubai"
Found 3 offline devices in Dubai, UAE:
· Device #DXB-0412 — Al Barsha Hub (offline 2h 14m)
· Device #DXB-0891 — Downtown Office (offline 14m)
· Device #DXB-1203 — JBR Marina (offline 6m)
AI> "Enroll John Smith on all 3 Dubai devices"
✓ Enrollment queued for DXB-0412, DXB-0891, DXB-1203
✓ Biometric templates syncing... completed in 38 seconds
✓ Access granted on 3 devices
# 50+ devices managed in < 10 seconds via natural language

Read the Claude AI integration guide →

Quick Start

Live in three steps · under 30 minutes

No SDK. No vendor calls. Pure HTTP — works with any language, any environment, any biometric device brand.

01

Plug in your device ~8 min

Register any fingerprint, face, palm, or RFID device on the Gateway. Native Push for internet-enabled devices (sub-second latency), Hybrid Push for legacy or air-gapped fleets. ZKTeco, Suprema, Hikvision, Anviz, eSSL, Morpho — all work out of the box.

02

See your first event ~min 12

First punch hits your callback URL within minutes. Standardised JSON across every device brand — attendance, enrollment, temperature, mask detection — same schema. Wire it to your webhook, log it, sync your DB, fire a Slack message. Done.

03

Ship the workflow ~min 30

Use 27 RESTful commands to enroll users, block access, sync templates, retrieve logs. Or hand it to Claude / ChatGPT / Gemini via MCP and manage the whole fleet through natural language. From zero to production workflow in your first half-hour.

API Reference

38 operations.
Zero SDK.

All payloads are raw JSON over HTTPS. Works with PHP, Node.js, Python, Go, Java, Ruby — any language that can make an HTTP request.

Callback APIs (11) — Device → Server
  • Real-time attendance punch
  • Photo capture on punch
  • Temperature monitoring
  • Face-mask detection
  • User enrollment push
  • Biometric template sync
  • User deletion event
  • Date/time modification
  • Profile update
  • Access window change
  • Device status alert
RESTful APIs (27) — Server → Device
  • Add user (single / batch)
  • Delete user / all users
  • Enable / disable access
  • Fingerprint enrollment
  • Face template enrollment
  • Palm vein enrollment
  • Update access time window
  • Load attendance logs
  • Device info & capacity
  • Clear logs / photos
  • Resend missed data
  • + 16 more operations
Fingerprint Face Recognition Palm Vein Iris RFID / NFC QR Code GPS Tracking Temperature
Sample — Attendance Callback (Device → Your Server) ● LIVE
// POST https://your-server.com/attendance-callback
// Authorization: Bearer <your-auth-token>

{
  "UserId": "EMP1042",
  "LogTime": "2026-05-02 09:14:27 GMT +0000",
  "DeviceId": "DXB-0891",
  "AttDirection": 0,  // 0=check-in, 1=check-out
  "VerifyMode": 1,   // 1=fingerprint
  "Temperature": 36.7,
  "Photo": "<base64-jpeg>",
  "Latitude": 25.2048,
  "Longitude": 55.2708
}
99.95%
Uptime SLA
≤250ms
Webhook latency
30-day
Retry queue · zero loss
24×7
Security monitoring
30+
Device brands · one API
In Production

What partners are running on Cams

Anonymized snapshots from across the network — magnitudes drawn from live partner deployments.

4,000+

An HRMS partner running biometric attendance across SMBs in 3 regions

India, MENA, and Africa — one Cams integration, customers buying whatever device brand is locally cheapest. Zero device-driver work on the partner side.

HRMS · multi-region
1,200+

A school-management platform deployed biometric check-in in 8 months

Campuses live across primary, secondary, and tertiary education. Push events to the partner's webhook directly — no polling, no per-vendor SDK juggling.

School · push webhooks
850+

A regional payroll vendor onboarded enterprise customers with zero device-side code

User-management + attendance log retrieval over REST. Customer keeps their existing hardware. Partner shipped the integration in 2 weeks of engineering time.

Payroll · REST-only
Integration Ecosystem

Connects to your entire stack

Pre-built integration modules for the world's leading ERP, HRMS, payroll, and AI workflow platforms. Zero custom development required.

ERP / HRMS / Payroll

AI Workflow Platforms

Use Cases

Attendance & Payroll
Access Control
Fleet & Vehicle Auth
Asset Tracking
School Management
Healthcare & Labs
Our Partner Network

Trusted by 1,000+ integration partners worldwide

ERP vendors, HR platforms, system integrators and consultants — across 104+ countries.

Transparent Pricing

Simple, device-based pricing

One-time activation + low annual renewal. No per-transaction fees. No user-count limits. Scale freely once activated.

Cams Devices

Native Push

For all Cams Biometrics hardware — SlimBeast, Macronium, Hawking, Ultron, Galaxy series. Full REST API + real-time callbacks.

$120 one-time
+ ₹5,750 activation · ₹3,000–₹6,000 /yr renewal
  • All 38 API operations
  • Sub-second real-time push
  • Full user & biometric management
  • MCP / AI agent access
  • $60–$120 annual renewal
Enterprise

Protocol Engine Lite

On-premise deployment for LAN-only environments, air-gapped networks, or large-scale self-hosted biometric infrastructure.

$500– $10,000
Based on scale · Contact sales for custom quote
  • On-premise / LAN deployment
  • Air-gapped network support
  • Dedicated support SLA
  • Custom protocol adapters
  • White-label available
About Cams Biometrics

Built by Dheeram Innovations Pvt Ltd · since 2016

Founder & CEO PRP · Chennai, India · LinkedIn →

80K+
Devices
11K+
Customers
104
Countries
Frequently Asked

Common questions

The questions buyers and partners ask most often. Want a deeper answer? Chat on WhatsApp or email sales.

Does Cams Biometrics store our customers' biometric data?

No raw biometric data is stored on Cams servers. Templates live on the devices themselves and on your customer's server. Encrypted mathematical representations pass through our Gateway temporarily for synchronization, and transaction queues retain delivery data for up to 30 days. Nothing biometric is permanently stored on our side.

Full details in the privacy policy §3.3 and §6.

Which biometric device brands are supported?

ZKTeco, Suprema BioStar, Hikvision, Anviz, eSSL, Matrix COSEC, Morpho / IDEMIA, Virdi, Nitgen, Realtime / Startek, Mantra, Secugen, Biomax, and our own Cams Biometrics hardware — plus 90+ other brands via the Hybrid Push connector.

If your device speaks HTTP or has any documented protocol, we can integrate it. Customers buy whatever hardware is locally available; one Cams integration covers them all.

How long does integration take?

First attendance event flowing into your callback URL in under 12 minutes. Full production workflow shipped in under 30 minutes. No SDK installation, no vendor negotiations — just HTTP and a webhook.

See the API documentation for the exact sequence, or jump to the three-step walkthrough above.

What does it cost?

Device-based pricing with one-time activation plus a low annual renewal:

· Cams devices (Native Push): $120 one-time + ₹3,000–6,000/yr renewal · tier details

· Third-party devices (Hybrid Push): $150 one-time + ₹4,500–7,500/yr renewal

· Enterprise (Protocol Engine Lite): $500–$10,000 scale-based, on-premise / air-gapped

No per-transaction fees. No user-count caps. Free sandbox key for evaluation.

Do I need to host my own server?

No — Cams Biometric Gateway is fully cloud-hosted. You only need a publicly reachable webhook URL on your side.

For air-gapped / LAN-only / on-premise deployments, Protocol Engine Lite runs locally on Windows or Linux and syncs with the Gateway when reachable. Same API, deployed on your hardware.

Is the platform secure?

ISO 9001 and ISO 27001 certified. GDPR and India DPDP-aligned. TLS encryption in transit, AES-256 at rest. MFA, RBAC, 24×7 security monitoring, audit logging on every biometric transaction.

The Gateway is built as a pass-through, not a data lake — raw biometric data never lands on our servers. Full posture in the privacy policy.

Can AI agents (Claude / ChatGPT / Gemini) control biometric machines?

Yes. The Gateway exposes an MCP endpoint at https://mcp.camsbiometrics.com/mcp. Any MCP-compatible AI agent — Claude, ChatGPT, Gemini, n8n / Make / Zapier workflows — can enroll users, manage devices, retrieve attendance logs, and stream events via natural language.

See the Claude integration guide for a worked example.

What if my customers are still using legacy or closed-network devices?

That's exactly what Hybrid Push and Protocol Engine Lite are for. The local connector translates legacy protocols (TCP, serial, vendor-binary) into the same standardised JSON your application already consumes from internet-enabled devices.

Same API surface, same payload shape — your application code stays unchanged whether the customer has a brand-new face-recognition device on Wi-Fi or a 10-year-old fingerprint reader on a LAN.

Get Started

Start building in minutes

Your first biometric event flowing into your application in under 30 minutes. No SDK. No vendor calls. Just HTTP.

Community Forum  ·  Device Compatibility Check  ·  Instant Code Generator

Try again
Try again