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

# Devgram Game Management API

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

## For AI agents

Programmatically access Game Management API resources. Covers 8 operations.

## Scope

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

## Capabilities

- Access Game Management API resources via REST API
- Manage game data programmatically
- Integrate Game Management API into automated workflows
- Query and filter Game Management API records by parameters
- Monitor Game Management API operational status and events

## Use cases

### Game Management Operations

Use the Game Management API to perform game management operations programmatically. The API provides 8 endpoints for managing games.

Example prompt: Execute a primary operation against the Game Management API

### Automated Game Workflows

Automate game operations by combining multiple Game Management API endpoints in a single workflow.

Example prompt: Create and manage games via the Game Management API

### AI Agent Integration via Jentic

AI agents discover and call Game Management 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 'game management API', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/juegos` | Crear un nuevo juego |
| GET | `/juegos` | Obtener lista de juegos |
| GET | `/juegos/{id_juego}` | Obtener un juego por ID |
| PUT | `/juegos/{id_juego}` | Actualizar un juego por ID |
| DELETE | `/juegos/{id_juego}` | Eliminar un juego por ID |
| GET | `/juegos/recomendados` | Obtener juegos recomendados |
| GET | `/juegos/{id_juego}/descargar` | Descargar juego por ID |
| POST | `/juegos/{id_juego}/ejecutar` | Ejecutar juego por ID |

## Key resources

- **Games** — Operations related to Juegos

## Why Jentic

- **Setup:** Wiring the Game Management API by hand means resolving its SwaggerHub host, shaping the game create, read, update, delete, download, and run calls, and handling retries yourself, even though it takes no auth. Through Jentic you install once, import the Game Management API from the API Directory, and your agent calls it with no credential to store.
- **Permission scoping:** The Game Management API puts the game id in the URL path (`/juegos/{id_juego}`), so a rule can pin your agent to one game. You choose the operations it may call, so a destructive one like deleting a game is not included unless you add it, leaving reads, downloads, and runs.
- **Credential handling:** This API needs no credentials, so there is nothing for the agent to hold. If a call ever required a secret, your own Jentic One instance would store it once, encrypted, and inject it at execution time so it never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list games' or 'download a game by id', and Jentic returns the matching Game Management 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 Game Management API use?

The Game Management 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 Game Management 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 game management API through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use game management API'. Jentic returns the matching Game Management API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Game Management API have?

The Game Management API exposes 8 endpoints covering games operations.

### Does the Game Management 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 Game Management API?

Yes. Because you run Jentic One yourself, your own rules decide which Game Management API operations the agent may call, so you can allow reads, listing recommended games, and downloading or running a game while excluding the destructive delete operation. Since the game id sits in the URL path at `/juegos/{id_juego}`, a rule can also pin the agent to a single game rather than every record. You choose which operations and inputs are in scope, and anything you do not grant stays off limits.