Install Jentic One Beta

Connect the Apuestas API to your agent

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.lmorenoo%2Fapuestas-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.lmorenoo%2Fapuestas-api" | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with Apuestas 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

Start building with Apuestas API

Explore with Jentic One

View OpenAPI Document

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

Key Endpoints

6 endpoints — api para el manejo de apuestas de futbol.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Apuestas API through Jentic.

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.

Lmorenoo Apuestas API

Browse all Swaggerhub Lmorenoo APIs

AI ReadinessAI-Aware (A-)72/100

See full scorecard

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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

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

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

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

31%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

56%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

67%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Apuestas API to your agent

Capabilities

Start building with Apuestas API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Lmorenoo Apuestas API

Jentic AI Readiness Score

Apuestas API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness