> 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/cheapest-kilowatt.md). # Energy procurement at data-centre scale Continuous energy procurement at data-centre scale. A hyperscale operator spends 30–50% of operating cost on electricity, and the cheapest electron at any given hour is rarely from the same supplier. Yet procurement is locked into long-dated bilateral contracts, because spot-market access is fragmented, onboarding a new supplier is slow, and verifying a carbon-intensity claim means chasing self-reported PDFs. An NFH fabric-aligned procurement stack lets the operator — or an autonomous agent acting for it — treat energy as a **continuous, signed, verifiable spot market**. Suppliers publish kWh offers; the operator [discovers](/product-documentation/products/discovr.md) and contracts hourly against policy; payment [settles](https://docs.finternetlab.io/) atomically against metered delivery; and every kWh is [anchored](/product-documentation/products/observability-audit.md) for downstream carbon reporting. ## What changes * **Procurement moves from a quarterly contracting cycle to a continuous spot motion** — the operator buys the cheapest compliant electron each hour. * **Carbon-intensity claims are signed and replayable**, not self-reported PDFs — so sustainability reporting is provable, not asserted. * **Suppliers below the threshold for traditional broker access reach demand directly** — widening the supply pool and sharpening price competition. * **Variable-renewable supply finds price signal at the granularity it actually has** — solar and wind get matched to load hour by hour. * **An agent can run the loop** — discovery, contracting, and settlement happen under explicit spend and carbon policy, with a full audit trail. ## Where to start Set up a sandbox Network Adapter, publish a single-supplier test catalogue, and run a simulated hourly procurement loop against it under a simple price-and-carbon policy. Migration to production is the same code with production endpoints — so validate the policy and the carbon-credential schema first. --- # 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/cheapest-kilowatt.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.