Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationbasic, bearer194 EndpointsREST
For Agents
Retrieve official MLB schedules, standings, team rosters, player and team stats, leaders, venues, and analytics such as spray charts and outs above average.
Use for: I need to get the MLB schedule for a specific date, Get the current standings for a league, List all players for a sport level, Retrieve a team's roster and coaches
Not supported: Does not handle ticketing, streaming video, or fantasy league management. Use for official MLB schedules, standings, and statistics only.
The MLB Stats API serves official Major League Baseball data: team rosters, player and team statistics, game schedules, live standings, venues, transactions, and seasons. It exposes stat search and leader queries, grouped and metric stats, and analytics such as spray charts, outs above average, and stolen-base probability, plus venue weather and uniform details. Agents can assemble schedules, box-score context, and historical records from a single read-oriented data surface.
Install Jentic One Beta
Connect the MLB Stats API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MLB Stats 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%2Fmlb.com%2Fmlb" | 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%2Fmlb.com%2Fmlb" | 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 MLB Stats API.
Retrieve game schedules by date, season, or schedule type
Read live and historical standings for a league
List a team's roster, coaches, and stat leaders
Query player and team statistics, including grouped and metric stats
Run stat search and leader queries across seasons
Pull analytics such as spray charts, outs above average, and stolen-base probability
Use Cases
Patterns agents use MLB Stats API for, with concrete tasks.
★ AI agent baseball data access via Jentic
An AI agent connected through Jentic answers baseball questions without browsing the MLB Stats API reference. It searches by intent such as getting a schedule or standings, Jentic returns the matching operation with its input schema, and the agent reads schedules, rosters, and leaders to build a response. The developer's own Jentic One instance supplies any configured credential at call time.
Call GET /api/v1/schedule for today's games, then GET /api/v1/standings/{standingsType} to add the current standings
Live scoreboard and schedule feeds
Sports apps and bots show today's games and results. The schedule operations return games by date, season, or schedule type, including postseason and tied-game schedules, so an agent can render a scoreboard and link each game to its venue and status.
Call GET /api/v1/schedule/postseason to list postseason games and GET /api/v1/venues/{venueId} for venue detail
Roster and player research
Fantasy and analytics tools need current rosters and player stats. The API lists a team's roster, coaches, and personnel, returns players for a sport level, and serves player and team statistics, letting an agent compile a player profile with season and historical numbers.
Call GET /api/v1/teams/{teamId}/roster for a team, then GET /api/v1/teams/{teamId}/leaders to add its stat leaders
Advanced stats and analytics
Analysts want tracking-derived metrics, not just box scores. The analytics operations return spray charts, outs above average, and stolen-base probability, and the stats search surface supports grouped and metric queries, so an agent can pull Statcast-style context for a batter or situation.
Call GET /api/v1/stats/analytics/sprayChart for the current batter and GET /api/v1/stats/leaders for a chosen statistic
Key Endpoints
194 endpoints — the mlb stats api serves official major league baseball data: team rosters, player and team statistics, game schedules, live standings, venues, transactions, and seasons.
METHOD
PATH
DESCRIPTION
GET
/api/v1/schedule
View schedule by schedule type
GET
/api/v1/standings/{standingsType}
View standings for a league
GET
/api/v1/teams/{teamId}/roster
View a team's roster
GET
/api/v1/teams/{teamId}/leaders
View team stat leaders
GET
/api/v1/stats/leaders
Get leaders for a statistic
GET
/api/v1/stats/analytics/sprayChart
Get the spray chart for the current batter
GET
/api/v1/venues/{venueId}
View venue info
GET
/api/v1/sports/{sportId}/players
Get all players for a sport level
GET
/api/v1/schedule
View schedule by schedule type
GET
/api/v1/standings/{standingsType}
View standings for a league
GET
/api/v1/teams/{teamId}/roster
View a team's roster
GET
/api/v1/teams/{teamId}/leaders
View team stat leaders
GET
/api/v1/stats/leaders
Get leaders for a statistic
GET
/api/v1/stats/analytics/sprayChart
Get the spray chart for the current batter
GET
/api/v1/venues/{venueId}
View venue info
GET
/api/v1/sports/{sportId}/players
Get all players for a sport level
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
Stats API Documentation
- Foundational (D-)42/100
44
Foundational Compliance56
Developer Experience & Jentic Compatibility33
AI-Readiness & Agent Experience41
Agent Usability43
Security45
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
44
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
77%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
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.
33
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
16%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
65%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
41
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
41%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
43
Security
Trust, risk posture, and security compliance.
Grade: D-Signals: 1
42%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
45
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: DSignals: 1
45%
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 MLB Stats API by hand means working across nearly two hundred read operations, picking the right schedule, stats, and standings paths, and handling the two declared HTTP schemes. Through Jentic you install once, import the MLB Stats API from the API Directory, and your agent calls the operations it needs.
Permission scoping
The MLB Stats API is a read-oriented data surface, and you choose which operations the agent may call. A rule can keep it to the schedule, standings, roster, and stats reads, so the few state-changing operations such as updating alumni or clearing status types are not reachable unless you add them.
Credential isolation
Any MLB Stats API credential you configure 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 the MLB schedule' or 'read league standings', and Jentic returns the matching MLB Stats 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 MLB Stats API through Jentic.
What authentication does the MLB Stats API use?
The MLB Stats API declares two HTTP schemes in its OpenAPI spec, basic and bearer, as alternatives on its operations. When a request does carry a credential, Jentic stores it encrypted in your own Jentic One instance and injects it at execution time, so it never enters the agent's prompt or logs.
Can I get game schedules with the MLB Stats API?
Yes. The schedule operations return games by date, season, and schedule type, including postseason, tied-game, and tracking-event schedules. An agent can read the schedule and then link each game to its venue, status, and standings context.
What are the rate limits for the MLB Stats API?
The OpenAPI spec does not specify numeric rate limits. Check the MLB Stats API documentation at https://docs.statsapi.mlb.com for current usage guidance before running high-frequency schedule or stats polling.
How do I get standings through Jentic?
Search Jentic by intent such as getting league standings, and it returns the MLB Stats standings operation with its input schema. Pass the standings type, read the response, and combine it with a schedule call for a full scoreboard. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the MLB Stats API?
Yes. The surface is read-oriented, and you choose which operations the agent may call, so a rule can allow only the schedule, standings, and stats reads it needs and exclude the few state-changing operations such as updating alumni or clearing status types. Every call it makes is logged by your self-hosted instance.
Is there an MLB Stats API MCP server?
You do not need an MCP server to give your agent the MLB Stats API. Jentic connects it directly from the API Directory: import it, and your agent calls the schedule, standings, and stats operations on demand without loading another server's tool definitions into its context.
GET STARTED