Fantasy Project
Fantasy Project automates an ESPN fantasy football league: it ingests player data, scores and optimizes rosters, and runs the resulting lineup, waiver, draft and trade actions against ESPN. The work is split across four repositories, coordinated from this one:
- fantasy-core-pipeline: FastAPI backend, ingestion and optimization. It is the only service that publishes to RabbitMQ.
- fantasy-browser-worker: Playwright and LLM automation worker that acts on ESPN.
- fantasy-web-ui: the React console.
- fantasy-infra: Kubernetes manifests, the job catalog and secrets wiring.
Disclaimer and scope
Fantasy Project is an independent personal project. It is not affiliated with, endorsed by or sponsored by ESPN or The Walt Disney Company. "ESPN" is used only to say which service the project works with.
- Unofficial endpoints. The project works with ESPN Fantasy through undocumented endpoints and browser automation, not a public API. ESPN can change them at any time, so features can break without notice.
- Personal use only. Use your own ESPN account, on leagues you are a member of.
- No scraping. The project doesn't scrape ESPN. It isn't meant for collecting data about other leagues or other users, or for using ESPN at scale.
- Terms of service. Automating actions such as lineup changes, waiver claims, trades and draft picks may conflict with ESPN's terms of use. You are responsible for complying with them, and you use the project at your own risk.
- Rate and impact. The bots act on one league at the volume of a person managing their team: periodic syncs of that league's data and individual roster moves.
Where to start
- Overview: architecture, end-to-end flows and the project map.
- Installation and configuration: running the stack yourself.
- Integrations: ESPN, LLM providers and other external services.
- Repositories: per-repo documentation.
- Contributing: how to work on the code and these docs.
Planning: the wayfinder map
The cross-repo epic taxonomy is charted as a wayfinder map: a single GitHub issue that indexes decisions and points at the child-issue tickets that hold their detail. See .wayfinder/tracker.md for how the map's operations map onto GitHub Issues.
Each of the four repos still owns its own issues. The map only groups them into epics; it doesn't replace per-repo issue tracking.