canonical: https://jentic.com/apis/eliteprospects.com/eliteprospects # Elite Prospects API 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. ## For AI 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. ## Scope Does not handle ticketing, live scoring, or fantasy league management. Use for retrieving ice hockey player, team, game, and draft data only. ## Capabilities - 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 - List award types and the players or staff who won them ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Retrieve a team's games and the arena it plays in, then assemble a season schedule view ## Key endpoints | 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 | ## Key resources - **Players** — Player profiles, statistics, and play styles - **Games and game logs** — Game results plus per-player and aggregated game logs - **Drafts** — Draft types, selections, and per-year rankings - **Teams and arenas** — Team records and the arenas they play in - **Agencies and staff** — Agencies, their player clients, and staff records - **Awards** — Award types and their player and staff winners ## AI readiness 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. - **Score:** 26 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 66 / 100 - Developer Experience & Jentic Compatibility: 56 / 100 - AI-Readiness & Agent Experience: 22 / 100 - Agent Usability: 68 / 100 - Security: 15 / 100 - AI Discoverability: 9 / 100 - **View full report:** https://jentic.com/apis/eliteprospects.com/eliteprospects/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **NHL API** — The NHL's own API covers official league stats and schedules, where Elite Prospects spans leagues worldwide and junior hockey. - **SportsData.io API** — Multi-sport data and odds that complement Elite Prospects when an agent needs sports beyond hockey. - **API-Sports** — Live fixtures and standings across many sports, pairing with Elite Prospects' deep hockey records. ## FAQ ### 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.