Download the register. Use the API. Keep v0 separate.

Licence

One limit worth stating plainly, and it is not a restriction on the bridges: CC0 can waive only rights Reep holds, so it does not grant rights in third-party source material, and each release carries its own provenance notes. Sponsorship and consultancy have separate terms but do not change access to the public Register.

Download surface

The DuckDB link always resolves to the current release's convenience build; the file itself is per-release on R2 and CSV bundles are linked from the release manifest above.

Full raw CSV exports are not committed to git and Git LFS is not the default distribution path. Cloudflare R2 Standard is the canonical launch host for large CSV and DuckDB files; GitHub is for docs, samples and small manifests.

Using the download

The file is a single DuckDB database, reep-register-v1.duckdb. Below: what it's for, a two-minute primer, a prompt to hand your AI, and how it compares to the API. Every count is read from the current release manifest, so it matches the file you download.

What it's mainly for: a crosswalk

Reep resolves football entities to stable Reep IDs and maps external provider IDs onto them. The single most useful thing in the file is the bridges table (provider, namespace, external_id, reep_id). Join your Opta, Transfermarkt or Wyscout IDs to it and you get one stable identity, plus canonical names, aliases and relationships.

Full entity breakdown, provider roles and per-competition coverage live onthe coverage page. What's deliberately excluded (DOB, minors, raw evidence) is in What is in scope below.

Hand it to your AI

Matching your data against the register is a good job for an AI assistant. This prompt gives it the context (what the data is, what it's for) and tells it to ask you about your data and goalfirst, rather than guessing your use case.

I've downloaded a DuckDB database from Reep, an open (CC0) football identity register. Before we do anything with it, read this context, then ask me questions.

What it is: Reep resolves football entities (players, coaches, referees, teams, competitions, seasons and matches) to stable Reep IDs, and maps external provider IDs (Opta, Transfermarkt, Wyscout and others) onto those IDs.

What it's mainly for: it is a crosswalk. Its most valuable use is reconciling football data that uses different providers' IDs into one identity, and enriching records with canonical names, aliases and relationships. Key tables:
- bridges(provider, namespace, external_id, reep_id): the provider-ID crosswalk
- entities(reep_id, entity_type, status, label): one row per resolved identity
- aliases(reep_id, alias, kind, rank, language): alternate/historical names for fuzzy matching
- relationships(from_id, to_id, kind): typed edges (team-season participation, affiliation, succession, …)
- redirects(old_id, reep_id): retired IDs mapped to their survivor; always resolve through this, never assume an ID has vanished
There is also an entity_search full-text index for name search.

Your first step: do not assume my use case. Ask me what data I have, which columns and provider IDs are in it, and what I'm trying to achieve. Once I've answered, propose an approach, help me load and query the file in DuckDB, join my data via the bridges table (falling back to alias name-matching where there is no provider ID), and flag ambiguous matches for me to confirm rather than guessing.

The file is reep-register-v1.duckdb, downloadable from https://reep.football/downloads .

Two-minute DuckDB primer

DuckDB is a single-file analytical database. Think SQLite, but for analytics. No server: open the file and run SQL. Install the CLI (brew install duckdb), the Python package (pip install duckdb), or query it in the browser with DuckDB-Wasm. Then:

duckdb reep-register-v1.duckdb "SHOW TABLES;"

SELECT e.reep_id, e.label, e.entity_type
FROM bridges b JOIN entities e USING (reep_id)
WHERE b.provider = 'transfermarkt'
  AND b.external_id = '<their-id>';

SELECT reep_id, alias, language
FROM aliases
WHERE alias ILIKE '%vardy%';

The database is self-describing: SHOW TABLES; lists every table andDESCRIBE entities; shows its columns. A machine-readableschema and per-filechecksums ship with every release.

DuckDB or the API?

Both serve the same stamped register. The download is for whole-register work offline; the API is a keyed, rate-limited convenience for single live lookups with automatic redirect resolution.

What is in scope

API surface

The API is a manually issued, rate-limited convenience over the same stamped public Register. Keys and request limits protect service reliability; they do not unlock additional fields or provider coverage. Use CSV or DuckDB for bulk ingestion.

v0 archive

Docs and correction paths