> For the complete documentation index, see [llms.txt](https://docs.myrspoven.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myrspoven.com/integrations/overview/energy-data/metry.md). # Metry [Metry](https://metry.io/) is a Swedish energy-data platform that consolidates meter readings from utilities and aggregators. When meters are read by the energy company rather than wired into the Building Management System (BMS), myCoreAI pulls hourly readings from Metry instead of routing through the building automation layer. See the [Energy data overview](/integrations/overview/energy-data.md) for how energy data flows into myCoreAI across BMS, third-party, and manual paths. ## When Metry is the right route Metry applies when one or more of the following is true: * Meters are billed and read by the energy company, not connected to the BMS. * A Metry account already consolidates the building's meter readings. * Hourly resolution is required but the meters are not exposed on the BMS. When meters are already on the BMS, that path is preferred — myCoreAI reads them directly with no extra integration. ## Resolution * **Hourly readings** when the underlying utility provides them. Required for optimization and detailed reporting. * **Daily or monthly readings** otherwise. Usable for reporting but limits optimization — see the [overview](/integrations/overview/energy-data.md#why-low-resolution-data-limits-what-myrspoven-can-do). myCoreAI treats Metry-sourced meters like BMS meters for analysis and reporting. The data pipeline tags them separately to preserve provenance. ## Requirements * An active Metry account covering the connected buildings. * Read access granted to Myrspoven from inside the Metry account. Myrspoven walks customers through the exact step at onboarding. * A confirmed mapping between Metry meter IDs and the buildings represented in myCoreAI. ## Cost Metry bills data access directly per their contract. Myrspoven does not charge separately for the integration. ## Alternatives * **Mestro** is the other supported third-party provider in Sweden. New providers are evaluated case by case — see [Requesting a new third-party integration](/integrations/overview/energy-data.md#requesting-a-new-third-party-integration). * When automated integration is not possible, [manual upload](/integrations/overview/energy-data/manual-upload.md) is available. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.myrspoven.com/integrations/overview/energy-data/metry.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.