Inside the Zafronix APIs family

The gap between Wikipedia (HTML, scrape–only, no contract) and Sportradar / Opta (enterprise sales, $10K+/month, twelve–page DPA) is enormous. Most builders, journalists, data analysts, and consumer apps live in that gap. The Zafronix APIs family fills it — with structured, queryable, AI-enriched sports data anyone can ship against. Starting with football. Same auth, same shape, same predictable pricing across the family.

Why “family” matters

We could have shipped four standalone APIs. We deliberately didn’t. A family has a different commitment to the developer:

• One auth. One key gets you all four. Add your fifth tournament and the integration is twenty minutes, not a procurement cycle.
• One shape. The Brazil vs. Sweden 1958 record looks structurally identical to the Spain vs. Netherlands 2010 record — same field names, same nullability rules, same date format, same conventions for “tournament not yet started”.
• One bill. Cross-tournament rate limit, one invoice line. You don’t pay separately for Euro and World Cup, because to your code base they’re the same thing.
• One docs surface. Read the WC API docs once. The Euro API docs are diff–sized, not full–sized.

What we mean by AI-enriched

Most sports APIs give you rows. We also give you sentences.

Every match, tournament, player, and team carries an ai_note field with a one-sentence storyline — generated, fact-checked against the underlying record, and human-reviewed for the high-traffic surfaces. So when your app shows the Pelé 1958 debut, you don’t have to source “first teenage hat–trick in a WC semifinal” from somewhere else. It’s in the response.

This is exactly the layer most developers either fake (hardcoded copy) or punt (just numbers). It’s the difference between “87% possession” and “Spain’s 87% possession was their highest of the tournament — and the second-highest by any team in any final since 1990.” The numbers are the same. The product feel isn’t.

The honest part: a 5-minute live lag

We wrote a whole post about this, so we’ll keep it short: during live matches, Zafronix APIs run on a deliberate ~5-minute lag. We don’t pretend to be Sportradar. If you need second–by–second betting–grade feeds, we’re not the right fit and we’ll tell you that upfront.

What we are right for: history apps, fantasy products, education tools, content surfaces, dashboards, journalism, and consumer apps where “a few minutes behind broadcast” is fine and predictable matters more than fastest.

Where it shows up today

Internally, the WC API powers siono.app/worldcup-history — the consumer surface where you can settle “who won the Golden Boot in 1958” from your group chat in two taps. That’s the same data, served the same way, with the same SLA. We’re an internal customer of our own API. If it breaks for you, it broke for us first.

Why we’re rolling the rest out slowly

The WC API has paying subscribers. World Cup 2026 is on the horizon and traffic is climbing. We are not going to break that surface by hot-swapping the underlying schema to be more “family-shaped”. The way it’ll work:

1. WWC, Euro, and UCL APIs ship on the family-shape from day one.
2. The WC API stays exactly as it is for current subscribers, on its current schema, until the new shape is battle-tested elsewhere.
3. A versioned migration path opens up. Current subscribers don’t move until they want to. Their pricing stays.

This is the same instinct we apply to QORA (don’t replace the cameras) and VenueFuze (don’t force a payment processor change). Operations-grade software respects what’s already running.

Where it goes

Football is the wedge. The same family pattern works for any sport with a long competitive history and uneven public data — basketball, cricket, rugby, F1, the Olympics. Beyond sports, the same approach works for any vertical where the gap between “free, unstructured” and “enterprise contract” is wide. We have ideas. Talk to us if you have one.

api.zafronix.com is live with the free tier and paid plans. Docs at /docs. Enterprise inquiries: contact form.