reep
Python SDK and command-line tool for the Reep Register, the open crosswalk of football provider IDs.
Status: in development. Version 0.0.1 reserves the package name and has no SDK functions yet. The first working release is 0.1.0. The development plan describes what it will do and in which order.
Use the register today
- Download the complete release (CSV and DuckDB, CC0): https://reep.football/downloads
- Hosted lookups with an API key: https://reep.football/api
What 0.1.0 will do
- Download and verify a dated release, and keep it current from the release changelogs.
- Resolve a provider ID, given as the full
(provider, namespace, external_id)triple, to its Reep ID, and follow merge redirects. - Translate an ID from one provider to another.
- Give AI agents a stable interface: JSON output with a fixed envelope, documented exit codes, and an MCP server.
Later releases add a guarded sync of Reep IDs into your own Postgres, MySQL or SQL Server tables, with a report of the rows it could not resolve.
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.
Licences
The code in this repository is MIT-licensed. The Reep Register data is CC0-1.0.
Metadata
Release files for reep 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| reep-0.0.1.tar.gz | 5.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| reep-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.3 kB
Release files / reep-0.0.1.tar.gz
| Download URL | reep-0.0.1.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ffd05a3eee390b7d14a489e8aa2965ad7f057bad1f0cfff714cda270ef4be865
|
|
BLAKE2b-256 checksum How to use checksums |
f61f569dbecca7405e0639437a52f8a9203ca2a7b8bc39ed01d03382546424c5
|
| 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 12, 2026.
Transparency logRelease files / reep-0.0.1-py3-none-any.whl
| Download URL | reep-0.0.1-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7a244a661f706c5fa7aa22b594cd4ffe560a911f5899bc0712961df8d53d20bd
|
|
BLAKE2b-256 checksum How to use checksums |
a94c1265cd635446ee189e3486e947d76ef1d98d0aaa5153ac7321517696c7de
|
| 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 12, 2026.
Transparency log
