> 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/~/revisions/CtwXOp8BlQZpECgk64tz/reader-management-system/documentation/windows-installation-and-operation-manual/magensa-remote-services.md).

# Magensa Remote Services

A Remote Services (RS) account is required for billable services. An RS account is NOT required for non-billable services. Billing is triggered by RS activity (this middleware does not affect the billing mechanism within RS). Middleware operates between Magensa RS and the client application.

The primary feature of this middleware is enabling developers or users to auto-launch or perform single-click actions within their application to:

* Load firmware for MagneSafe readers.
* Load both Main Firmware (FW) and Bluetooth Low Energy (BLE) Firmware.
* Load firmware by Device ID, allowing compatibility across multiple reader generations with different firmware versions.
* Load terminal and application settings.
* Load CAPKs (Certification Authority Public Keys).
* Load encryption keys.
* Load device configurations.&#x20;

## Onboarding <a href="#id-2.1_onboarding" id="id-2.1_onboarding"></a>

MagTek will provide the necessary Profile configurations and Web API Keys if requested.


---

# 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/~/revisions/CtwXOp8BlQZpECgk64tz/reader-management-system/documentation/windows-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.
