Install Jentic One Beta

Connect the KickoffAPI — Football Data API (v1, legacy) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the KickoffAPI — Football Data API (v1, legacy), 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%2Fkickoffapi.com%2Fkickoffapi" | 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%2Fkickoffapi.com%2Fkickoffapi" | 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 KickoffAPI — Football Data API (v1, legacy) API.

List fixtures by date, league, season, team, round, status, or venue, or only live matches, with an optional timezone

Read a fixture's events, lineups, team statistics, and player statistics by fixture id

Compare two teams' past and upcoming meetings with the head-to-head endpoint

Get league standings for a season, plus top scorers, top assists, and top yellow and red cards

GET STARTED

Start building with KickoffAPI — Football Data API (v1, legacy) API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use KickoffAPI — Football Data API (v1, legacy) API for, with concrete tasks.

★ Match-Day Assistant Through Jentic

An AI agent answering football questions lists live fixtures, reads the events and lineups for the match the user cares about, and pulls the league standings for context. Through Jentic the agent finds each KickoffAPI operation by intent and calls it with your x-api-key, which stays on your own machine, and the read-only surface means it can only fetch data.

List fixtures with the live filter, pick the match for a given team, then read GET /fixtures/{id}/events and GET /fixtures/{id}/lineups and summarise the match so far

Pre-Match Preview

A content writer or fantasy player wants a preview before kickoff. The agent pulls the head-to-head record, injuries and sidelined players for both sides, the fixture prediction, and each team's season statistics, then assembles a short preview.

For an upcoming fixture, call GET /fixtures/headtohead with the two team ids in h2h, GET /injuries for the fixture, and GET /predictions with the fixture id, then write a preview

League Tables and Leaderboards

A sports site keeps tables and leaderboards current. The agent reads standings for a league and season, then top scorers, top assists, and top yellow and red cards for the same league and season, which are the required parameters on each leaderboard endpoint.

Get standings for a league id and season 2025, then top scorers and top assists for the same league and season, and return the top five of each

Odds Monitoring

A betting analyst tracks prices. The agent lists bookmakers and bet types, reads pre-match odds for a fixture filtered by bookmaker and bet, and polls in-play odds for live matches, reading the X-RateLimit-Remaining header to stay within the plan.

List bookmakers and bets, get odds for a fixture with one bookmaker and bet id, then read GET /odds/live for that fixture

Key Endpoints

43 endpoints — the kickoffapi v1 api returns football (soccer) data as json: live scores, fixtures and results, lineups, match events, team and player statistics, head-to-head records, standings, injuries, transfers, predictions, and pre-match and in-play odds across 1,245 leagues in 171 countries.

METHOD

PATH

DESCRIPTION

GET

/fixtures

List fixtures and live scores

GET

/fixtures/{id}/events

Get a fixture's events

GET

/fixtures/{id}/lineups

Get a fixture's lineups

GET

/fixtures/headtohead

Get head-to-head fixtures

GET

/standings

Get league standings

GET

/players/topscorers

Get top scorers

GET

/odds/live

Get in-play odds

GET

/account/status

Get usage against plan ceilings

GET

/fixtures

List fixtures and live scores

GET

/fixtures/{id}/events

Get a fixture's events

GET

/fixtures/{id}/lineups

Get a fixture's lineups

GET

/fixtures/headtohead

Get head-to-head fixtures

GET

/standings

Get league standings

GET

/players/topscorers

Get top scorers

GET

/odds/live

Get in-play odds

GET

/account/status

Get usage against plan ceilings

Why Jentic?

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

Setup

Wiring KickoffAPI by hand means sending the x-api-key header, choosing between flat and nested response shapes, and pacing calls against its rate limit headers and Retry-After on 429. Through Jentic you install once, import KickoffAPI from the API Directory, store the key once, and your agent calls it.

Permission scoping

KickoffAPI puts the fixture id in the URL path for events, lineups, and statistics (/fixtures/{id}/events), so a rule can pin your agent to one match, while the list endpoints take league, team, and season as query parameters and are bounded by operation. You choose the operations it may call, so endpoints like the odds feeds are not included unless you add them.

Credential isolation

Your KickoffAPI 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 'live football scores' or 'Premier League standings', and Jentic returns the matching KickoffAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using KickoffAPI — Football Data API (v1, legacy) API through Jentic.

What authentication does the KickoffAPI v1 API use?

Per its OpenAPI spec, KickoffAPI v1 authenticates with an API key sent in the x-api-key header on every request. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.

Is there a KickoffAPI MCP server?

You don't need an MCP server to give your agent KickoffAPI. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it, discovering fixture, standings, and odds operations on demand instead of loading a server's tool definitions into its context.

Can I limit what my agent is allowed to do with the KickoffAPI v1 API?

Yes. Every operation is a read, but each one spends your plan's allowance, so write a rule that allows only the fixtures, standings, and per-fixture events operations for a scores agent and leave the odds and player endpoints out. Every call it makes is logged, so you can see what used the quota.

What are the rate limits for the KickoffAPI v1 API?

Per the KickoffAPI spec, plans are Free 100/day (30/min), Starter 7,500/day (120/min), Pro 75,000/day (300/min), and Ultra 250,000/day (600/min), with Enterprise on request. Responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset per minute plus daily equivalents, and a 429 carries Retry-After in seconds.

Is KickoffAPI v1 still supported?

v1 is legacy and frozen, and stays live until its sunset on 01 January 2027. KickoffAPI recommends v2 for new integrations, which uses its own string identifiers and a data and meta envelope.

Can KickoffAPI return the nested fixture format?

Yes. Responses are flat by default, and GET /leagues, GET /fixtures, and GET /fixtures/headtohead return the nested fixture, league, teams, goals, and score shape when you pass format=nested. Use format=flat to force the flat row back.

How do I get live football scores with KickoffAPI through Jentic?

Search Jentic for an intent like 'get live football scores', import the KickoffAPI v1 API from the API Directory, and store your API key. Your agent calls GET /fixtures with the live filter, then GET /fixtures/{id}/events for goals and cards in a match. To run it on your own infrastructure, install Jentic One from its GitHub repo.

KickoffAPI — Football Data API (v1, legacy)

AI ReadinessFoundational (D-)42/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsBusiness IntelligenceapiKey43 EndpointsREST

For Agents

Get live football scores, fixtures, lineups, match events, standings, player and team statistics, injuries, transfers, predictions, and odds across 1,245 leagues. Legacy v1, live until 01 January 2027.

Use for: Show me the live football scores right now, Get the Premier League standings for this season, Who are the top scorers in La Liga this season, Find the lineups for tonight's match

Not supported: Does not place bets, stream video, or cover sports other than football. Use for reading football fixtures, statistics, standings, and odds data only.

The KickoffAPI v1 API returns football (soccer) data as JSON: live scores, fixtures and results, lineups, match events, team and player statistics, head-to-head records, standings, injuries, transfers, predictions, and pre-match and in-play odds across 1,245 leagues in 171 countries. Fixtures can be filtered by date, league, season, team, round, status, and venue, or limited to live matches, and per-fixture events, lineups, statistics, and player stats are addressable by fixture id in the path. Responses come flat by default, with a nested fixture, league, teams, goals, and score shape available through format=nested on leagues, fixtures, and head-to-head. This v1 surface is legacy and frozen until its sunset on 01 January 2027; new integrations should use v2.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

96%

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.

Developer Experience & Jentic Compatibility

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

Grade: B-Signals: 4

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: DSignals: 4

28%

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.

50%

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.

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1

10%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the KickoffAPI — Football Data API (v1, legacy) to your agent

Capabilities

Start building with KickoffAPI — Football Data API (v1, legacy) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

KickoffAPI — Football Data API (v1, legacy)

Jentic AI Readiness Score

KickoffAPI — Football Data API (v1, legacy)

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