> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/services/reader-management-system/documentation/android-installation-and-operation-manual/magensa-remote-services.md).

# Magensa Remote Services

* Customer needs a Remote Services (RS) Account for billable services
* Customer DOES NOT need an RS Account for non-billable services
* Billing occurs upon RS activity (this middleware does NOT impact the billing mechanics with RS)
* Middleware between Magensa RS and Client App

Its main differentiator is to allow a developer or user to auto-launch or single-click within their app to perform:

* Loads Firmware&#x20;
* Main FW and BLE FW
* By Device ID so blending readers across various generations with differing FW files
* Loads Terminal and Application Settings
* Loads CAPKs
* Loads keys
* Load Device Configs


---

# 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://developer.magtek.com/services/reader-management-system/documentation/android-installation-and-operation-manual/magensa-remote-services.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.
