Every recipe & nutrition API I tried was too expensive or too messy. So I'm fixing it.
Hey all 👋 building in public here.
I kept hitting the same wall: I wanted recipe and nutrition data for a project, and every API was either priced for funded companies or gave me inconsistent, half-complete data. Some recipes had no image, some had a bad one, some were missing descriptions or whole fields. I'd pay for it and then burn a weekend cleaning it up.
So I started building Foodashi: a recipe and nutrition API where every recipe is complete and consistent. You send a dish name and get back real ingredients, nutrition computed from 11 official food databases, EU-14 allergen flags, dietary tags, a taste profile, a quality score, and a photo. If a recipe doesn't pass every check, it gets discarded instead of shipped. And where a nutrition value is estimated rather than measured, I flag it instead of pretending it's exact.
What I keep noticing: everyone is building food, health, and recipe apps right now, mostly with AI assistants, and they all hit the same data wall I did. So I'm building the affordable, consistent option for exactly that wave.
It's pre-launch, opening through a waitlist. But mostly I would love your take:
🍳 What's the worst food or nutrition data you've had to build around?
🛠️ If clean, consistent food data was cheap and easy to get, what would you build with it?
Reading every reply.

Replies