Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the User API, 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.devgram%2Fapi-de-usuarios" | shStep 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.devgram%2Fapi-de-usuarios" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with User API.
Access User API resources via REST API
Manage user data programmatically
Integrate User API into automated workflows
Query and filter User API records by parameters
Monitor User API operational status and events
GET STARTED
Patterns agents use User API for, with concrete tasks.
★ User Management Operations
Use the User API to perform user management operations programmatically. The API provides 8 endpoints for managing users.
Execute a primary operation against the User API
Automated User Workflows
Automate user operations by combining multiple User API endpoints in a single workflow.
Create and manage users via the User API
AI Agent Integration via Jentic
AI agents discover and call User API 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.
Search Jentic for 'user API', load the operation schema, and execute with Jentic-managed credentials
8 endpoints — an api for managing users.
METHOD
PATH
DESCRIPTION
/usuarios
Registrar un nuevo usuario
/usuarios
Get all users
/usuarios/login
Iniciar sesión de usuario
/usuarios/{id_usuario}
Obtener un usuario por ID
/usuarios/{id_usuario}
Actualizar un usuario por ID
/usuarios/{id_usuario}
Eliminar un usuario por ID
/usuarios/{id_usuario}/privado
Obtener información privada de un usuario por ID
/usuarios/{id_usuario}/estadisticas
Obtener estadísticas de juego de un usuario por ID
/usuarios
Registrar un nuevo usuario
/usuarios
Get all users
/usuarios/login
Iniciar sesión de usuario
/usuarios/{id_usuario}
Obtener un usuario por ID
/usuarios/{id_usuario}
Actualizar un usuario por ID
/usuarios/{id_usuario}
Eliminar un usuario por ID
/usuarios/{id_usuario}/privado
Obtener información privada de un usuario por ID
/usuarios/{id_usuario}/estadisticas
Obtener estadísticas de juego de un usuario por ID
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the User API by hand means reading its OpenAPI definition, pointing at the right SwaggerHub server, and hand-coding each user operation and its retries yourself. Through Jentic you install once, import the User API from the API Directory, store any credential it needs once, and your agent calls it.
Permission scoping
The User API puts the user id in the URL path (/usuarios/{id_usuario}), so a rule can pin your agent to one user: it can read that user's profile, private data, and statistics and nothing else. You choose the operations it may call, so destructive ones like deleting a user are not included unless you add them.
Credential isolation
Any credential this API requires is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a user account' or 'fetch a user's statistics', and Jentic returns the matching User API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using User API through Jentic.
What authentication does the User API use?
The User API uses none 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.
What are the rate limits for the User API?
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 use user API through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use user API'. Jentic returns the matching User API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the User API have?
The User API exposes 8 endpoints covering users operations.
Does the User API support pagination?
Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.
Can I limit what my agent is allowed to do with the User API?
Yes. Because you run Jentic One yourself, your own rules decide which User API operations and credentials the agent may use. Since the user id sits in the URL path (/usuarios/{id_usuario}), you can pin the agent to a single user so it only reads that user's profile, private data, and game statistics. You pick the operations it may call, so destructive ones like deleting a user with DELETE /usuarios/{id_usuario} are left out unless you explicitly grant them.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically access User API resources. Covers 8 operations.
Use for: I need to integrate with User API, Find available user management operations, Get the current status of User API resources, List all records from User API
Not supported: Does not handle payments, communications, or crm - use for user management only.
An API for managing users. The API exposes 8 endpoints.