canonical: https://jentic.com/apis/swaggerhub.lmorenoo/apuestas-api

# Lmorenoo Apuestas API

API para el manejo de apuestas de futbol. The API exposes 6 endpoints.

## For AI agents

Programmatically crear un torneo, busca un torneo. Covers 6 operations.

## Scope

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

## Capabilities

- crear un torneo
- busca un torneo
- Integrate Apuestas API into automated workflows
- Query and filter Apuestas API records by parameters
- Monitor Apuestas API operational status and events

## Use cases

### Developer Tools Operations

Use the Apuestas API to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including crear un torneo, busca un torneo, crear un cotejo.

Example prompt: Call POST `/torneo/{idTorneo}` to crear un torneo

### Automated administradores Management

Automate administradores operations by combining multiple Apuestas API endpoints. Agents can busca un torneo and then crear un cotejo in a single workflow.

Example prompt: Call GET `/torneo/{idTorneo}` to busca un torneo, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Apuestas 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. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'crear un torneo', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/torneo/{idTorneo}` | crear un torneo |
| GET | `/torneo/{idTorneo}` | busca un torneo |
| POST | `/cotejo/{idCotejo}` | crear un cotejo |
| GET | `/cotejo/{idCotejo}` | busca un cotejo |
| POST | `/apuesta/{idApuesta}` | crear una apuesta |
| GET | `/apuesta/{idApuesta}` | busca una apuesta |

## Key resources

- **administradores** — Apostadores para admins
- **apostadores** — Operadores para apostadores
- **invitadores** — Operadores para invitados

## Why Jentic

- **Setup:** Wiring the Apuestas API by hand means mapping its tournament, match, and bet routes, coding each GET and POST, and handling retries yourself. Through Jentic you install once, import the Apuestas API from the API Directory, store any host details once, and your agent calls it.
- **Permission scoping:** This API puts the resource id in the URL path (`/torneo/{idTorneo}`, `/apuesta/{idApuesta}`), so a rule can pin your agent to one tournament, match, or bet: it can read or write that resource and nothing else. You choose the operations it may call, so a create or update path is not included unless you add it.
- **Credential handling:** Any access details for the Apuestas API 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 'create a tournament' or 'read a bet', and Jentic returns the matching Apuestas API 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 Apuestas API use?

The Apuestas API uses no 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 crear un torneo with the Apuestas API?

Yes. Use the POST `/torneo/{idTorneo}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Apuestas 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 crear un torneo through Jentic?

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

### How many endpoints does the Apuestas API have?

The Apuestas API exposes 6 endpoints covering administradores, apostadores, invitadores operations.

### Can I limit what my agent is allowed to do with the Apuestas API?

Yes. Because you run Jentic One yourself, your own rules decide which Apuestas API operations and credentials the agent may use, and you can grant read-only access with GET `/torneo/{idTorneo}`, GET `/cotejo/{idCotejo}`, and GET `/apuesta/{idApuesta}` while withholding the POST create paths. Since the resource id sits in the URL path, a rule can pin the agent to a single tournament, match, or bet so it touches nothing else. A create or update operation is available to the agent only if you explicitly add it.