Sportmonks Football API
62
AI ReadinessAI-Aware (B-)62/100
Official vendor OpenAPI document · agent-readyAI/MLMl InferenceapiKey24 EndpointsREST
For Agents
Programmatically get inplay livescores, get all livescores. Covers 24 operations with apiKey authentication.
Use for: I need to inplay livescores, I want to all livescores, Search for all fixtures, Find all fixture by id
Not supported: Does not handle payments, communications, or crm - use for ai and machine learning only.
Comprehensive football data API providing access to fixtures, livescores, standings, teams, players, coaches, referees, odds, predictions, and more. Covers over 2,500 leagues worldwide. Authentication via API token in Authorization header. The API exposes 24 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Sportmonks Football API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sportmonks Football 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.
1
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%2Fsportmonks.com%2Fsportmonks" | sh2
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%2Fsportmonks.com%2Fsportmonks" | 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.
Capabilities
What an agent can do with Sportmonks Football API.
GET Inplay Livescores
Manage ai ml data programmatically
Integrate Sportmonks Football API into automated workflows
Query and filter Sportmonks Football API records by parameters
Monitor Sportmonks Football API operational status and events
Use Cases
Patterns agents use Sportmonks Football API for, with concrete tasks.
★ AI and Machine Learning Operations
Use the Sportmonks Football API to perform ai ml operations programmatically. The API provides 24 endpoints covering core functionality including get inplay livescores, get all livescores, get all fixtures.
Call GET /livescores/inplay to get inplay livescores
Automated Coaches Management
Automate coaches operations by combining multiple Sportmonks Football API endpoints. Agents can get all livescores and then get all fixtures in a single workflow.
Call GET /livescores to get all livescores, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Sportmonks Football 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 apiKey tokens manually.
Search Jentic for 'get inplay livescores', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
24 endpoints — comprehensive football data api providing access to fixtures, livescores, standings, teams, players, coaches, referees, odds, predictions, and more.
METHOD
PATH
DESCRIPTION
GET
/livescores/inplay
GET Inplay Livescores
GET
/livescores
GET All Livescores
GET
/fixtures
GET All Fixtures
GET
/fixtures/{id}
GET Fixture by ID
GET
/fixtures/date/{date}
GET Fixtures by Date
GET
/leagues
GET All Leagues
GET
/leagues/{id}
GET League by ID
GET
/leagues/search/{name}
GET Leagues Search by Name
GET
/livescores/inplay
GET Inplay Livescores
GET
/livescores
GET All Livescores
GET
/fixtures
GET All Fixtures
GET
/fixtures/{id}
GET Fixture by ID
GET
/fixtures/date/{date}
GET Fixtures by Date
GET
/leagues
GET All Leagues
GET
/leagues/{id}
GET League by ID
GET
/leagues/search/{name}
GET Leagues Search by Name
Jentic AI Readiness Score
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.
S
Sportmonks Football API
- AI-Aware (B-)62/100
93
Foundational Compliance63
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability50
Security51
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
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.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
39%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
51
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C-Signals: 1
51%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Sportmonks Football API by hand means provisioning its API key, attaching it to every request, and pointing calls at the api.sportmonks.com/v3/football host yourself. Through Jentic you install once, import the Sportmonks Football API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Sportmonks puts the fixture and league ids in the URL path (/fixtures/{id}, /leagues/{id}), so a rule can pin your agent to reading one fixture or league. The endpoints here are all reads, so you choose which livescore and lookup operations it may call and nothing writes back.
Credential isolation
Your Sportmonks API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get inplay livescores' or 'look up a fixture', and Jentic returns the matching Sportmonks Football API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Sportmonks Football API through Jentic.
What authentication does the Sportmonks Football API use?
The Sportmonks Football API uses an API key passed in the `Authorization` header. 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 inplay livescores with the Sportmonks Football API?
Yes. Use the GET /livescores/inplay endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Sportmonks Football 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 inplay livescores through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get inplay livescores'. Jentic returns the matching Sportmonks Football API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Sportmonks Football API have?
The Sportmonks Football API exposes 24 endpoints covering coaches, fixtures, leagues operations.
Can I limit what my agent is allowed to do with the Sportmonks Football API?
Yes. Because you run Jentic One yourself, your own rules decide which Sportmonks operations and credentials the agent may use. Every endpoint here is read-only, so you can permit just the livescore and lookup calls it needs, such as GET /livescores/inplay or GET /leagues, and nothing can write data back. Since Sportmonks carries fixture and league ids in the URL path, like /fixtures/{id} and /leagues/{id}, you can even pin the agent to reading a single fixture or league.
GET STARTED