Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the VisageCloud, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
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%2Fvisagecloud.com%2Fvisagecloud" | 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%2Fvisagecloud.com%2Fvisagecloud" | 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.
What an agent can do with VisageCloud API.
Get account information by accessKey and secretKey
Change password for an account using old password
Compare several faces identified by faceHash, without depending on mapping faces
Perform detection on a given picture or picture URL
GET STARTED
For Agents
Programmatically get account information by accesskey and secretkey, get billing information by accesskey and secretkey. Covers 52 operations.
Use for: I need to account information by accesskey and secretkey, I want to billing information by accesskey and secretkey, Search for change password for an account using old password, Find all account information including accesskey and secretkey by email and password
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
Face search, recognition & classification API. Just make a call to our REST API each time your app needs to access face recognition and classification capabilities. The API exposes 52 endpoints.
Retrieve the last *count* operations per current account
Patterns agents use VisageCloud API for, with concrete tasks.
★ Communications Operations
Use the VisageCloud to perform communications operations programmatically. The API provides 52 endpoints covering core functionality including get account information by accesskey and secretkey, get billing information by accesskey and secretkey, change password for an account using old password.
Call GET /rest/v1.1/account/account to get account information by accesskey and secretkey
Automated Analytics for presence and audience Management
Automate analytics for presence and audience operations by combining multiple VisageCloud endpoints. Agents can get billing information by accesskey and secretkey and then change password for an account using old password in a single workflow.
Call GET /rest/v1.1/account/billing to get billing information by accesskey and secretkey, then verify the result
AI Agent Integration via Jentic
AI agents discover and call VisageCloud endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'get account information by accesskey and secretkey', load the operation schema, and execute with Jentic-managed credentials
52 endpoints — face search, recognition & classification api.
METHOD
PATH
DESCRIPTION
/rest/v1.1/account/account
Get account information by accessKey and secretKey
/rest/v1.1/account/billing
Get billing information by accessKey and secretKey
/rest/v1.1/account/changePassword
Change password for an account using old password
/rest/v1.1/account/login
Get account information including accessKey and secretKey by email and password
/rest/v1.1/analysis/compare
Compare several faces identified by faceHash, without depending on mapping faces
/rest/v1.1/analysis/detection
Perform detection on a given picture or picture URL
/rest/v1.1/analysis/listLatest
Retrieve the last *count* operations per current account
/rest/v1.1/analysis/recognition
Perform labeled recognition on a given picture or picture URL
/rest/v1.1/account/account
Get account information by accessKey and secretKey
/rest/v1.1/account/billing
Get billing information by accessKey and secretKey
/rest/v1.1/account/changePassword
Change password for an account using old password
/rest/v1.1/account/login
Get account information including accessKey and secretKey by email and password
/rest/v1.1/analysis/compare
Compare several faces identified by faceHash, without depending on mapping faces
What agents get from Jentic-routed access to this vendor.
Setup
Wiring VisageCloud by hand means handling its login and account credentials and driving its detection, recognition, and comparison calls yourself. Through Jentic you install once, import VisageCloud from the API Directory, store the credential once, and your agent calls it.
Permission scoping
VisageCloud carries its analysis targets in the request body rather than the URL path, so scope the agent to the operations it needs, such as running face detection or comparing images. You choose that set, so an account-level operation like changing the password is not included unless you add it.
Credential isolation
Your VisageCloud credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'detect faces in an image' or 'compare two faces', and Jentic returns the matching VisageCloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using VisageCloud API through Jentic.
What authentication does the VisageCloud use?
The VisageCloud uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get account information by accesskey and secretkey with the VisageCloud?
Yes. Use the GET /rest/v1.1/account/account endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the VisageCloud?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get account information by accesskey and secretkey through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get account information by accesskey and secretkey'. Jentic returns the matching VisageCloud operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the VisageCloud have?
The VisageCloud exposes 52 endpoints covering analytics for presence and audience, stream, analysis operations.
/rest/v1.1/analysis/detection
Perform detection on a given picture or picture URL
/rest/v1.1/analysis/listLatest
Retrieve the last *count* operations per current account
/rest/v1.1/analysis/recognition
Perform labeled recognition on a given picture or picture URL