Implement Green Button (ESPI) asynchronous notification callbacks so a DataCustodian pushes new usage data instead of being polled
domain: greenbuttonalliance.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register a thirdPartyNotifyUri as part of your ApplicationInformation resource with the DataCustodian
Have the DataCustodian POST an Atom feed entry to that URI when new interval data becomes available for a subscription
Parse the notification payload to identify which UsagePoint or subscription changed
Issue an authenticated GET back to the DataCustodian's referenced resource endpoint to retrieve the actual updated data
Handle retries and duplicate deliveries, since notification delivery is not guaranteed exactly-once
Known gotchas
The push notification is only a pointer/trigger, not the data itself — your third-party application still must pull the referenced resource using its access token
Not all utility DataCustodian implementations support outbound notifications, so a polling fallback is often required even when notifications are configured
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?