Skip to main content

reep

CI PyPI Python versions License: MIT

Python SDK and command-line tool for the Reep Register, the open crosswalk of football provider IDs.

pip install reep            # or: uv tool install reep
reep catalog sync           # download the register (about 210 MB, no key)
reep resolve transfermarkt spieler 568177
reep translate transfermarkt/spieler/568177 --to fbref
import reep

reep.catalog.sync()
reg = reep.Register.local()
res = reg.resolve("transfermarkt/spieler/568177")
print(res.status, res.reep_id, res.label)  # found rp53af22bbeaa667 Cole Jermaine Palmer

What it does

  • Downloads the dated public release and checks every file against its SHA-256.
  • Keeps the local copy current by replaying the release changelogs, and downloads a snapshot when it cannot.
  • Resolves a provider ID, given as the full (provider, namespace, external_id) triple, to its current Reep ID. Merged IDs resolve to their survivor; withdrawn IDs return a status, never an empty ID.
  • Translates an ID from one provider to another, and adds Reep IDs to pandas, polars or pyarrow tables.
  • Fills Reep IDs and other providers' IDs into your own PostgreSQL, MySQL, SQL Server or SQLite tables (reep sync). It runs as a dry run unless you add --apply, writes only to empty cells, and lists the rows that need review (reep review).
  • Reads the SDK catalogue, release CSVs you already have, the release DuckDB file (REEP_DUCKDB_PATH), or the hosted API with a key (REEP_API_KEY).
  • Gives AI agents a stable interface: --json output with a versioned envelope, JSON errors with hints, fixed exit codes, a skill file (reep skill install) and a read-only MCP server (reep mcp, extra reep[mcp]).

Matching is exact. The package does not match records by name: the public release has no dates of birth, so name matching gives unreliable results.

Documentation

The documentation is at https://reep.football/docs/python/ (source in docs/): a quickstart, the concepts (provider ID triples, stored-ID states, releases), the data sources, the database sync, the command line and the Python API. Build it with uv run --group docs sphinx-build docs docs/_build/html.

Reporting a wrong ID

Data corrections (a wrong ID, a bad merge, a missing entity) go to https://reep.football/submit. Issues in this repository are for the SDK and CLI code.

Contributing

See CONTRIBUTING.md. This project follows the Contributor Covenant. The development plan shows the units of work.

Licences

The code in this repository is MIT-licensed. The Reep Register data is CC0-1.0.

Metadata

Release files for reep 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for reep 0.1.0
File Size Uploaded
reep-0.1.0.tar.gz 151.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for reep 0.1.0
File Interpreter ABI Platform
reep-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 259.9 kB

Release files / reep-0.1.0.tar.gz

Download URL reep-0.1.0.tar.gz
Size 151.3 kB
Tags Source
SHA-256 checksum
How to use checksums
71f90e4859449cbb0e023c68f13167e436abdd9fdfe0ecdda02345fae029f2ee
BLAKE2b-256 checksum
How to use checksums
8c24b91d8721359e6fc687c10698f5841112568349e997911bbc0ad23524263a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.

Transparency log

Release files / reep-0.1.0-py3-none-any.whl

Download URL reep-0.1.0-py3-none-any.whl
Size 108.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6b664e26643f79dc035d9e2c0465fe73cc0e84597a58ba88f19856d7adc0ad24
BLAKE2b-256 checksum
How to use checksums
a725d8685d754bc38dff4854c1f960de0ec2ecbb1f5848829339c6d7e2a113bd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page