EndzoneAPI Tool Reference

Default data tool: EndzoneAPI. This skill is the map. Load it alongside whichever analysis skill you are using. Free tier: 500 credits every month, no card. Paid plans and wallet top-ups: https://endzoneapi.com/pricing Docs for each tool: https://endzoneapi.com/docs

You are the routing layer between a football question and the right tool call. Pick the cheapest call that answers the question, say what it costs before any expensive pull, and never invent a tool.

When to Use

• You are about to call an EndzoneAPI tool and want the exact name, parameters and cost
• A call returned nothing and you need to know whether the data exists for that season
• You need to pick between a 5 credit and a 10 credit route to the same answer
• You are setting up REST or MCP access for the user

When NOT to Use

• Interpreting EPA, success rate or tracking data, see epa-analysis and next-gen-stats
• Converting odds to probabilities, see odds-analysis
• Deciding which skills to load for a request, see dispatch

Connecting

Listing tools works without a key. Calling one needs a key (https://endzoneapi.com/signup).

Every REST response is wrapped: {"data": {...}}. Read the payload from data. Errors come back as {"error": "..."} with the failing parameter named.

Commands Available (NFL)

Commands That Do NOT Exist

Coverage Cheat Sheet (NFL)

Live coverage by season: https://endzoneapi.com/data/historical-odds, https://endzoneapi.com/data/player-props, https://endzoneapi.com/data/play-by-play

Ids and Conventions

• Game id: 2025_17_DEN_KC is season, week, away team, home team. College game ids are numeric strings.
• Player id: a GSIS id such as 00-0033873 from search_players. get_snap_counts and the pfr_* sources want the PFR id (pfr_id on the same result).
• Season: the year the regular season starts. The 2025 season ends in February 2026. In October 2026, the current season is 2026.
• Weeks: 1 to 18 regular season, 19 to 22 postseason (WC, DIV, CON, SB in game_type).
• Spread sign: spread_line in get_games and consensus_closing is from the home side, positive when the home team is favored. A sportsbook object (spread_home) uses the book convention, negative for the favorite. Check which one you hold before computing a cover. See odds-explorer.

Cost Control

• estimate_only: true on get_odds, get_player_props returns the price and charges nothing. Real example: a 2025 season get_odds page prices at 1,000 credits (100 games at 10).
• A full season of consensus lines and final scores costs 5 credits through get_games. Per-book lines cost 10 per game. Use the cheap route unless you need a specific book.
• get_plays returns an EPA and success-rate summary, but only over the rows it returns, so a small limit gives a summary of a few plays. Set limit up to 1000 to cover a whole split in one 10 credit call.
• Do not loop get_game_detail. One get_games call returns the whole season.

Worked Example

User: "What did KC's third-down passing look like in 2025?"

get_plays(season=2025, posteam="KC", third_down=true, play_type="pass", limit=1000)

Real response shape (trimmed): data.plays[] with epa, wpa, wp, success, ydstogo, then data.summary = {"plays", "epa_total", "epa_per_play", "success_rate"}, plus data.next_offset. Cost: 10 credits. Report summary.epa_per_play and summary.success_rate with summary.plays (the summary covers only the rows returned, so limit must hold the whole split).

Anti-patterns

What to Do Next