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

# Dacardona1 Betting API

A betting and tournament management API. The API exposes 6 endpoints.

## For AI agents

Programmatically access Betting API resources. Covers 6 operations.

## Scope

Does not handle payments, communications, or crm - use for betting and tournament management only.

## Capabilities

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

## Use cases

### Betting Operations

Use the Betting API to perform betting operations programmatically. The API provides 6 endpoints covering core functionality including adding a new tournament, searching tournaments, adding a new match.

Example prompt: Execute a primary operation against the Betting API

### Automated Betting Workflows

Automate betting operations by combining multiple Betting API endpoints. Agents can search a tournament and then add a new match in a single workflow.

Example prompt: Search for a tournament and then add a match via the Betting API

### AI Agent Integration via Jentic

AI agents discover and call Betting API endpoints through Jentic without managing credentials directly.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/torneo/{idTorneo}` | Add a new tournament |
| GET | `/torneo/{idTorneo}` | Search for a tournament |
| POST | `/cotejo/{idCotejo}` | Add a new match |
| GET | `/cotejo/{idCotejo}` | Search for a match |
| POST | `/apuesta/{idApuesta}` | Place a new bet |
| GET | `/apuesta/{idApuesta}` | Search for a bet |

## Key resources

- **Administrators** — Operations related to administrators
- **Bettors** — Operations related to bettors
- **Guests** — Operations related to guests

## Why Jentic

- **Setup:** Wiring the Betting API by hand means resolving its SwaggerHub host, shaping the tournament, match, and bet calls, and handling retries yourself, even though it takes no auth. Through Jentic you install once, import the Betting API from the API Directory, and your agent calls it with no credential to store.
- **Permission scoping:** The Betting API puts the resource id in the URL path (`/torneo/{idTorneo}`, `/cotejo/{idCotejo}`, `/apuesta/{idApuesta}`), so a rule can pin your agent to one tournament, match, or bet. You choose the operations it may call, so creating or updating a bet is not included unless you add it, leaving a read-only view of a tournament.
- **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 'read a tournament' or 'place a bet', and Jentic returns the matching Betting 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 Betting API use?

The Betting 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 Betting 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 betting API through Jentic?

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

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

The Betting API exposes 6 endpoints covering tournaments, matches, and bets operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which of the Betting API's operations the agent may call, so you can grant read access to tournaments, matches, and bets while withholding the create operations that add a tournament, add a match, or place a bet. Since each resource id sits in the URL path (`/torneo/{idTorneo}`, `/cotejo/{idCotejo}`, `/apuesta/{idApuesta}`), a rule can pin the agent to a single tournament, match, or bet. This API needs no credentials, so scoping is entirely a matter of the operations you choose to expose.