Install Jentic One Beta

Connect the Elite Prospects API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Elite Prospects 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%2Feliteprospects.com%2Feliteprospects" | 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%2Feliteprospects.com%2Feliteprospects" | 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 Elite Prospects API.

Retrieve player, team, and game records from the hockey database

Pull game logs and aggregated game-log statistics for a player or team

Look up draft selections and draft rankings by draft type and year

Browse agencies and the players they represent

Retrieve arena details and the teams based there

GET STARTED

Start building with Elite Prospects API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Elite Prospects API for, with concrete tasks.

★ Agent-Driven Hockey Data Lookup

An AI agent connected through Jentic answers hockey questions by querying player profiles, game results, and game logs directly. Because the Elite Prospects surface is organised by resource, the agent fetches a player, then that player's game logs, then the teams and leagues involved, resolving a multi-part question into a sequence of read calls.

Look up a player, retrieve their game logs for the current season, and summarise goals and assists

Scouting and Player Research

Scouts and analysts pull draft selections, draft rankings by year, and player statistics to build prospect reports. The API exposes draft types, per-year rankings, and the scouts behind them, so an agent assembles a ranked prospect list for a given draft without scraping league pages.

Retrieve the draft rankings for a given draft type and year and return the top-ranked prospects

Team and League Record Browsing

A sports data product browses teams, their arenas, and the games they played to populate team pages. The Elite Prospects API returns arena details with the teams based there and game records per team, letting an agent build a team's schedule and venue view from structured records.

Retrieve a team's games and the arena it plays in, then assemble a season schedule view

Key Endpoints

145 endpoints — the elite prospects api serves ice hockey data covering players, teams, games, leagues, drafts, and awards drawn from the elite prospects database.

METHOD

PATH

DESCRIPTION

GET

/games

List games

GET

/games/{id}

Retrieve a game

GET

/game-logs

List game logs

GET

/draft-selections

List draft selections

GET

/agencies

List agencies

GET

/arenas

List arenas

GET

/countries

List countries

GET

/award-types

List award types

GET

/games

List games

GET

/games/{id}

Retrieve a game

GET

/game-logs

List game logs

GET

/draft-selections

List draft selections

GET

/agencies

List agencies

GET

/arenas

List arenas

GET

/countries

List countries

GET

/award-types

List award types

Why Jentic?

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

Setup

Wiring Elite Prospects by hand means managing the `apiKey` query parameter and learning how 145 read operations are grouped across players, games, drafts, and awards. Through Jentic you install once, import the API from the API Directory, store the key once, and your agent calls the operations it needs.

Permission scoping

Every Elite Prospects operation is read-only, so you choose which resources your agent may query, such as players and game logs, and leave the rest unavailable. There are no write or delete operations to expose, and a rule keeps the agent to the data you intend.

Credential isolation

Your Elite Prospects API key is held by your own Jentic One instance, encrypted, and injected into the query string at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get a player's season stats' or 'list draft selections', and Jentic returns the matching Elite Prospects operation with its input schema so the agent queries the right resource without walking the full endpoint list.

FAQs

Specific to using Elite Prospects API through Jentic.

What authentication does the Elite Prospects API use?

The Elite Prospects API authenticates with an API key passed as the `apiKey` query parameter, per its OpenAPI spec. Through Jentic the key is held by your own Jentic One instance and attached to each request at execution time, so it never appears in your agent's prompt or logs.

Can I get player statistics and game logs with the Elite Prospects API?

Yes. The API returns player profiles and statistics, game results, and both per-player and aggregated game logs, along with leagues, drafts, and awards. Your agent can read a player, then that player's game logs, to assemble season totals.

What are the rate limits for the Elite Prospects API?

The OpenAPI spec does not specify rate limits. Check with Elite Prospects API support or see https://www.eliteprospects.com for the current limits before running high-volume queries.

Is there an Elite Prospects MCP server?

You do not need an MCP server to give your agent the Elite Prospects API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent discovers the read operations it needs on demand without loading an extra server's tool definitions into its context.

Can I limit what my agent is allowed to do with the Elite Prospects API?

Yes. Every operation here is a read, so you write a rule that allows only the resources your agent needs, such as players and game logs, and leave the rest of the 145-operation surface unavailable. Every call it makes is logged.

How do I query hockey data through Jentic?

Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the Elite Prospects API from the Jentic directory and search by intent such as 'get a hockey player's game logs'. Jentic returns the matching operation with its input schema so your agent builds a valid query. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Elite Prospects API

AI ReadinessNon-Ready (F)26/100

See full scorecard

Community OpenAPI document · agent-readyAnalyticsBusiness IntelligenceapiKey145 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Query ice hockey data: player profiles and stats, team and game records, game logs, draft selections and rankings, awards, agencies, and arenas from the Elite Prospects database.

Use for: Find all games played by a given hockey team, Get the season statistics for a hockey player, Retrieve the draft selections for a specific draft year, Look up which players a given agency represents

Not supported: Does not handle ticketing, live scoring, or fantasy league management. Use for retrieving ice hockey player, team, game, and draft data only.

The Elite Prospects API serves ice hockey data covering players, teams, games, leagues, drafts, and awards drawn from the Elite Prospects database. Your agent reads player profiles and statistics, game results and game logs, draft selections and rankings by year, and the agencies, arenas, and staff tied to them. Every operation is a read, so the surface is a structured query layer over a deep hockey record set rather than a system that writes back.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

65%

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

100%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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

39%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

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: B+Signals: 1

68%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

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

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Elite Prospects API to your agent

Capabilities

Start building with Elite Prospects API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Elite Prospects API

Jentic AI Readiness Score

Elite Prospects 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