AI Macro Calculator

Type a Meal, Get a Rough Macro Estimate — No App.

Describe what you ate — “200g chicken breast, 1 cup rice, olive oil” — and @vustbot gives back a rough estimate of protein, carbs, fat, and calories, free, in the same Telegram chat. This is a general-chat text estimate, not @vustCalBot's photo-vision pipeline — that's a separate, more precise option when you'd rather photograph your plate.

Free tier · text-based estimate · no signup wallFree chat estimate — not a lab measurement
Rough macro estimate from typed textFree multi-model AI chatNo app, no signup wall

Honest framing — two different tools

A text estimate, not the photo pipeline

It's easy to conflate this with @vustCalBot, so we'll say it plainly: @vustbot's macro estimate comes from a typed description in general AI chat — general nutrition knowledge applied to your words, not a vision model reading a photo. @vustCalBot is a separate, photo-only bot: it looks at a picture of your food and does not read typed text at all. Pick the text estimate when you already know your ingredients; pick @vustCalBot's photo path (/cal, /macro-tracker) when you'd rather point a camera at your plate.

Neither path is a lab measurement — both are estimates. The photo pipeline generally needs less manual quantity-guessing from you since it reads the plate directly.
Specimens

See the difference

A typed meal description into @vustbot, the rough estimate that comes back, then a quick correction in the same thread.

A typed meal into a macro estimate

What you tell @vustbot

"Estimate the macros: 200g grilled chicken breast, 1 cup cooked white rice, 1 tablespoon olive oil, a side of steamed broccoli."

What comes back

A rough breakdown — roughly 46g protein, 45g carbs, 16g fat, ~500 kcal — with a one-line caveat that this is a general-knowledge estimate, not a lab-measured value, and that exact numbers shift with cooking method, brand, and precise portion size. It may also ask a clarifying question if a quantity is ambiguous, like whether the rice is measured cooked or dry.

Refine it in the same chat

Follow-up in the same thread

"Actually the rice was dry-measured, and I used 2 tablespoons of oil, not 1."

What comes back

An adjusted estimate reflecting the corrected inputs — dry rice roughly doubles the effective carb count once cooked, and the extra tablespoon of oil adds about 120 calories of fat — because it's a conversation you can correct, not a one-shot lookup.
Practical use cases

Who's estimating macros with @vustbot

People who already know their ingredients
They can describe a meal in words and don't want to photograph it.
Type "200g chicken, 1 cup rice, olive oil" into @vustbot and get a rough protein/carb/fat/calorie estimate back.
Anyone double-checking a rough number
They want a quick sanity check on a meal's macros without a dedicated app.
A ballpark estimate in the same chat, refinable with a follow-up like "actually the rice was dry-measured."
People who'd rather photograph their plate
They don't want to estimate portions themselves.
This page points them to @vustCalBot's separate photo-vision pipeline (/cal, /macro-tracker) instead — a different, more precise tool for that job.
How it works01–03

From a typed meal to a macro estimate

  1. 01

    Type what you ate

    Open @vustbot and describe the meal with rough quantities — "200g grilled chicken, 1 cup rice, 1 tbsp olive oil." This is text chat, not @vustCalBot's photo pipeline.

  2. 02

    Get a rough estimate

    It returns approximate protein, carbs, fat, and calories, with a caveat that this is a general-knowledge estimate, not a lab measurement.

  3. 03

    Refine with a correction

    Say "the rice was dry-measured" or "I used 2 tbsp of oil" and it adjusts the estimate in the same thread.

Same tool · in Telegram@vustbot

A rough macro estimate, from text

Open @vustbot, describe a meal with rough quantities, and get protein/carb/fat/calorie estimates back — a text estimate, not the @vustCalBot photo pipeline.

Open in Telegram
Quality & trust

Honest scope — two different tools, not one

Text estimate, not the photo pipeline

@vustbot's macro estimate comes from a typed description in general AI chat. @vustCalBot is a separate, photo-only bot that reads a picture of your food — it does not read typed text at all. The two are distinct capabilities.

A ballpark, not a lab measurement

The estimate draws on general nutrition knowledge, not a verified database lookup or a scale. Cooking method, brand, and exact portion size all shift the real numbers.

No daily log across sessions

It can total several meals described in one thread if you ask, but doesn't automatically remember yesterday's meals across separate chats. For an automatically-summed daily log from photos, see /macro-tracker.

FAQ

Frequently asked questions

Is this the same as @vustCalBot's photo feature?

No — and this is the key distinction. @vustCalBot is a separate, photo-only bot: you send it a picture of your food and it runs a vision pipeline to estimate calories and macros from the image. @vustCalBot does not read typed text at all — a plain text message to it is silently ignored. This page describes a different capability: typing a food description into @vustbot (general AI chat) and getting a text-based estimate back. If you'd rather photograph your meal than type it out, use @vustCalBot or see /cal and /macro-tracker instead.

How accurate is a macro estimate from a text description?

Treat it as a reasonable ballpark, not a lab measurement. @vustbot draws on general nutrition knowledge to estimate protein, carbs, fat, and calories from what you describe — it does not look up a verified nutrition database entry or weigh your food. Cooking method, exact brand, and true portion size all shift the real numbers. For a same-message double-check, describing the same meal with more precise quantities (grams instead of "a handful") tightens the estimate.

Should I use the text estimate or the photo estimate?

They serve different moments. Typing into @vustbot is faster when you already know your ingredients and rough weights — no photo needed, just describe it. @vustCalBot's photo pipeline is better when you're not sure exactly what's on the plate or don't want to estimate portions yourself; it looks at the actual image. Neither is lab-grade precise, but the photo path generally needs less manual quantity-guessing from you since it's reading the plate directly.

Is this a dedicated macro-tracking app, or general AI chat?

General AI chat, stated plainly. @vustbot is a free multi-model assistant in Telegram — it estimates macros for a meal you describe, in the same thread you might use for anything else. It's not a dedicated nutrition app with a food database, daily totals dashboard, or logged history. If you want your day's meals summed automatically from photos, that's the @vustCalBot / /macro-tracker flow instead.

Can it handle a full day of meals, not just one dish?

Yes — describe several meals in one message or across the same thread ("breakfast was X, lunch was Y, dinner was Z") and it estimates each, then can total them if you ask. It won't automatically remember yesterday's meals or keep a running daily log across separate chat sessions; each estimate works from what you type in that conversation.

Does a macro estimate cost anything, or need an account?

Yes to free, no to accounts. Your Telegram identity is the login — no email signup, no card required to get a macro estimate. The free tier runs on GPT-5.6 Luna and Gemini 3 Flash; heavier models are available on paid tiers, but a text-based macro estimate costs nothing to generate.

Ready when you are

Type a meal, get a rough estimate.

Free text-based macro estimate. For a photo-based estimate instead, see @vustCalBot.