Meal scanning and food search
Meal Scan and food search use a database of 5M+ foods, including brands, restaurants, and recipes, to turn meal photos or food descriptions into structured nutrition data.
Nutrition APIs and health context intelligence for developers and care teams.
January AI provides nutrition and metabolic APIs alongside a Health Context Engine for digital health applications. Meal inputs can become structured nutrition data and estimated glucose responses, while the context engine assembles longitudinal health records and returns structured answers with citations.
The platform offers developer APIs, clinician tools, and consumer experiences. Free and Pro API access is for non-clinical use under the Developer Terms, with U.S. eligibility and data restrictions. Healthcare deployments involving protected health information require a separate Enterprise agreement before data submission.
Meal Scan and food search use a database of 5M+ foods, including brands, restaurants, and recipes, to turn meal photos or food descriptions into structured nutrition data.
The glucose API estimates a two-hour glucose curve and impact level without requiring a CGM. Healthy Food Alternatives provides suggestions for different food choices.
The Health Context Engine brings together clinical records, patient-generated data, omics, biomarkers, and claims. It resolves the record against SNOMED-CT, LOINC, RxNorm, ICD-10, and CPT.
The engine combines inference with deterministic clinical rules and retrieves guidelines, landmark trials, and curated literature. Citations make structured outputs traceable to their evidence.
For healthcare deployments under an applicable Enterprise agreement, capabilities include natural-language patient context queries, behavior guidance, risk stratification, and next-action recommendations.
January’s Clinician Nutrition Monitor runs inside the Epic patient chart. Regulated-data access and clinical use depend on the applicable Enterprise agreement.
Digital health developers can combine meal capture, food lookup, and predicted glucose responses to give users feedback as they log meals.
Enterprise care teams can query a consolidated patient timeline spanning laboratory results, medications, wearable signals, and claims when preparing a care review under their healthcare agreement.
Teams operating under an applicable healthcare agreement can use patient context and cited evidence to support patient-facing conversations. Free and Pro APIs are not authorized for clinical decision-making.
Organizations can deploy January experiences under their own brand through a custom Enterprise agreement rather than assembling every consumer workflow themselves.
Sign up at dashboard.january.ai, create an API key, and make a first API call. REST endpoints cover nutrition, glucose prediction, and health context; documentation is available at docs.january.ai.
Free includes three API keys and 1,000 credits. Pro is $99 per month with 10 keys and 10,000 monthly credits. Startup is listed at $749 per month with unlimited keys and 100,000 monthly credits; access requires an application. Enterprise offers custom volume and pricing.
Requests are metered by endpoint family, including scans, searches, and glucose predictions. Free/Pro terms enforce allowances and reset them each billing period without carryover. Pro bills monthly in advance and renews until cancellation.
No. Their Developer Terms prohibit PHI and clinical decision-making, diagnosis, treatment, or emergency use. PHI projects must move to Enterprise before submitting data. BAA, HIPAA-aligned practices, and SLAs are available only under a separate Enterprise agreement; Startup’s pricing labels do not establish PHI permission.
Customers and end users must be in the United States. Output may be used within the customer’s application, but the terms prohibit sending glucose curve predictions to third-party platforms or redistributing the API or output as a standalone data feed.
Os dados de tráfego são apenas para referência.