> For the complete documentation index, see [llms.txt](https://saral.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saral.sunbird.org/readme.md).

# Sunbird Saral Overview

Overview

Sunbird Saral attempts to create a connection between the information that exists in the physical world and ties it to digital structured information.

Saral literally means simplicity, has been conceptualized to enable users to create structured digital information using mobile devices. The process is also called Saralify or Phygitization. Saral should be viewed as an OCR-plus application that is capable of doing OCR and can also understand the structure of the physical input.

Saral v1.x works as an edge location solution to phygitize  data on physical layout printed sheets and upload the data to the backend. This backend data will be then pushed to [`CQube`](https://cqube.sunbird.org) (Analytics system) for insights and take actions accordingly.

[`Saral SDK`](/engage/saral-sdk-source-code-repository.md)  is  the core Phygitization component interfaced with [`Saral Layout Specification`](/learn/specifications/layout-specification.md). Saral v1.x App is a reference Android App built on [`Saral SDK`](/engage/saral-sdk-source-code-repository.md)&#x20;

[`Saral SDK`](/engage/saral-sdk-source-code-repository.md)  can be used to build custom Android applications with OCR capabilities(OMR, Handwritten Digit recognition)`. Refer` [Application Architecture](/learn/saral-app-architecture.md) for more details about [`Saral SDK`](/engage/saral-sdk-source-code-repository.md)

Download the Saral poster below to get a brief overview of how Saral can make a difference:

{% file src="/files/XVFt6KH6MMmbBedgOR8Z" %}

&#x20;                                               &#x20;


---

# 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 dynamically by asking a question.

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

```
GET https://saral.sunbird.org/readme.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 `build a script that syncs our docs to a CMS` 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.
