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

# Procesar Selfie vs Otro Expediente

Servicio que recibe una imagen en el request y dos claves para realizar la búsqueda en FILENET: cveExpe y cveImgExpe, estas claves son enviadas a FILENET para obtener la fotografía del expediente solicitado con base en la clave proceso para realizar la comparación entre ambas fotografías. The API exposes 1 endpoints secured with basic authentication.

## For AI agents

Programmatically biométricos - selfie vs otro expe. 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 Otro Expe
- Manage storage data programmatically
- Integrate Selfie vs Otro Expediente into automated workflows
- Query and filter Selfie vs Otro Expediente records by parameters
- Monitor Selfie vs Otro Expediente operational status and events

## Use cases

### Storage and Databases Operations

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

Example prompt: Call POST /validafacialexpe to biométricos - selfie vs otro expe

### Data Retrieval and Monitoring

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

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/validafacialexpe` | Biométricos - Selfie vs Otro Expe |

## Key resources

- **Selfie vs Otro Expe** — Recibe una imagen en el request y dos claves para realizar la búsqueda en FILENET: cveExpe y cveImgE

## Why Jentic

- **Setup:** Wiring Selfie vs Otro Expediente by hand means learning its HTTP basic auth with an AFORE-issued user and password, choosing between its internal 172.21.67.22 and 192.168.1.73 procesar-facial hosts, and sending the BusinessId and BusinessClient headers on each /validafacialexpe call. Through Jentic you install once, import Selfie vs Otro Expediente 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 another 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 Otro Expediente 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 another file', and Jentic returns the matching Selfie vs Otro Expediente 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 Otro Expediente use?

The Selfie vs Otro Expediente 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 otro expe with the Selfie vs Otro Expediente?

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 Otro Expediente?

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

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

The Selfie vs Otro Expediente exposes 1 endpoints covering selfie vs otro expe operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials your agent may use, and scoping here is by operation. This service has a single operation, POST /validafacialexpe, which matches a selfie against another expediente photo in FILENET, so you allow only that call and nothing else runs. No other biometric action is callable unless you explicitly add it, and your basic credentials stay in your own instance rather than the agent context.