# Core Concepts

### Features and Suggestion Types

In general terms, the output of our APIs is personalized food suggestions, which is why we are called Suggestic 😉. These suggestions can take many forms, such as recipe recommendations or specific dishes at nearby restaurants.&#x20;

In addition to personalized food suggestions, we provide a set of interconnected tools, like food logging and shopping lists, that leverage the same underlying personalization technology. Together, suggestions and tools can be used to create a more holistic nutrition experience.

Here's a general list of available features and suggestion types:

* Recipes
* Meal Plans
* Shopping Lists
* Restaurants, Menus, and Menu Items
* Food Logs
* Program Content and Guidance

### Personalization

Conceptually, the Suggestic platform defines personalization at 3 different levels of depth, as follows:

1. **Program (or diet)** - Represents the base rules used to generate food suggestions. i.e., Vegan Diet.&#x20;
2. **User Data** - Refers to any type of user preferences or data stream associated specifically with an individual user. i.e., food restrictions.
3. **Filters** - These can be set to further refine food suggestions. i.e., cuisine type.

![Generating a food suggestion involves all 3 levels of personalization](/files/-M3qcpj7ePG4YIkZ05lo)

{% hint style="info" %}
Please note that throughout the documentation we may interchangeably use the terms diet or program.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.suggestic.com/graphql/start-here/core-concepts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
