Sleeper
Sleeper is a fantasy sports platform — a mobile-first app for creating and managing fantasy football, basketball, and other sports leagues with chat, drafts, waivers, and real-time scoring built in. Sleeper publishes a free, read-only HTTP API at api.sleeper.app that exposes public fantasy data: users, leagues, rosters, matchups, transactions, drafts, draft picks, traded picks, trending players, and the current sport/season state. The API requires no API token or OAuth because no content can be modified through it; every endpoint is a GET request returning JSON, and callers are asked to stay under 1,000 requests per minute to avoid IP blocks. Sleeper is backed by a16z and General Catalyst.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Sleeper the way a machine reads it — 11 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Sleeper scores 41.3/100 (thin), with a separate agent-readiness read of 55/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Sleeper
Each block below is one kind of artifact we hold for Sleeper. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Sleeper Drafts API
The Drafts API from Sleeper — 6 operation(s) for drafts.
Sleeper Leagues API
The Leagues API from Sleeper — 4 operation(s) for leagues.
Sleeper Matchups API
The Matchups API from Sleeper — 1 operation(s) for matchups.
Sleeper Players API
The Players API from Sleeper — 2 operation(s) for players.
Sleeper Playoffs API
The Playoffs API from Sleeper — 2 operation(s) for playoffs.
Sleeper State API
The State API from Sleeper — 1 operation(s) for state.
Sleeper Transactions API
The Transactions API from Sleeper — 1 operation(s) for transactions.
Sleeper Users API
The Users API from Sleeper — 1 operation(s) for users.
Scroll within the panel for all 8 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
sleeper-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Sleeper — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sleeper · machine-readable index on apis.io