L = -1/N ∑ [y_i log(ŷ_i) + (1 - y_i) log(1 - ŷ_i)]Attention(Q, K, V) = softmax(QK^T / √d_k)Vf(x) = 1 / (1 + e^{-x})∇ × E = -∂B/∂tH(p, q) = -∑ p(x) log q(x)E[X] = ∫ x f(x) dxP(A|B) = P(B|A)P(A) / P(B)w^T x + b = 0θ_{t+1} = θ_t - η ∇_θ J(θ)
[HASANTAVISION]
PRIVACY-FIRST CV
{ }

MAKE YOUR APP SEE

Select a demo or product to preview media.

Back to Home
Integration Notes

API Docs

Use these notes to evaluate integration fit before requesting production access. Paid onboarding includes credentials, exact base URLs, request limits, and service-specific examples.

Server-side keys

Keep API keys on your backend. Browser clients should call your own server, not Hasantavision directly.

Sensitive data review

Identity, workplace, and document workflows should define consent, retention, and access control before launch.

Latency targets

Share expected image size, request volume, and deployment region during onboarding so limits are realistic.

Observable errors

Treat non-2xx responses as operational events and log request IDs when provided.

Services

01 // Endpoints
/api/face-recognition/v1/compare

Face Recognition

Input

Two face images as base64 JSON or multipart files

Output

Similarity score, match decision, threshold, processing time

/api/ocr/v1/extract

OCR / Document AI

Input

Document image as multipart form data

Output

Text, fields, document type, confidence, bounding boxes

/api/liveness/v1/detect

Liveness Detection

Input

Face image as multipart form data

Output

Live/spoof decision, confidence, depth, texture, reflection scores

/api/ppe/v1/detect

PPE Detection

Input

Workspace image as multipart form data

Output

Person boxes, hardhat/mask/glove flags, compliance score

Request Pattern

POST /api/ocr/v1/extract
Authorization: Bearer <server-side-api-key>
Content-Type: multipart/form-data

[email protected]

Client-side demos on this website call Next.js proxy routes so API keys stay server-side. Production integrations should follow the same pattern.

Ready for Credentials?

Select an API tier and include expected request volume, data type, latency target, and deployment environment. That context determines the safest onboarding path.

View API Plans