canonical: https://jentic.com/apis/swaggerhub.procesar/selfie-vs-selfie

# Procesar Selfie vs Selfie

Servicio que recibe una(s) imagen(es) de fotografía “selfie” del trabajador y las compara contra las imágenes correspondientes guardadas en BD, del expediente del trabajador. The API exposes 1 endpoints secured with basic authentication.

## For AI agents

Programmatically biométricos - selfie vs selfie. Covers 1 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for media and content only.

## Capabilities

- Biométricos - Selfie vs Selfie
- Manage media data programmatically
- Integrate Selfie vs Selfie into automated workflows
- Query and filter Selfie vs Selfie records by parameters
- Monitor Selfie vs Selfie operational status and events

## Use cases

### Media and Content Operations

Use the Selfie vs Selfie to perform media operations programmatically. The API provides 1 endpoints covering core functionality including biométricos - selfie vs selfie.

Example prompt: Call POST /validafacial to biométricos - selfie vs selfie

### Data Retrieval and Monitoring

Query Selfie vs Selfie resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Selfie vs Selfie endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Selfie vs Selfie 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 basic tokens manually.

Example prompt: Search Jentic for 'biométricos - selfie vs selfie', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/validafacial` | Biométricos - Selfie vs Selfie |

## Key resources

- **Selfie vs Selfie** — recibe una(s) imagen(es) de fotografía “selfie” del trabajador y las compara contra las imágenes cor

## Why Jentic

- **Setup:** Wiring Selfie vs Selfie by hand means learning its HTTP basic auth with an AFORE-issued user and password, pointing at the internal procesar-facial host on 172.21.67.22, and sending the BusinessId and BusinessClient headers on each /validafacial call. Through Jentic you install once, import Selfie vs Selfie from the API Directory, store the basic credentials once, and your agent calls it.
- **Permission scoping:** This service carries the business identifiers in request headers rather than in the URL path, so scoping is by operation: you limit the agent to the operations it needs, here comparing two selfies through /validafacial. Only the operations you allow are callable, so no other biometric action runs unless you add it.
- **Credential handling:** Your Selfie vs Selfie basic credentials 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.
- **Discovery method:** Agents search Jentic by intent such as 'compare two selfies', and Jentic returns the matching Selfie vs Selfie operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

### What authentication does the Selfie vs Selfie use?

The Selfie vs Selfie uses HTTP Basic authentication with username and password. 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 biométricos - selfie vs selfie with the Selfie vs Selfie?

Yes. Use the POST /validafacial endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Selfie vs Selfie?

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 biométricos - selfie vs selfie through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'biométricos - selfie vs selfie'. Jentic returns the matching Selfie vs Selfie operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Selfie vs Selfie have?

The Selfie vs Selfie exposes 1 endpoints covering selfie vs selfie operations.

### Can I limit what my agent is allowed to do with the Selfie vs Selfie API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and scoping here is by operation. The Selfie vs Selfie API exposes a single operation, POST /validafacial, which compares two selfie images, so you allow just that call and no other biometric action can run. The stored HTTP Basic credentials, along with the BusinessId and BusinessClient headers, are injected at execution time and never enter the agent's prompt or context.