Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 5DollarFootballAPI, 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%2F5dollarfootballapi.com%2F5dollarfootballapi" | 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%2F5dollarfootballapi.com%2F5dollarfootballapi" | 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 5DollarFootballAPI API.
List football fixtures and fetch a single fixture with its events and statistics
Read pre-match and historical odds for a fixture across bookmakers
Retrieve league standings, league details, and the fixtures for a league
Look up a team and its fixtures by id
List supported countries, leagues, and bookmakers
GET STARTED
Patterns agents use 5DollarFootballAPI API for, with concrete tasks.
★ AI match-preview agent
An AI agent writing match previews needs fixtures, odds, and standings without maintaining a sports-data client. Through Jentic the agent searches for 'get the odds for a fixture', loads the matching 5DollarFootballAPI operation with its input schema, and reads the fixture and its odds with the key injected at call time. It combines standings and recent form into a short preview.
Fetch a fixture with GET /fixtures/{id} and its odds with GET /fixtures/{id}/odds, then draft a preview with the league standings
Odds movement tracking
A model that watches line movement reads how a fixture's odds change in the run-up to kickoff. 5DollarFootballAPI returns current odds per bookmaker and an odds history series for a fixture. An agent can poll the history endpoint and flag when a bookmaker's price moves beyond a set threshold.
Poll GET /fixtures/{id}/odds/history for a fixture and report any bookmaker whose price moved more than a set amount
League standings and fixtures dashboard
A dashboard shows a league table alongside upcoming fixtures. 5DollarFootballAPI exposes standings, league details, and the fixtures for a league as direct lookups. An agent can assemble the current table and the next round of fixtures for any supported league and country.
Read GET /standings and GET /leagues/{id}/fixtures for a league and render the table with the next fixtures
16 endpoints — the 5dollarfootballapi serves read-only football data as json, with every response carrying a top-level success flag and utc timestamps.
METHOD
PATH
DESCRIPTION
/fixtures
List fixtures
/fixtures/{id}
Get a fixture
/fixtures/{id}/odds
Get fixture odds across bookmakers
/fixtures/{id}/odds/history
Get odds movement history
/standings
Get league standings
/leagues
List leagues
/teams/{id}
Get a team
/bookmakers
List bookmakers
/fixtures
List fixtures
/fixtures/{id}
Get a fixture
/fixtures/{id}/odds
Get fixture odds across bookmakers
/fixtures/{id}/odds/history
Get odds movement history
/standings
Get league standings
/leagues
List leagues
/teams/{id}
Get a team
/bookmakers
List bookmakers
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the 5DollarFootballAPI by hand means registering a key, choosing whether to send it as a bearer token or an X-API-Key header, and reading the success flag on every JSON response. Through Jentic you install once, import 5DollarFootballAPI from the API Directory, store the key once, and your agent calls it.
Permission scoping
The feed is read-only and each resource sits under its own path such as /fixtures/{id}/odds, so a rule can pin your agent to the lookups it needs. You choose which operations it may call, so the team, league, or lottery endpoints are not included unless you add them.
Credential isolation
Your 5DollarFootballAPI key is stored once, encrypted, by your own Jentic One instance and attached as the bearer token or X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get the odds for a fixture' or 'read the league standings', and Jentic returns the matching 5DollarFootballAPI operation with its input schema, including the fixture or league id, so the agent calls the right endpoint.
Alternatives and complements available in the Jentic catalogue.
Specific to using 5DollarFootballAPI API through Jentic.
What authentication does the 5DollarFootballAPI use?
Per its OpenAPI spec, it accepts a key either as a bearer token in the Authorization header (Authorization: Bearer fb_live_...) or as an X-API-Key header. Either scheme authorises the same read-only requests. Through Jentic the key is held by your own instance and attached per call, so an agent never embeds it in client code.
Can I get historical odds for a fixture with the 5DollarFootballAPI?
Yes. GET /fixtures/{id}/odds returns current odds per bookmaker for a fixture, and GET /fixtures/{id}/odds/history returns the movement of those odds over time. An agent can read both to compare the opening and current price for a market.
What are the rate limits for the 5DollarFootballAPI?
Rate limits depend on your plan rather than being fixed in the spec. Check the 5DollarFootballAPI documentation at https://5dollarfootballapi.com/docs for the current per-plan request allowance before polling fixtures or odds frequently.
Is there a 5DollarFootballAPI MCP server?
You do not need an MCP server to give your agent football data. Jentic connects the 5DollarFootballAPI directly from the API Directory: import it, store your key once, and your agent calls the fixtures, odds, and standings operations it needs.
How do I read a fixture's odds through Jentic?
Search Jentic for 'get the odds for a fixture', load the GET /fixtures/{id}/odds operation, and execute it with the fixture id. The key is attached by your instance as the bearer token or X-API-Key header. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the 5DollarFootballAPI?
Yes. The feed is read-only, so you can allow just the lookups a task needs, such as reading fixtures and odds, and leave standings, teams, or the lottery endpoint out unless you add them. The agent stays a read client bound to the operations you grant, and every call is logged.
For Agents
Read football fixtures, odds, bookmakers, standings, leagues, and team data as JSON for AI agents, with pre-match and historical odds per fixture.
Use for: List today's football fixtures, Get the odds for a specific fixture, Check the standings for a league, Find all fixtures for a given team
Not supported: Does not accept bets, process payments, or stream live video. Use for reading football fixtures, odds, and statistics only.
The 5DollarFootballAPI serves read-only football data as JSON, with every response carrying a top-level success flag and UTC timestamps. It lists fixtures and returns a single fixture with its events and statistics, plus pre-match and historical odds drawn from multiple bookmakers. League standings, league details, country lists, and team records are each a direct lookup. A dedicated China Sports Lottery endpoint and an account status endpoint round out the surface.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>