> For the complete documentation index, see [llms.txt](https://docs.sajix.com/overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sajix.com/overview/readme.md).
# Overview
Empowering Healthcare, Transforming Outcomes.
### Hi there 👋
Sajix Inc. works toward building sustainable, affordable and comprehensive healthcare platform for care providers and care users.
Sajix Inc. is driven by a profound vision for the future. We are dedicated to crafting an expansive ecosystem in healthcare that not only meets today’s needs but sustains and thrives for generations to come. We envision a world where healthcare is not just a service but a holistic experience, accessible to all, and economically viable.
***
### Useful Links
{% hint style="info" %}
Contribution guidelines - We love your input! We want to make contributing to [Tech-Stack Connect Program](https://github.com/orgs/SajixInc/discussions) as easy and transparent as possible.
{% endhint %}
---
# 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://docs.sajix.com/overview/readme.md?ask=&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.