Install Jentic One Beta

Connect the API-NE-PlantillaBaseExample to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API-NE-PlantillaBaseExample, 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.

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%2Fswaggerhub.jhon.hernandez%2Fapi-ne-plantillabaseexample" | sh

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%2Fswaggerhub.jhon.hernandez%2Fapi-ne-plantillabaseexample" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 API-NE-PlantillaBaseExample API.

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}.

GET STARTED

Start building with API-NE-PlantillaBaseExample API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use API-NE-PlantillaBaseExample API for, with concrete tasks.

★ 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.

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.

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.

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

6 endpoints — se debe describir la funcionalidad especificando el alcance y proposito del api capacidades y operaciones: - listar persona.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using API-NE-PlantillaBaseExample API through Jentic.

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.

Jhon Hernandez API-NE-PlantillaBaseExample

Name: API-NE-PlantillaBaseExample API
Brand: API-NE-PlantillaBaseExample
Availability: InStock

Browse all Swaggerhub Jhon Hernandez APIs

Community OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey, bearer6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For 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.

Use for: I need to devuelve el documento persona cuyo idpersona={idpersona} de la colección persona, I want to reemplaza completamente los datos del documento persona cuyo idpersona={idperson, Search for actualiza algunos atributos del documento persona cuyo idpersona={idpersonas}. l, Find all elimina el documento persona cuyo idpersona={idpersonas}.

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

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.

Jentic One on Github View OpenAPI Document