College Football Data
DATA · DATA & ANALYTICS
Games, drives, play-by-play, rankings, and recruiting, read-only.
Connecting College Football Data in practice
Access is metered per month rather than per second and billed through Patreon, so the free key is 1,000 calls for a whole month and live play-by-play does not appear until the $5 Tier 2. An agent that polls a game in progress spends a free key in one afternoon and then gets an entitlement response, not a rate-limit one.
Rate limits
- Free key: 1,000 API calls per month.
- Academic tier: 3,000 calls per month, and registration requires a .edu email address.
- Tier 1 ($1/month): 5,000 calls per month, adds live scoreboard.
- Tier 2 ($5/month): 30,000 calls per month, adds live play-by-play.
- Tier 3 ($10/month): 75,000 calls per month, adds the GraphQL API.
- Tier 4 ($15/month): 125,000 calls per month.
- No per-second figure is published anywhere; the tiers are monthly call counts only.
Worth knowing
- The key goes in an Authorization: Bearer header, and the docs point out that a missing space after "Bearer" is a common cause of 401.
- Requests sent from the documentation playground count toward usage exactly like requests from any other client, so exploring the reference spends the same quota the agent needs.
- Features are tier-gated rather than scope-gated: the same endpoint that answers on a Tier 3 key returns a quota or entitlement response on a free one, which is a different failure from a 404.
- The legacy Swagger UI is still online during the transition to the new reference, so two documentation surfaces describe the same base URL at once.
Checked against CFBD getting started (2026-09-29), CFBD authentication (2026-09-29), CFBD usage and access (2026-09-29), CFBD API access tiers (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put College Football Data behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.