Use the EnergyHub Marketplace API to pre-enroll eligible customers; POST customer and device records with device_type, serial_number, and program_id fields to the enrollment endpoint
Authenticate vendor device data via the Mercury Edge Connect integration layer; configure the OEM cloud webhook to forward device state-of-charge, power, and availability telemetry to Mercury
Verify device eligibility by calling the GET /devices/{id}/eligibility endpoint and checking that the response status is 'ELIGIBLE' and baseline_kw is populated
Create a dispatch event via the Mercury DERMS event API: POST to /events with program_id, start_time, end_time, and target_kw fields; confirm the event status transitions to DISPATCHED
Monitor dispatch performance via GET /events/{event_id}/performance to retrieve device-level kW reduction and participation rate during the event window
Retrieve M&V results post-event from the Mercury reporting API to obtain measured versus baseline load reduction for settlement
Known gotchas
Mercury uses OpenADR 2.0b for some OEM integrations and proprietary REST for others; check the integration tier for each device OEM before assuming a single dispatch path works across a heterogeneous fleet
The baseline calculation window is typically set at the program level (e.g., 10-of-10 similar days); enrolling a device less than 10 days before a dispatch event results in no valid baseline and the device is excluded from the event
Device availability signals are advisory; Mercury will attempt dispatch regardless and mark non-responding devices as 'did not respond' rather than pre-filtering them — plan settlement logic accordingly
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp