> For the complete documentation index, see [llms.txt](https://docs.nfh.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfh.global/use-cases/rooftop-solar-prosumers.md). # Rooftop solar & prosumer energy markets Peer-to-peer rooftop solar, portable net-metering credits, and demand response — a prosumer energy market on NFH fabric. A farmer with a 5 kW rooftop array generates far more at noon than the household uses, and the local utility pays a thin feed-in rate for the surplus. Next door, a cold-storage owner is buying expensive daytime grid power. They can't trade with each other — the meter, the utility portal, and the settlement rails all assume one seller (the utility) and many passive consumers. NFH fabric turns rooftops, EV fleets, and flexible industrial loads into **addressable participants in a real-time energy market** — able to discover each other, contract under network policy, and settle instantly against metered delivery. ## What changes * A prosumer sells surplus daytime solar to a **neighbour or nearby business** at a better price than the net-metering rate — improving ROI in exactly the hours their own use is lowest. * Net-metering credits become **portable across a participant's sites** (one site → another site's bill) because entitlement is a credential, not a hard-wired meter address. * A rooftop-solar EPC can stitch **lead → survey → grid approval → rebate → payout** into one journey, because each step is a signed, discoverable action instead of a separate portal. * A load-intelligence platform routes charging and industrial loads to **off-peak hours and nearby surplus solar** without a multi-month integration per utility or prosumer. * The distribution utility gets **demand-response participation and peak shaving** without new transformer capex. ## Where to start Stand up a sandbox Network Adapter for one feeder. Register two prosumers and one flexible load, publish a signed surplus-kWh catalogue, and run a simulated noon-hour matching-and-settlement loop under a simple feeder-limit policy. Production is the same code with the utility's real endpoints and policy pack. --- # 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.nfh.global/use-cases/rooftop-solar-prosumers.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.