Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the STATS 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%2Fstats.com%2Fstats" | shStep 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%2Fstats.com%2Fstats" | 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 STATS API.
Get access token
List resources
Integrate STATS API into automated workflows
Query and filter STATS API records by parameters
Monitor STATS API operational status and events
GET STARTED
Patterns agents use STATS API for, with concrete tasks.
★ Developer Tools Operations
Use the STATS API to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including get access token, list resources, get resource.
Call POST /auth/token to get access token
Automated Authentication Management
Automate authentication operations by combining multiple STATS API endpoints. Agents can list resources and then get resource in a single workflow.
Call GET /resources to list resources, then verify the result
AI Agent Integration via Jentic
AI agents discover and call STATS 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 'get access token', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — sports data and statistics.
METHOD
PATH
DESCRIPTION
/auth/token
Get access token
/resources
List resources
/resources/{id}
Get resource
/auth/token
Get access token
/resources
List resources
/resources/{id}
Get resource
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the STATS API by hand means running its token exchange, mapping the resource listing and lookup calls, and handling the response shapes yourself. Through Jentic you install once, import the STATS API from the API Directory, and your agent calls it against the resource operations it needs.
Permission scoping
You limit the agent to the operations it needs, such as listing resources or fetching a resource by id, so it never touches the token exchange or other calls unless you include them. Scope the agent by operation to keep it to those reads.
Credential isolation
The STATS API declares no security scheme, so there is no static secret to store, and nothing ever enters the agent's prompt, logs, or context. Jentic One executes the calls on your behalf from the operation's input schema.
Intent-based discovery
Agents search Jentic by intent such as 'get an access token' or 'list available resources', and Jentic returns the matching STATS API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using STATS API through Jentic.
What authentication does the STATS API use?
The STATS 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 get access token with the STATS API?
Yes. Use the POST /auth/token endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the STATS 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 get access token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get access token'. Jentic returns the matching STATS API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the STATS API have?
The STATS API exposes 3 endpoints covering authentication, resources operations.
Can I limit what my agent is allowed to do with the STATS API?
Yes. Jentic One is self-hosted, so your own rules decide which STATS API operations and credentials the agent may use. You can scope the agent by operation to just the reads it needs, such as GET /resources to list resources or GET /resources/{id} to fetch a single resource by id, so it never touches the POST /auth/token exchange or any other call unless you explicitly include it. Because the agent only ever sees the operations you grant, an operator stays in control of exactly what it can call.
For Agents
Programmatically get access token, list resources. Covers 3 operations.
Use for: I need to access token, I want to resources, Search for resource, List all records from STATS API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Sports data and statistics. The API exposes 3 endpoints.