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

# Procesar Selfie vs Expediente Identificación

Servicio que recibe una imagen en el request, busca en base de datos el expediente de identificación (01) permanente (estatus 5), y con los datos obtenidos del expediente, realiza la búsqueda en FILENET para descargar la fotografía del trabajador asociada a ese expediente. The API exposes 1 endpoints secured with basic authentication.

## For AI agents

Programmatically biométricos - selfie vs expe identificación. Covers 1 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for storage and databases only.

## Capabilities

- Biométricos - Selfie vs Expe Identificación
- Manage storage data programmatically
- Integrate Selfie vs Expediente Identificación into automated workflows
- Query and filter Selfie vs Expediente Identificación records by parameters
- Monitor Selfie vs Expediente Identificación operational status and events

## Use cases

### Storage and Databases Operations

Use the Selfie vs Expediente Identificación to perform storage operations programmatically. The API provides 1 endpoints covering core functionality including biométricos - selfie vs expe identificación.

Example prompt: Call POST /validafacialexpe to biométricos - selfie vs expe identificación

### Data Retrieval and Monitoring

Query Selfie vs Expediente Identificación 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 Expediente Identificación endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Selfie vs Expediente Identificación 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 expe identificación', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/validafacialexpe` | Biométricos - Selfie vs Expe Identificación |

## Key resources

- **Selfie vs Expe Identificación** — Recibe una imagen en el request, busca en base de datos el expediente de identificación (01) permane

## Why Jentic

- **Setup:** Wiring Selfie vs Expediente Identificacion 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 /validafacialexpe call. Through Jentic you install once, import Selfie vs Expediente Identificacion 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 matching a selfie against the identification file through /validafacialexpe. Only the operations you allow are callable, so no other biometric action runs unless you add it.
- **Credential handling:** Your Selfie vs Expediente Identificacion 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 'match a selfie against the identification file', and Jentic returns the matching Selfie vs Expediente Identificacion operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Dropbox** — Alternative storage API
- **Box** — Alternative storage API
- **Amazonaws** — Complementary storage API

## FAQ

### What authentication does the Selfie vs Expediente Identificación use?

The Selfie vs Expediente Identificación 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 expe identificación with the Selfie vs Expediente Identificación?

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

### What are the rate limits for the Selfie vs Expediente Identificación?

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 expe identificación 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 expe identificación'. Jentic returns the matching Selfie vs Expediente Identificación operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Selfie vs Expediente Identificación have?

The Selfie vs Expediente Identificación exposes 1 endpoints covering selfie vs expe identificación operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials your agent may use, and this API scopes access by operation. You can allow only POST /validafacialexpe, which matches a submitted selfie against the permanent identification file, so that is the single call your agent can make. No other biometric action runs unless you explicitly add it, and your stored basic credentials plus the required business-identifier headers are supplied at execution time rather than exposed to the agent.