LogoAI ForensiX

Introduction

Overview of AI-Forensix, its features, and how to get started with the API.

What is AI-Forensix?

AI-Forensix is a flexible, production-ready deepfake detection platform that delivers fast, multilayered analysis for images, video, audio, text and face biometrics - via a polished UI and a unified REST API. Deployable in the cloud or on-premises, Haranzel routes requests through an API Gateway to dedicated microservices (image, video, audio, text, face, liveliness, remote URL analysis and e-meeting inspection) so you get scalable, low-latency results and clear explainability for each file or stream.


Getting Started

The steps below briefly explain how to integrate the AI-ForensixS API with your app or backend. Follow these steps to create verification tasks, receive notifications, and retrieve analysis results.


1️. Create & Verify Your Account

Step 1 - Register Visit https://developers.haranzel.ai and create your developer account. You will be asked to provide:

Name phone Email Password confirm password

Step 2 - Email Verification Check your inbox for a verification link. Your account becomes active only after email verification.


2️. Choose Your API Services (Scopes)

Once logged in, go to:

Dashboard → API Access → Select Services

Here you can enable the API features you need, such as:

Image Deepfake Detection

Video Analysis

Audio Spoof Detection

Text Integrity Analysis

Face Verification

Face Search & Embeddings

Liveliness Detection

URL-Based Media Analysis

E-Meeting Deepfake Detection

Each service corresponds to an API scope.

You may enable one or multiple scopes based on your use case.


3️. Generate Your API Key

After selecting your scopes, navigate to:

Dashboard → API Keys → Generate New Key

The system will:

Create a unique API key

Bind it to the scopes you selected Display usage limits and expiry (if configured) Use this key in the Authorization header for all API calls:

Authorization: Bearer YOUR_API_KEY

🔒 Important: Your API Key gives direct access to your enabled services - keep it secret and never expose it in client-side code


On this page