WaveWeigh
Today's food scanning apps recognise what's on the plate, but estimate portion sizes from a flat 2D photo — and portion size is where most of the calorie error comes from. WaveWeigh measures food volume directly in 3D, so the numbers are actually accurate. Available as an API for nutrition apps. Join the waitlist for early access.
If we reach 1,000 signups, we'll build it.
The problem with food scanning today
Every nutrition tracking app, calorie counter, and GLP-1 platform that offers photo-based food logging relies on the same fundamental approach: identify the food in a 2D image, then estimate the portion size. Food identification has gotten reasonably accurate. Portion estimation has not — because portion size is a measurement of volume, and volume cannot be reliably extracted from a flat photograph.
This is why App Store reviews of nutrition apps are full of complaints about inaccurate calorie counts. Users see "60 calories" when they ate 260. They see "8,000 calories" when they ate 800. The food is recognised correctly. The portion is wildly wrong.
WaveWeigh fixes this by measuring food volume directly in three dimensions. The result is portion estimates that match reality, available as a drop-in API that complements existing food recognition pipelines.
Built for
- Nutrition tracking apps and calorie counters
- GLP-1 telehealth platforms with food logging
- Diabetes management apps requiring accurate carb counts
- Dietitian and nutritionist client platforms
- Bariatric surgery tracking apps
- Sports nutrition and athletic performance apps
- Continuous glucose monitor companion apps
Pricing
WaveWeigh is planned to launch at 5¢ per inference. Waitlist subscribers receive a permanent discounted rate of 3¢ per inference at launch. Further volume-based discounts are available for high-usage customers.
Frequently asked
Who is the WaveWeigh API for?
Nutrition tracking apps, calorie counters, GLP-1 telehealth platforms, diabetes management apps, dietitian tools, bariatric tracking apps, and any food tracking platform where users currently log meals via photo.
How is this different from existing food recognition APIs?
Existing food recognition APIs identify what the food is. WaveWeigh measures how much. Most calorie estimation error comes from portion size, not food identification — and portion size cannot be reliably estimated from a flat 2D photo. WaveWeigh complements existing recognition pipelines.
When will the API launch?
We're targeting launch in 2026. Waitlist subscribers receive early access and discounted pricing.
How will pricing work?
5¢ per inference at launch, with a permanent 3¢ rate for waitlist subscribers. Volume-based discounts available for high-usage customers. Design partner programs include custom pricing for early integration partners.
Are you taking design partners?
Yes — limited slots available for nutrition apps and platforms interested in early integration. Email ja@glucoflo.com.