01
Persistent nutrition profiles
Store long-term profiles — demographics, goals, allergies, preferences and history — rather than one-off plan requests.
Platform
ONE by OSCA is infrastructure for product teams. Your users stay in your app or portal while ONE powers profiles, plans, logging and nutrition experiences.
Core principles
Unlike traditional food APIs that stop at search and nutrient tables, ONE supports the journey from requirements to ongoing personalisation.
01
Store long-term profiles — demographics, goals, allergies, preferences and history — rather than one-off plan requests.
02
Allergies and dietary restrictions stay non-negotiable. Preferences can adapt when a perfect plan is not possible.
03
Isolation, credentials, branding and catalog controls so each customer ships under their own brand.
04
Everything is exposed through APIs so ONE runs behind your experience as backend infrastructure or an embedded engine.
Lifecycle
01 Plan
Generate 1–14 day plans from diet types, allergens, preferences and nutrient priorities.
02 Track
Support food logging and consumption history that feeds analysis and future recommendations.
03 Analyse
Inspect macros, micronutrients and progress toward the goals your product defines.
04 Learn
Use preference signals so recommendations and plans become more relevant over time.
05 Optimise
Close nutrient gaps, refine priorities and regenerate plans with clearer nutritional intent.
What stays yours
Clients use ONE as a backend service, a complete nutrition platform capability, or an embedded engine — without requiring end users to interact with ONE directly.
End users never need to know ONE exists. You own UX, identity and go-to-market.
Default rules, supported diets, allergens, catalogs and branding per customer.
Usage visibility and operational hooks that help teams run the integration in production.
Talk to the ONE by OSCA team about how personalised nutrition can fit your product roadmap — and how optional wearable data context can extend it when needed.
Product teams book a demo · Engineering teams explore the API and SDKs