2024: GenAI APIs and microservices
The year LLM features were shipped as clean, documented APIs, and the first paid client app was built.
- Status
- stable
- Trust
- human-reviewedhuman:rrizwan98 ·
1 min read
- Approved
- human:rrizwan98 ·
Fewer repositories, more of them private: 11 in the year, 6 of them private. For the first time more than half the work is not public, which is what it looks like when learning turns into client work.1
What happened
- LLM-powered APIs. AI-Powered-APIs and GPT Actions in February and March, then two resume tools, a generator and a CV optimiser, in July.2
- Production microservices. An online-mart platform with separate customer and admin APIs in July.
- A real client. A plant-identification app, built in August and reworked as microservices in October and November. It is private, and it is the first line in this record that a customer paid for.
- FastAPI as the backbone. Every AI feature shipped as a documented API.2
The public repositories
| Created | Repository | What it is |
|---|---|---|
| 2024-02-10 | AI-APIs | AI APIs |
| 2024-02-11 | AI-Powered-APIs | LLM-powered API services |
| 2024-03-01 | GPT-action-and-APIs | GPT Actions backed by APIs |
| 2024-05-02 | portfolio | Portfolio site |
| 2024-07-27 | online-mart-customer-api | Customer-side API of the online-mart platform |
Private work
Six private repositories: the online-mart admin API, two resume tools (a generator and a CV optimiser), and three repositories of a plant-identification app for a real client: the app, its microservice, and the identification service.1 They are counted here and never named.
What this era taught
LLMs are only useful when wrapped in reliable services that a business can call.2
Next: 2025: AI agents.
Footnotes
Sources
- [^github-repos]GitHub API, repositories owned by rrizwan98, read 26 August 2026
- [^journey-note]From Predictive AI to Forward Deployed Engineer: My 6-Year Journey, Raza Rizwan, July 2026