Build an OpenADR 3.0 VEN client that subscribes to program events and submits usage reports
domain: openadr.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Model interactions around the four core OpenADR 3.0 objects: Program, Event, Report, and Subscription
As a VEN, create a Subscription so the VTN can push notifications via webhook or message queue rather than requiring continuous polling
Read active Events under a Program to determine required load-shed or shift actions
Submit Reports back to the VTN to share energy usage/telemetry data tied to a given Event or Program
Use the OpenADR 3.0 RESTful create/read/update/delete operations exposed for these primary objects per the openadr3 specification
Known gotchas
OpenADR 3.0 is a RESTful API, a significant architectural change from OpenADR 2.0b's SOAP-based web service; 2.0b VEN/VTN code is not directly portable
Subscriptions support both webhook push and message-queue delivery models; pick the one your infrastructure can reliably receive
Confirm which minor version (e.g. 3.0.0 vs 3.1.0) a given VTN implementation targets, since the spec has continued to evolve
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?