How Do You Access Utility Usage and Billing Data Without an API?
Almost no utility provider offers a public API for usage or billing data. A logistics company tracking energy costs across a hundred warehouses, or a healthcare system monitoring utility spend across dozens of facilities, still needs that data somewhere, and waiting on an API that most utilities have no roadmap to build isn’t a plan. Deck solves this by automating the utility’s own customer portal directly, logging in and reading the same usage and billing information a person would see on screen, structured into JSON through Deck’s own API.
There are a few real ways teams get utility data out of a system that wasn’t built to hand it over, and they aren’t interchangeable. Picking the wrong one for a given provider means either overbuilding for a feed that isn’t coming or underbuilding for a redesign that will eventually break it.
What Are the Ways to Get Utility Data Without an API?
- Manual retrieval. Someone logs in, checks usage, downloads the bill. Works fine for a handful of accounts, doesn’t scale past that.
- Green Button, where a utility supports it. A small number of large investor-owned utilities expose usage data through this standardized feed. Coverage stops at whichever utilities chose to implement it, and it doesn’t cover billing status or payment.
- Custom scripts against a specific portal. Works until the utility changes its layout, then breaks until someone rebuilds it. The maintenance cost scales with the number of providers automated, not the number of accounts.
- Browser automation. Deck logs into the portal directly and extracts structured data the same way a person reading the screen would, without depending on the utility supporting Green Button or exposing anything else.
Deck is a computer use agent platform that automates workflows by operating any web interface directly, so the target utility never has to expose an API for it to work. Deck’s agents read the page visually rather than matching a fixed selector, so a redesigned billing page doesn’t take the extraction down the way it would a hardcoded script.
Why Does the Method Matter at Scale?
A company with utility accounts spread across a hundred facilities is going to find a mix: a handful of large providers might support Green Button, most won’t. Building only against Green Button means permanent gaps for every utility that hasn’t adopted it, which is most of them outside a few large metro areas. Custom scripts close some of that gap, but every provider added is another script to maintain, and utility portals change often enough that maintenance becomes a standing job rather than a one-time build.
Manual retrieval doesn’t have either of those failure modes, but it doesn’t scale. A person checking a hundred utility portals by hand every billing cycle is doing a full-time job that grows every time a new facility gets added. Deck removes the coverage ceiling because it isn’t waiting on a data-sharing standard the provider may never adopt, and it removes the maintenance burden because the extraction adapts to layout changes instead of breaking on them.
What Does This Look Like in Practice?
A healthcare system operating 45 clinic locations across six states needed monthly electricity and gas usage data to track facility operating costs. Three of the larger providers supported Green Button. The other 30-plus were smaller regional and municipal utilities with no data-sharing option of any kind, which meant a facilities coordinator manually logging into each portal every month to record usage figures, a process that took roughly a week and a half of staff time per reporting cycle.
With Deck automating the remaining providers directly, all 45 locations feed into the same reporting pipeline regardless of which utility serves them. The monthly data pull that took a week and a half of manual work now runs unattended, with the coordinator reviewing exceptions instead of collecting raw numbers by hand.
FAQs
Does Deck work alongside Green Button where a utility already supports it?
Yes. Green Button and Deck aren’t mutually exclusive. A team can rely on Green Button for the utilities that support it and use Deck for every provider that doesn’t, which in practice is most of them.
Is Deck a replacement for a custom scraper built against a specific utility portal?
In most cases, yes. A custom script tied to one layout breaks the first time that layout changes. Deck’s agents read the page visually, which holds up against the kind of redesign that takes down a hardcoded script.
What kind of utility data can Deck extract?
Usage figures, billing amounts, due dates, and account status, whether that information sits directly on a page or is locked inside a downloadable PDF bill.
How long does it take to add a new, uncovered utility provider?
Adding a single provider typically takes days, since it follows the same authenticate-navigate-extract pattern Deck already uses for every other provider.
Ready to get started?
See how Deck can connect your product to any system — no APIs needed.
Build my Agent →