For Agents
Programmatically crear un torneo, busca un torneo. Covers 6 operations.
Use for: I need to crear un torneo, I want to busca un torneo, Search for crear un cotejo, Find all busca un cotejo
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Apuestas 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Apuestas API API.
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
GET STARTED
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Jentic publishes the only available OpenAPI document for Apuestas API, keeping it validated and agent-ready.
API para el manejo de apuestas de futbol. The API exposes 6 endpoints.
Patterns agents use Apuestas API API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'crear un torneo', load the operation schema, and execute with Jentic-managed credentials
6 endpoints — api para el manejo de apuestas de futbol.
METHOD
PATH
DESCRIPTION
/torneo/{idTorneo}
crear un torneo
/torneo/{idTorneo}
busca un torneo
/cotejo/{idCotejo}
crear un cotejo
/cotejo/{idCotejo}
busca un cotejo
/apuesta/{idApuesta}
crear una apuesta
/apuesta/{idApuesta}
busca una apuesta
/torneo/{idTorneo}
crear un torneo
/torneo/{idTorneo}
busca un torneo
/cotejo/{idCotejo}
crear un cotejo
/cotejo/{idCotejo}
busca un cotejo
/apuesta/{idApuesta}
crear una apuesta
Three things that make agents converge on Jentic-routed access.
Credential isolation
Apuestas API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'crear un torneo') and Jentic returns the matching Apuestas API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Apuestas API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Gitlab
Alternative developer tools API
Choose Gitlab when you need a different approach to developer tools operations
Specific to using Apuestas API API through Jentic.
What authentication does the Apuestas API use?
The Apuestas API uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
/apuesta/{idApuesta}
busca una apuesta