> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/use/source-code/manage-learn/ml-core-service/overview.md).

# Overview

The ML Core Service is a pivotal component within the Manage Learn system. Its primary function involves generating resources according to specified roles and locations, in addition to furnishing data based on user particulars. This service is instrumental in producing programs and solutions. Its utility extends beyond mere assistance for support, administration, and users; it also serves as a foundational resource for various other components integrated into the Manage Learn framework.

For further information, please visit the following link: [click here](/learn/functional-capabilities/manage-learn/overview.md)

For step-by-step instructions on creating programs and solutions, please consult the document provided below:

{% embed url="<https://docs.google.com/document/d/1lpOYKVn7gbzCfNK5QwACUDELY2vk9y97M8STI1_mlPA/edit>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ed.sunbird.org/use/source-code/manage-learn/ml-core-service/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.