Register the VEN (Virtual End Node) in Concerto's administration interface; obtain the VTN URL, VEN ID, and registration ID from the Concerto platform configuration
Implement the OpenADR 2.0b VEN using mutual TLS; send an oadrCreatePartyRegistration request to the VTN, confirm with oadrCreatedPartyRegistration containing the registrationID
Subscribe to EiEvent signals: poll the VTN's oadrRequestEvent endpoint or configure push delivery; parse the EiEventSignal for signalType LOAD_DISPATCH with payload units in kW
Apply the dispatch command to the battery fleet management system; send oadrCreatedEvent with eventResponses status OPTED_IN within the dtstart window
Configure the REST telemetry push: register a webhook URL in Concerto's integration settings to receive per-device state-of-charge, active power (kW), and availability payloads in JSON
Validate end-to-end by triggering a test event in the Concerto UI and confirming the VEN acknowledges and the webhook receives a telemetry payload within 60 seconds
Known gotchas
Concerto uses OAuth 2.0 client credentials for its REST API and separate mutual TLS certificates for the OpenADR VTN; these are provisioned independently and mixing up credentials causes 401 on the REST side or TLS handshake failure on the OpenADR side
OpenADR 2.0b EiEvent signals use ISO 8601 duration strings (e.g., PT30M) for event duration; parsing them as seconds directly will schedule 30-second events instead of 30-minute ones
The Concerto platform runs on AWS and applies a 30-second timeout on webhook deliveries; VEN endpoints that take longer than this will be marked as unreachable and events will not be re-delivered
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