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.
Face Identity is a beta authentication service hosted on Azure App Service that exposes a customer registration and token issuance flow. The two endpoints register a customer record and issue an authentication token that can be used to call protected resources. The surface is minimal and intended as the auth layer in front of a face identity verification stack.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffaceidentity-beta.azurewebsites.net" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffaceidentity-beta.azurewebsites.net" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.