SkyBiometry Face Detection and Recognition API
49
AI ReadinessFoundational (D+)49/100
Official vendor OpenAPI document · agent-readyCRMCustomer SupportapiKey14 EndpointsREST
For Agents
Programmatically test authentication, check usage limits. Covers 14 operations with apiKey authentication.
Use for: I need to test authentication, I want to check usage limits, Search for namespaces, Find all users in namespaces
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
SkyBiometry provides a cloud-based face detection and recognition API. Detect faces in images, recognize trained users, manage face tags, and train face templates for identification. Supports both JSON and XML response formats. The API exposes 14 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the SkyBiometry Face Detection and Recognition API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SkyBiometry Face Detection and Recognition API, 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.
1
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%2Fskybiometry.com%2Fskybiometry" | sh2
Step 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%2Fskybiometry.com%2Fskybiometry" | 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.
Capabilities
What an agent can do with SkyBiometry Face Detection and Recognition API.
Test authentication
Check usage limits
List namespaces
Detect faces in images (POST)
Recognize faces in images
Use Cases
Patterns agents use SkyBiometry Face Detection and Recognition API for, with concrete tasks.
★ CRM Operations
Use the SkyBiometry Face Detection and Recognition API to perform crm operations programmatically. The API provides 14 endpoints covering core functionality including test authentication, check usage limits, list namespaces.
Call GET /account/authenticate.json to test authentication
Automated Account Management
Automate account operations by combining multiple SkyBiometry Face Detection and Recognition API endpoints. Agents can check usage limits and then list namespaces in a single workflow.
Call GET /account/limits.json to check usage limits, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SkyBiometry Face Detection and Recognition API 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 apiKey tokens manually.
Search Jentic for 'test authentication', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
14 endpoints — skybiometry provides a cloud-based face detection and recognition api.
METHOD
PATH
DESCRIPTION
GET
/account/authenticate.json
Test authentication
GET
/account/limits.json
Check usage limits
GET
/account/namespaces.json
List namespaces
GET
/account/users.json
List users in namespaces
POST
/faces/detect.json
Detect faces in images (POST)
GET
/faces/detect.json
Detect faces in images
GET
/faces/recognize.json
Recognize faces in images
GET
/faces/train.json
Train face templates
GET
/account/authenticate.json
Test authentication
GET
/account/limits.json
Check usage limits
GET
/account/namespaces.json
List namespaces
GET
/account/users.json
List users in namespaces
POST
/faces/detect.json
Detect faces in images (POST)
GET
/faces/detect.json
Detect faces in images
GET
/faces/recognize.json
Recognize faces in images
GET
/faces/train.json
Train face templates
Jentic AI Readiness Score
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.
S
SkyBiometry Face Detection and Recognition API
- Foundational (D+)49/100
100
Foundational Compliance69
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience94
Agent Usability15
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
69
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
1%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
40%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
52%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SkyBiometry Face Detection and Recognition API by hand means passing both api_key and api_secret as query parameters to api.skybiometry.com/fc on every call and tracking your account limits yourself. Through Jentic you install once, import SkyBiometry from the API Directory, store the key and secret once, and your agent calls it.
Permission scoping
SkyBiometry passes its targets in query parameters rather than resource ids in the path, so limit the agent to the operations it needs, such as detecting or recognizing faces. Training and account user operations are not included unless you add them to the allowed set.
Credential isolation
Your SkyBiometry API key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'detect faces in an image' or 'recognize a trained face', and Jentic returns the matching SkyBiometry operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using SkyBiometry Face Detection and Recognition API through Jentic.
What authentication does the SkyBiometry Face Detection and Recognition API use?
The SkyBiometry Face Detection and Recognition API uses an API key passed in the `api_key` query. 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 test authentication with the SkyBiometry Face Detection and Recognition API?
Yes. Use the GET /account/authenticate.json endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SkyBiometry Face Detection and Recognition API?
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 test authentication through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'test authentication'. Jentic returns the matching SkyBiometry Face Detection and Recognition API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SkyBiometry Face Detection and Recognition API have?
The SkyBiometry Face Detection and Recognition API exposes 14 endpoints covering account, faces, tags operations.
Can I limit what my agent is allowed to do with the SkyBiometry Face Detection and Recognition API?
Yes. Because you run Jentic One yourself, your own rules decide which SkyBiometry operations and credentials the agent may use. SkyBiometry passes its targets in query parameters rather than resource ids in the path, so you can restrict the agent to only the operations it needs, such as detecting or recognizing faces via /faces/detect.json and /faces/recognize.json. Training operations like /faces/train.json and account user operations such as /account/users.json stay off-limits unless you add them to the allowed set.
GET STARTED