A fact checked against an official club, league or governing-body announcement. A direct source link and check date should be shown.
Trust & transparency
Data Sources & Methodology
Tavalyze is currently an MVP. This page explains what is verified, what comes from another provider and what exists only to demonstrate the future product.
An estimate published by a named third-party data provider. Market value is an opinion, not the same as a transfer fee.
Temporary information used to build and test the product. It must not be presented as current or authoritative.
A Tavalyze output calculated from documented inputs and assumptions. It is a scenario—not a confirmed future event.
What the current MVP does
- Player and team facts: mostly a manually entered demo dataset. Profiles without source links should be treated as unverified.
- Market values: manually entered estimates. A sourced value shows the provider and date; it is never the same thing as a confirmed transfer fee.
- Value forecasts: a simple age-based demo model with base, upside and downside scenarios.
- Club Fit: a prototype score using position, age, estimated value and manually defined club profiles. It does not use live rumors or verified squad needs.
Path to real predictions
- 1. Connect licensed football and contract data.
- 2. Store source, timestamp and confidence per field.
- 3. Train and back-test models on historical transfers.
- 4. Publish accuracy and calibration results.
Real-data connection
API-Football adapter ready
Tavalyze now has a server-only connection layer for player profiles, statistics, squads and transfers. The secret key is never sent to the browser.
- 1. Create a free API-Football account.
- 2. Copy
.env.exampleto.env.local. - 3. Add the key as
API_FOOTBALL_KEYand restart the development server. - 4. Open
/api/football/statusto verify the connection.
Test the live connection
Search the API-Football player database. These profile facts come from the connected provider; market values still use Tavalyze's separately labelled estimates.
One submitted search may use one of the 100 daily API requests.