AEC software teams can add solar radiation simulation through the infrared.city API or its Python and TypeScript SDKs. Infrared Core computes incident solar energy on ground, facade and roof surfaces. Your application can display those values beside the design geometry.
Start with the decision your user needs
A common question is how to put climate analysis inside an existing product. For a solar feature, start with a specific decision: which building surfaces need closer review before the design advances?
Define the study boundary and analysis period before you design the result viewer. Decide whether users need ground exposure, facade values or roof values. The Simulation library describes these outputs and their inputs.
Keep the feature label precise. Solar radiation reports incident energy in kWh/m². It does not report photovoltaic yield or indoor daylight. Do not present the result as either of those measures.
Compare building forms by surface solar energy
Consider an AEC application that compares alternative building forms on a development site. Run solar radiation for each option across the site and its surrounding building context. Use a selected summer month from the same weather file for every option.
Resolve facade and roof results on the building surface meshes. Keep the actual roof slopes and facade geometry in the scene. Include the relevant trees and shade structures. The radiation method uses direct and diffuse weather radiation, ray-traced shade and sky exposure, and facade material reflections.
Return surface energy values in kWh/m². The software team can show a coloured building view with values available when a user selects a surface. An architect or facade engineer can then identify exposed surfaces and choose where to investigate shading changes.
The API and SDK provide the integration route today. Keep the geometry, weather source and period attached to each saved result. Hold those inputs constant when comparing design options.
Separate computation from product behaviour
Your team still needs to define the user workflow. Specify how users select surfaces, start a run and read the result. Show the units and period beside the colour scale.
Keep the API key on the server. The API page includes secure backend recipes for applications with multiple users.
The Climate in your product route puts sun results inside your interface. The Platforms and software page covers adding simulation to an existing product or building an application on the API. Start with a solar workflow whose output answers a clear design question.
Sources
- infrared.city validation , accessed 31 Oct 2026.