The canonical REST surface and HTTP MCP server are live for invited testers. Coverage, source attribution and verification vary by resource; the methodology page states what is measured today.
No paid plan is currently purchasable. Join the waitlist for supported access, or browse the public website while the evidence ledger and historical completeness programme continue.
Free
$0forever
Build something real before you pay.
Indie
$19/ month
Everything we can defensibly serve, one flat price.
Pro
$79/ month
For production apps and research at volume.
Enterprise
Customtalk to us
Custom terms, licensing and support.
Multiple upstream identifiers and datasets map into one Postgres schema. Entity aliases and resolvers reduce duplication, while ongoing QA identifies mistaken merges and contamination that automation misses.
Results, events, lineups, statistics, historical odds and modelled metrics share a queryable shape, while nullable fields preserve honest historical gaps instead of implying uniform depth.
The deployed HTTP MCP endpoint exposes question-shaped tools for agents. Use tools/list for the current surface; tool execution requires an issued beta key.
| Surface | Current status | Important limit |
|---|---|---|
| Public website | Live | Browser access; not a third-party API stability contract |
| REST API | Invite-only closed beta | Public/free preview is current-season for canonical match data; supported historical access needs the project apikey plus an entitled x-api-key |
| HTTP MCP | Discovery live; execution invite-only | Keyed tools use the same database content tier; use tools/list for deployed schemas |
| OpenAPI | Version 3.0.3 specification | Documents the supported canonical surface, not internal tables |
| Bulk export / SLA | Not generally available | Contact us for requirements; no advertised entitlement exists yet |
Not yet. Plans and prices are confirmed — Free $0, Indie $19/mo, Pro $79/mo, Enterprise by arrangement — and self-serve checkout opens shortly. Access is invite-only during closed beta; join the waitlist and we will invite you in order.
The deployed HTTP MCP endpoint lets compatible agents discover structured football tools. Tool execution uses the same issued beta key as REST. Because the surface evolves, tools/list is authoritative for tool names and input schemas.
The erratum log publishes confirmed user-facing corrections and their supporting sources. We are extending this into a database-enforced evidence trail so operational repairs cannot bypass the public record.
Not uniformly complete. The production database has records from 1871, but only a small number of competitions currently reach before 1900. Events, lineups, advanced statistics, evidence and source URLs are much sparser than scores. Ask about measured coverage for your fields and competition.
Freshness varies by source and ingestion job, and there is no general real-time SLA. Use retrieval metadata where present and ask about the specific dataset if freshness is critical.
No. Publisher-aware match and player-season tiers distinguish corroborated, single-source and flagged rows. Corroborated requires two assessed publisher groups; multiple aliases or products from one publisher do not qualify. Tiering does not yet cover every individual field or entity.
curl "$FOOTIO_BASE/players?
name=ilike.*messi*" \
-H "apikey: $FOOTIO_ANON" \
-H "x-api-key: $FOOTIO_KEY"
https://amidfjrgsztslrpeaiec
.supabase.co/functions/v1/mcp
Use tools/list for the current surface.
https://foot.io/openapi-v2.yaml
Canonical beta REST surface,
not internal database tables.