canonical: https://jentic.com/apis/visagecloud.com/visagecloud # VisageCloud 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. ## For AI agents Programmatically get account information by accesskey and secretkey, get billing information by accesskey and secretkey. Covers 52 operations. ## Scope Does not handle payments, crm, or developer tools - use for communications only. ## Capabilities - 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 - Retrieve the last *count* operations per current account ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'get account information by accesskey and secretkey', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/rest/v1.1/account/account` | Get account information by accessKey and secretKey | | GET | `/rest/v1.1/account/billing` | Get billing information by accessKey and secretKey | | POST | `/rest/v1.1/account/changePassword` | Change password for an account using old password | | POST | `/rest/v1.1/account/login` | Get account information including accessKey and secretKey by email and password | | GET | `/rest/v1.1/analysis/compare` | Compare several faces identified by faceHash, without depending on mapping faces | | POST | `/rest/v1.1/analysis/detection` | Perform detection on a given picture or picture URL | | GET | `/rest/v1.1/analysis/listLatest` | Retrieve the last *count* operations per current account | | POST | `/rest/v1.1/analysis/recognition` | Perform labeled recognition on a given picture or picture URL | ## Key resources - **Analytics for presence and audience** — Retrieve analytics for presence and audience - **Stream** — Manages Streams - **Analysis** — Performs image-recognition related operations - **Classifier** — Create classifiers on existing faces - **Collection** — Manages collections ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 70 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 61 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 54 / 100 - Agent Usability: 93 / 100 - Security: 100 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/visagecloud.com/visagecloud/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Twilio** — Alternative communications API - **Sendgrid** — Alternative communications API - **Pusher** — Complementary communications API ## FAQ ### 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. ### Can I limit what my agent is allowed to do with the VisageCloud API? Yes. Jentic One runs self-hosted, so you decide which VisageCloud operations your agent can call and which credential it uses. You can grant only the analysis operations you need, such as face detection, comparison, and labeled recognition, while leaving account-level operations like changing the password out of scope unless you explicitly add them. Because VisageCloud carries its targets in the request body rather than the URL path, this operation-level allow list is what controls what the agent can actually do.