- Building Insights: roof segments with pitch and azimuth, max panel count, yearly sunshine hours and energy per configuration
- Financial analyses by monthly bill, with savings and payback estimates where Google has utility data
- Data Layers: DSM, RGB, mask, annual and monthly flux rasters for a radius around a point
- Both routes read-only; imagery quality (HIGH/MEDIUM/LOW) returned so you know how much to trust the estimate
Google Solar API Connector
Google's Solar API — rooftop solar potential for a building from aerial imagery: usable roof area, segments, sunshine hours, panel layouts and financial estimates, plus per-building data layers — registered in Apivom Atlas for solar installers, energy and property tenants, with your own Maps Platform key.
What you can do
Use cases
- Instant pre-qualification for solar leads — Run Building Insights on a prospect's address to get usable roof area, panel count and yearly production before a site visit is booked.
- Proposal visuals from real roof data — Pull the data layers and panel layouts to render the proposed installation on the customer's actual roof in your quoting tool.
The Solar API on solar.googleapis.com models the solar potential of a specific building from Google's aerial imagery and elevation data. Building Insights, for a coordinate, returns the roof broken into segments with pitch, azimuth and area, the sunshine hours and the energy each possible panel configuration would produce over a year, carbon-offset figures and — where Google has local utility data — financial analyses per monthly bill with savings and payback. Data Layers returns the underlying rasters for a radius around a point: digital surface model, RGB imagery, building mask and annual and monthly solar flux, ready for your own visualisation or engineering tools. Apivom Atlas registers both read-only routes with the Maps Platform credential contract, per-tenant logging and the AI integration guide (llms.txt); your key, project and quotas apply. No Apivom product workflow uses solar data today — the connector is available to installers, energy retailers and property tenants who want to build on it, and a product flow is scoped per customer.
Your own Google Cloud API key (Maps Platform) with this API enabled on the project; the Apivom product sends it as the x-goog-api-key header on each call. Google bills the project that owns the key. The key is encrypted in your Iris tenant; Apivom Atlas stores nothing.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
Is every building covered?
No. Coverage depends on Google's high-resolution imagery; the response reports imagery quality (HIGH, MEDIUM, LOW) and buildings outside coverage return not-found. Financial figures appear only where Google has local utility-rate data.
Which Google Cloud project pays for the calls?
The project that owns the API key you connect. Enable this specific API on that project, restrict the key to the APIs you actually use, and Google's Maps Platform pricing and monthly credit apply to it directly — Apivom adds no charge and shows every call in your tenant's integration log.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.