Transparency
Sources, Credits, and Data Rights
The product's data sources, referential assets, and rights posture around public baseball material, team marks, and league information.
ByColby Reichenbach
Overview
AiBS depends on public baseball data and referential visual assets, but it does not claim league ownership or endorsement.
AiBS uses public baseball-facing data sources and transforms them into product views, model layers, and editorial outputs. That includes game, team, umpire, and challenge information as well as the public rules and reporting used to explain MLB's ABS system.
The product also uses referential team marks, colors, and related visual identifiers in service of describing baseball entities that already exist. That does not imply ownership, partnership, or endorsement.
This page exists to make the provenance and posture explicit instead of burying it behind generic footer language.
Data
Public inputs, product-specific transforms.
The underlying baseball information comes from public-facing sources such as MLB and related APIs. AiBS then restructures, stores, and models that data in its own database, views, and runtime loaders. The transformed product outputs are not a copy of a public endpoint. They are the result of the application's own processing, aggregation, and presentation layers.
Marks and references
Names, logos, and colors are used to describe the sport accurately.
Team names, abbreviations, colors, and visual identifiers appear so the product can identify clubs and present baseball information clearly. Those references are used descriptively. They do not transfer ownership, affiliation, or endorsement.
This is the same reason public rule and reporting sources are cited directly on the relevant pages. When the product is explaining MLB's ABS system, the user should be able to inspect the underlying public reporting and league material that informed that explanation.