canonical: https://jentic.com/apis/swaggerhub.devgram/api-de-usuarios

# Devgram User API

An API for managing users. The API exposes 8 endpoints.

## For AI agents

Programmatically access User API resources. Covers 8 operations.

## Scope

Does not handle payments, communications, or crm - use for user management only.

## Capabilities

- 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

## Use cases

### User Management Operations

Use the User API to perform user management operations programmatically. The API provides 8 endpoints for managing users.

Example prompt: Execute a primary operation against the User API

### Automated User Workflows

Automate user operations by combining multiple User API endpoints in a single workflow.

Example prompt: 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.

Example prompt: Search Jentic for 'user API', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/usuarios` | Registrar un nuevo usuario |
| GET | `/usuarios` | Get all users |
| POST | `/usuarios/login` | Iniciar sesión de usuario |
| GET | `/usuarios/{id_usuario}` | Obtener un usuario por ID |
| PUT | `/usuarios/{id_usuario}` | Actualizar un usuario por ID |
| DELETE | `/usuarios/{id_usuario}` | Eliminar un usuario por ID |
| GET | `/usuarios/{id_usuario}/privado` | Obtener información privada de un usuario por ID |
| GET | `/usuarios/{id_usuario}/estadisticas` | Obtener estadísticas de juego de un usuario por ID |

## Key resources

- **Users** — Operations related to Usuarios

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

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