# api-company

Meta-repo for the `leeworks-apis` recursive build loop. This repo holds cross-cutting concerns; the actual APIs each live in their own repo.

## Sibling repos

| Repo | Purpose | Status |
|---|---|---|
| [leeworks-agents/zip-enrichment](https://gitea.leeworks.dev/leeworks-agents/zip-enrichment) | US ZIP code enrichment (Census ACS + HUD-USPS) | Phase 1 |
| [leeworks-agents/holidays](https://gitea.leeworks.dev/leeworks-agents/holidays) | Public holidays and business days | Phase 1 |
| [leeworks-agents/air-quality](https://gitea.leeworks.dev/leeworks-agents/air-quality) | AQI + pollen + forecast | Phase 1 |

## What lives here

- `MASTER_BUILD_PROMPT.md` — the prime directive driving the build loop
- `ROADMAP.md` — cross-repo milestones (Phase 0–6)
- `STATUS.md` — living revenue + infra scorecard
- `docs/pre-launch-checklist.md` — go-live gate checklist (run the day before public launch)
- `SESSION_LOG.md` — append-only log of agent work sessions
- `research/RESEARCH_LOG.md` — market research findings, candidate API ideas
- `flux/` — cluster-level Flux manifests (registry, runner, monitoring, docs-site)
- `monitoring/` — Prometheus, Grafana, Gatus configs
- `docs-site/` — Astro + Redoc site at `docs.leeworks.dev`

## How this gets worked on

The `agent-company` Kubernetes deployment in `0xWheatyz/Talos` runs three crons every 5 hours:

- `/manager` discovers `agent-ready` issues here and in each API repo, fans out `@repo-manager` subagents
- `/sprint` reads `ROADMAP.md` and breaks down the next phase into new issues
- `/ship` merges approved PRs and creates upstream PRs to `0xWheatyz` forks

Goal: $100/mo net revenue via RapidAPI marketplace listings.