Skip to content

Archive

Engineering Notes

Articles on React, Next.js, hiring, and full-stack development.

Notes

22

Topics

6

Latest

Apr 12, 2026

01 / FeaturedAI18 min read

If you build with AI, you need keys. This is the expanded version of the shortlist I actually use: one router for breadth, a few vendor consoles for latency and specialty models, GitHub when I already live in tokens, and Cloudflare when the edge is the product, plus how I combine them before I touch billing.

Read article

6

Free-key entry points for real projects

Takeaways

  • 01OpenRouter: one key reaches many models. Use the Models tab “free” filter so paid routes do not fail once you are out of credits; log the model ID on every request so 402s are obvious.
  • 02Google AI Studio, Groq, and GitHub expose usage in the console; NVIDIA and Cloudflare favor per-model keys or schemas. Plan for rate limits and label keys in your secret manager.
  • 03Groq Cloud lives at console.groq.com (not xAI Grok). Prefer expiring keys and revoke when a demo is done, with the same hygiene for GitHub PATs.
  • 04Treat “unlimited” UI rows as marketing-adjacent: upstream RPM/TPM and fair-use still apply; add backoff and a second provider before you demo to investors.

Collection

More engineering notes

RSS feed

Subscribe for new posts, or read how referrals and sponsored placements are handled on this site.