API
This portfolio has an API.
In plain terms: everything on this site is also available as machine-readable data, documented like a real product. If you're building a tool, scraping for a hiring pipeline, or just curious - don't parse my HTML, use this.
Why does a portfolio need an API? Partly because treating your own data as a product is good engineering practice in miniature - typed content, one source of truth, documented contract. And partly because future features (like the npx vedant terminal resume card) will be real consumers of these endpoints.
The whole resume as structured JSON - experience, education, projects, achievements, links.
All projects, including the honest tradeoff notes shown on /work.
Work experience with highlights and stack per role.
Build metadata for the deployment you're talking to: commit, deploy number, test results.
Try it
curl https://vedanthirekar.com/api/resume | jq '.experience[0].company' "Methix"
All endpoints are read-only, unauthenticated, and served statically - they're generated from the same typed content modules that render the pages, so the API can never disagree with the site.