How harsh-o4/codolio-api works
Codolio API exposes live profile scraping by username or URL, plus a raw-HTML endpoint. The controller validates requests and delegates to the scraper service, which fetches Codolio pages and is intended to produce the profile response model. The scraper’s main parsing method is empty in the supplied excerpt, so the HTML-to-profile extraction flow cannot be established. There is no persistence layer or documented README feature detail; external calls and startup wiring are shown only where source supports them.
Main entry points: Program.cs HTTP API host · ScraperService.cs Live scraper · ProfileController.cs Profile endpoints · IScraperService.cs Scraper contract
Components 7
API surface
- HTTP API host
Program.cs - Profile endpoints
Controllers/ProfileController.cs
Scraping service
- Scraper contract
Services/IScraperService.cs - Live scraper
Services/ScraperService.cs
Profile data
- Profile response
models/Profile.cs
Other components
- API caller
- Codolio pages
Connections 7
- API caller → HTTP API host: sends request
Program.cs - HTTP API host → Profile endpoints: routes requests
Program.cs - Profile endpoints → Scraper contract: delegates scraping
Controllers/ProfileController.cs - HTTP API host → Live scraper: registers client
Program.cs - Scraper contract → Profile response: returns profile
Services/IScraperService.cs - Live scraper → Codolio pages: fetches HTML
Services/ScraperService.cs - Live scraper → Profile response: builds response
Services/ScraperService.cs