canonical: https://jentic.com/apis/swaggerhub.jhon.hernandez/api-ne-plantillabaseexample

# Jhon Hernandez API-NE-PlantillaBaseExample

Se DEBE describir la funcionalidad especificando el alcance y proposito del API capacidades y operaciones: - Listar Persona. - Registrar Persona. The API exposes 6 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically devuelve el documento persona cuyo idpersona={idpersona} de la colección persona, reemplaza completamente los datos del documento persona cuyo idpersona={idperson. Covers 6 operations with apiKey, bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Devuelve el documento Persona cuyo idPersona={idPersona} de la colección persona
- Reemplaza completamente los datos del documento Persona cuyo idPersona={idPerson
- Actualiza algunos atributos del documento Persona cuyo idPersona={idPersonas}. L
- Elimina el documento Persona cuyo idPersona={idPersonas}.
- Registra un nuevo documento Persona en la colección personas.

## Use cases

### Developer Tools Operations

Use the API-NE-PlantillaBaseExample to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including devuelve el documento persona cuyo idpersona={idpersona} de la colección persona, reemplaza completamente los datos del documento persona cuyo idpersona={idperson, actualiza algunos atributos del documento persona cuyo idpersona={idpersonas}. l.

Example prompt: Call GET `/personas/{idPersona}` to devuelve el documento persona cuyo idpersona={idpersona} de la colección persona

### Automated Personas Management

Automate personas operations by combining multiple API-NE-PlantillaBaseExample endpoints. Agents can reemplaza completamente los datos del documento persona cuyo idpersona={idperson and then actualiza algunos atributos del documento persona cuyo idpersona={idpersonas}. l in a single workflow.

Example prompt: Call PUT `/personas/{idPersona}` to reemplaza completamente los datos del documento persona cuyo idpersona={idperson, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API-NE-PlantillaBaseExample 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, bearer tokens manually.

Example prompt: Search Jentic for 'devuelve el documento persona cuyo idpersona={idpersona} de la colección persona', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/personas/{idPersona}` | Devuelve el documento Persona cuyo idPersona={idPersona} de la colección persona |
| PUT | `/personas/{idPersona}` | Reemplaza completamente los datos del documento Persona cuyo idPersona={idPerson |
| PATCH | `/personas/{idPersona}` | Actualiza algunos atributos del documento Persona cuyo idPersona={idPersonas}. L |
| DELETE | `/personas/{idPersona}` | Elimina el documento Persona cuyo idPersona={idPersonas}. |
| POST | `/personas` | Registra un nuevo documento Persona en la colección personas. |
| GET | `/personas` | Devuelve un listado de recurso de Personas |

## Key resources

- **Personas** — Operations for personas

## Why Jentic

- **Setup:** Wiring API-NE-PlantillaBaseExample by hand means handling both its Ocp-Apim-Subscription-Key header and a JWT bearer token, then writing your own request and retry logic around the persona reads and writes. Through Jentic you install once, import API-NE-PlantillaBaseExample from the API Directory, store the subscription key and token once, and your agent calls it.
- **Permission scoping:** This API puts the persona id in the URL path (`/personas/{idPersona}`), so a rule can pin your agent to one persona and the operations around it. You choose the operations it may call, so destructive ones like deleting or fully replacing a persona are not included unless you add them.
- **Credential handling:** Your API-NE-PlantillaBaseExample subscription key and bearer token 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 'get a persona record' or 'update a persona', and Jentic returns the matching API-NE-PlantillaBaseExample operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the API-NE-PlantillaBaseExample use?

The API-NE-PlantillaBaseExample uses apiKey, bearer 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 devuelve el documento persona cuyo idpersona={idpersona} de la colección persona with the API-NE-PlantillaBaseExample?

Yes. Use the GET `/personas/{idPersona}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the API-NE-PlantillaBaseExample?

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 devuelve el documento persona cuyo idpersona={idpersona} de la colección persona through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'devuelve el documento persona cuyo idpersona={idpersona} de la colección persona'. Jentic returns the matching API-NE-PlantillaBaseExample operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API-NE-PlantillaBaseExample have?

The API-NE-PlantillaBaseExample exposes 6 endpoints covering personas operations.

### Can I limit what my agent is allowed to do with the API-NE-PlantillaBaseExample?

Yes. Because you run Jentic One yourself, your own rules decide which of the persona operations the agent may call and which stored credentials it may use. Since the persona id sits in the URL path (`/personas/{idPersona}`), you can pin the agent to a single persona and to read-only operations like GET `/personas/{idPersona}` and GET /personas, leaving destructive calls such as DELETE `/personas/{idPersona}` or the full-replace PUT `/personas/{idPersona}` out unless you explicitly grant them. The operator controls this scope, so the agent only ever exercises the operations and keys you have allowed.