How withqwerty/reep works
Reep v0 is a frozen football-identity register with a legacy API for looking up entities and mapping provider IDs. Callers send requests to the Cloudflare Worker, which serves lookup, search, resolution, and batch operations against D1; contribution uploads are an additional path to R2. The repository also contains frozen CSV snapshots. The sampled Worker excerpts are partial, so the graph omits uncertain route wiring and any connection between those files and the runtime database.
Main entry points: worker.ts API Worker
Components 19
API runtime
- API Worker
src/worker.ts - Request authentication
src/worker.ts - Entity lookup
src/worker.ts - Name search
src/worker.ts - Provider lookup
src/worker.ts - ID resolution
src/worker.ts - Batch operations
src/worker.ts - Freeze metadata
src/worker.ts - Contribution upload
src/worker.ts
Identity register
- People snapshot
data/people.csv - Teams snapshot
data/teams.csv - Competitions snapshot
data/competitions.csv - Seasons snapshot
data/seasons.csv - Names snapshot
data/names.csv
External services
- D1 register
- R2 contributions
- Unkey
- RapidAPI proxy
Other components
- API caller
Connections 17
- API caller → API Worker: requests
- API Worker → Request authentication: checks auth
- API Worker → Entity lookup: dispatches
- API Worker → Name search: dispatches
- API Worker → Provider lookup: dispatches
- API Worker → ID resolution: dispatches
- API Worker → Batch operations: dispatches
- API Worker → Freeze metadata: adds metadata
- API Worker → Contribution upload: dispatches
- Entity lookup → D1 register: queries
- Name search → D1 register: queries
- Provider lookup → D1 register: queries
- ID resolution → D1 register: queries
- Batch operations → D1 register: queries
- Request authentication → Unkey: verifies keys
- Request authentication → RapidAPI proxy: checks proxy secret
- Contribution upload → R2 contributions: stores uploads