Recipes

Cross-domain plays you can wire.

A recipe is a reference pattern: a signal, a proposed response, the policy and human review around it, and the record a supported deployment should keep. Public feeds may be live; the building actions shown here are illustrative.

Weather × Facilities reviewLive public signal
Your facilities plan should know the weather.

A non-production pattern for using NWS and NOAA alerts in a human-reviewed facilities response. Fire, egress, and life-safety systems remain independent and authoritative.

View recipe →
Grid × HVAC
Your building should know the grid.

An illustrative pattern for using grid-price and demand-response signals in a bounded, human-reviewed HVAC proposal.

View recipe →
Air quality × Ventilation
Your HVAC should know the air outside.

An illustrative pattern for using air-quality context in a bounded, human-reviewed ventilation proposal.

View recipe →
Seismic × Emergency awarenessLive public signal
Your emergency plan should know the ground.

A non-production pattern for using the public USGS feed in a human-reviewed emergency checklist. Elevators, gas, access, and life-safety systems remain independent and authoritative.

View recipe →
What recipes are built from
Connector library

The systems that supply the signal

Every deployable recipe needs a verified connector and an explicit maturity state. Browse what is live and what requires managed early access.

Browse connectors → Agent library

The operators that run the play

A named operator proposes within a bounded role. Browse the live and early-access operator listings.

Browse agents → Loop builder

Wire your own play

Pick a signal, an action and an operator, and watch the loop run before you build it.

Open the tool →