statshawk

// company

About statshawk

statshawk is a sports data platform built by EdgeHawk, LLC. It delivers one normalized data layer across 50+ competitions in 16 sports, with the deepest coverage for the majors: NBA, MLB, NFL, NHL, and NCAA scores, box scores, rosters, game logs, standings, player props, and pregame matchup analysis. All of it comes through two surfaces: a REST API for products and a Model Context Protocol (MCP) server for AI assistants and coding agents.

What we do

Sports data is scattered across league sites, broadcasters, and scraped HTML, and every league shapes it differently. statshawk ingests those sources, reconciles them into one schema, and serves the result with predictable identifiers, documented freshness tiers, and a stable /v1 contract. The same account and the same data power both the REST API at api.statshawk.ai and the MCP server at mcp.statshawk.ai.

The MCP server exists because large language models are confidently wrong about last night's box score. Connecting Claude, ChatGPT, Cursor, or any MCP-capable assistant to statshawk replaces guesses with tool calls that return real, current numbers.

Who we are

EdgeHawk, LLC is a small, product-focused team of engineers who have built data pipelines and developer tools for sports, finance, and AI products. We run statshawk as a hosted service: we operate the ingestion, the API, the MCP server, and the billing, so you can integrate in an afternoon and stay integrated.

We publish our documentation, OpenAPI description, agent onboarding skills, and changelog openly at statshawk.ai/docs and /llms.txt.

How we operate

  • Versioned, documented API. Every endpoint lives under /v1. Breaking changes normally ship as a new major version with a published deprecation window; documented exceptions (including the 2026-09-11 quota hard-stop under /v1) are announced in the changelog. See the versioning policy.
  • Transparent pricing. A free tier with no card required, usage-based paid plans, and published rate limits and quotas: see pricing.
  • Privacy by default. API keys are stored hashed, MCP credentials are encrypted at rest, and we never sell usage data: see the privacy policy.
  • Humans answer email. Reach the team through the contact page.