canonical: https://jentic.com/apis/faceidentity-beta.azurewebsites.net/face-identity

# Faceidentity Beta Face Identity API

Jentic publishes the only available OpenAPI specification for Face Identity API, keeping it validated and agent-ready. The Face Identity API registers customer identities and issues access tokens for them. You enroll a customer through the registration operation and then obtain a token that your application can use to represent that authenticated customer, covering the enrollment and token-issuance steps of a face-based identity flow.

## For AI agents

Register customer identities and issue access tokens for them through the Face Identity API, covering the enrollment and token-issuance steps of a face-based authentication flow.

## Scope

Covers customer registration and access-token issuance only. Does not manage roles, verify documents, or provide the underlying face recognition model.

## Capabilities

- Register a new customer identity for face-based authentication
- Enroll a customer through a single onboarding operation
- Issue an access token for a registered customer
- Obtain a token that downstream services can verify
- Authenticate a returning customer to receive a fresh token

## Use cases

### AI Agent Customer Onboarding

An AI agent can enroll a new customer into a face-based identity system by calling the registration operation with the customer's details. Through Jentic the agent finds this operation by intent and passes the required fields, so an onboarding assistant can create customer identities without a developer wiring the endpoint by hand.

Example prompt: Register a new customer with the required details and confirm the identity was created

### Token Issuance for Sessions

An authentication agent can start a session for a registered customer by issuing an access token. The API returns a token that the application uses on subsequent calls, so an agent can complete the login step of a workflow and hand the token to the rest of the system.

Example prompt: Issue an access token for a registered customer and return it for the session

### Identity Enrollment in Signup Flows

A signup workflow can register a customer and immediately obtain a token so the new user is ready to act. Because the API covers both enrollment and token issuance, an agent can chain the two steps to onboard and authenticate a customer in a single flow.

Example prompt: Register a customer, then issue a token so the new customer can start a session

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/authentication/customer/registration` | Register a new customer identity |
| POST | `/authentication/customer/token` | Issue an access token for a customer |

## Key resources

- **Customer Registration** — Enroll a new customer identity into the system
- **Access Token** — Issue an access token for a registered customer

## Why Jentic

- **Setup:** Because Jentic maintains the only structured spec for this beta API, wiring it by hand means reading undocumented endpoints and guessing the request shapes. Through Jentic you install once, import the API from the Directory, and your agent calls the registration and token operations with a validated schema.
- **Permission scoping:** You choose which Face Identity operations the agent may call. A rule can allow only customer registration, or only token issuance, so the agent works within the exact set of operations you approved and nothing more.
- **Credential handling:** Face Identity declares no API key in its spec, so there is nothing sensitive to manage. The access token this API issues is returned in the response for your application to use, and Jentic runs every call under your own instance and logs it.
- **Discovery method:** Agents search Jentic by intent such as 'register a customer' or 'issue an access token', and Jentic returns the matching Face Identity operation with its input schema so the agent calls the right endpoint.

## Related APIs

- **Auth0** — Auth0 provides full authentication, token issuance, and user management.
- **FaceCheck** — FaceCheck searches for a face across the web for verification.
- **Clarifai** — Clarifai offers image and face recognition models.

## FAQ

### Why is there no official OpenAPI spec for Face Identity API?

Face Identity does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Face Identity API via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Face Identity MCP server?

You don't need an MCP server to give your agent the Face Identity API. Jentic connects it directly from the API Directory: import it and your agent can register customers and issue tokens. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

### Can I limit what my agent is allowed to do with the Face Identity API?

Yes. You choose which operations the agent may call, so you can allow it to register customers but not issue tokens, or the reverse. The agent cannot reach any operation you did not pick, and every call it makes through your own instance is logged.

### Does the Face Identity API need authentication?

The OpenAPI spec declares no authentication scheme, so no API key is required to call these endpoints. The endpoints themselves handle identity: one registers a customer and the other issues an access token your application then uses.

### Can my agent register a customer and then log them in with the Face Identity API?

Yes. The agent can call the registration operation to enroll a customer and then the token operation to issue an access token for that customer. Chaining the two lets a signup workflow onboard and authenticate a user in one flow.

### What are the rate limits for the Face Identity API?

The OpenAPI spec does not specify rate limits. This is a beta service, so confirm the current limits and availability with the provider before relying on it in production.