Aside from using Arbiter's TUI as a persistent terminal companion, the best way to validate the API is to build on top of it. I'd been doing that while putting together a web portal around it, but I also wanted a smaller, self-contained example for the documentation — an open-source project someone could actually read end to end. Turning plain-English meals into recipes and nutrition macros seemed like a good fit.

The concept was for a nutrition tracker where you describe a meal the way you'd say it out loud — "two eggs and a banana," "grande oat milk latte," "16 oz of water" — and it logs the macros for you, with no searching a food database or building a recipe by hand. It's not meant to be a product. I think it does a great job of showing how little it takes to wire real agents into a project once you have a runtime doing the heavy lifting.

Continue reading