Who is Gluto?

April 16, 2026 · Gluto.ai

Gluto is the name of your assistant on Gluto.ai — the voice you chat with in plain language, the one that remembers you are not asking about gluten-free life in the abstract: you are trying to eat, travel, and decide safely with celiac disease.

The name is a little myth we enjoy: a made-up guardian spirit from Greek-sounding roots (purely for storytelling — not a figure from classical mythology) who looks out for people who must avoid gluten. Think of Gluto as the small god in your pocket whose job is not to impress you with trivia, but to save you time, surface evidence, and help you stay on the safe side of the plate.

If you know ChatGPT’s “Deep Research,” meet the celiac-shaped version

OpenAI’s Deep Research in ChatGPT is explicitly an agentic workflow: you describe what you need; the system can plan, search and read the public web (and files or connected sources you allow), work across many steps, and return a structured, cited-style report — built for questions that would take a human a long time to click through manually. OpenAI positions it for multi-step aggregation and synthesis, not a one-line fact. See Introducing deep research and Deep research in ChatGPT (Help Center) for the official picture.

Agentic systems in general mean the same thing engineers usually mean: instead of a single model guessing once, a coordinator breaks work into actions (search, read, compare), runs tools, and synthesizes a final answer. Deep Research is one famous consumer example; enterprise copilots and research bots follow the same pattern.

Gluto is built in that spirit — but only for celiac disease and gluten-free living. You still get a chat that feels as natural as talking to a general assistant, but underneath Gluto is a multi-agent system: a coordinator plus several specialist agents, each with permission to search the internet, read pages, and (where we have connected them) pull from curated publications and internal evidence (for example medical PDF collections for the research-oriented specialist).

Gluto is the orchestrator

In that stack, Gluto is not just another label on the same model — it is the orchestrator. It reads your message, assigns work to the right specialist tool (sometimes more than one in parallel), waits for evidence and partial results to come back, and can assign additional tasks in a later round if the situation needs another pass (for example: first find nearby candidates, then dig menus or reviews for two finalists). When enough evidence is on the table, Gluto merges everything and responds to you in one voice — usually in a conversation-sized amount of time, not a thirty-minute lab report, unless you explicitly ask for deeper research.

The bench: seven specialists (and what each is for)

When we say multi-agent, we mean a bench of specialists — not seven separate apps you must discover. Gluto invites them. Each specialist is implemented as its own pipeline: it can query the web, follow links, read text from many sites, and where configured use retrieval over published or internal documents. Here is the roster in plain English:

• Medical internet research — Evidence-forward answers on celiac disease, testing, symptoms, complications, and closely related medical topics, with sources preserved so you can verify and share with your clinician.
• Therapy-style support — Emotional weight of the diet: anxiety, family pressure, dating, burnout. Still grounded in reputable coping and mental-health material found on the web, not generic pep talk.
• Food ordering safety — Practical scripts for this dish at this kind of restaurant: what to ask the server, how cross-contact might appear on the line, how to order more safely.
• Product comparison — Packaged foods: ingredients, certifications, substitutions, “is brand A safer than brand B for my household?”
• Restaurant investigator — When you name a specific venue and need a deep web pass (reviews, forums, social posts, articles) beyond what our map already stores.
• Gluten-free recipe finder — Complete cooking paths with constraints (dairy-free, nut-free, quick weeknight, etc.), not a vague link dump.
• Celiac travel companion — Airports, phrase cards, destination norms, how to communicate risk in another language, trip planning that respects strict gluten avoidance.

Separately from that “seven,” Gluto also carries map-aware tools for near you discovery: combining your approximate location (when you allow browser location or when we infer a coarse region from network context), our vetted restaurant data, and semantic search so “fried chicken near me” is not a random list from the open web alone.

What happens when you send a message? Walk-through: “Celiac safe fried chicken near me”

1. Gluto reads the intent. This is a location + food craving + safety ask, not a medical diagnosis thread and not a product barcode question. The coordinator steers toward nearby discovery and, if needed later, menu-level reasoning or a restaurant deep-dive.
2. Location context. When you have allowed it, Gluto can use browser geolocation for a precise “near me.” Otherwise it may fall back to coarse IP-based geography (imprecise, but enough for many metro areas) or whatever city you typed. Honest systems never pretend they know your table at a window seat — they approximate, then improve when you share more.
3. Candidate places. Gluto pulls from our map-grade restaurant pool (distance, safety-style scores where we have them, and semantic match to “fried chicken” and celiac context), then can open the public web for menus, recent reviews, hours, and photos when links exist.
4. Quality and safety lens. The answer should not be “here are ten random pins.” Gluto’s specialists and tools are biased toward cross-checking what people say online with what we already store, highlighting cross-contact cautions, dedicated fryers where mentioned, and clear tradeoffs (crispy vs. shared oil vs. baked).
5. One answer. You get a short list of actionable options with why each might fit — not a wall of URLs without interpretation.

Follow-ups — the conversation keeps working

After the first reply, you stay in the same thread. Examples:

• “Which one is better for a date night?” — Gluto can re-rank with ambiance, reservation friction, and quieter seating in mind, still anchored in safety notes from reviews and our data.
• “Which are open right now?” — Another pass against hours on official pages and maps; we remind you that hours drift on holidays.
• “Which is the least greasy / most vegetable-forward?” — That nudges toward menu text and community descriptions, not fantasy nutrition facts.

Each follow-up is another agentic lap: Gluto decides whether to call the same map tools, the restaurant investigator, food-ordering safety, or a quick web read on a URL you paste — then summarizes again so you can decide.

When your group has more than one worry

Celiac decisions are rarely solo. One person cares about dedicated fryers, another about price, another about noise for kids, another about romantic lighting. You can dump all of that into one message. Gluto’s job is to normalize the constraints, hunt evidence for each, and return a single plan nobody has to screenshot from five tabs.

Why we still say “talk to your doctor — and the restaurant”

No assistant replaces a clinician or the staff who actually cook your meal. Gluto’s role is to compress research time and surface questions you should ask, with citations where we found them, so your final yes/no stays yours.

Gluto is the name we gave to a celiac-only, multi-agent research desk that fits in your pocket: as capable in spirit as the new wave of “deep research” chat tools — but narrow, hungry for sources, and obsessed with gluten-free safety instead of the whole internet.