Enroll and dispatch a fleet of DERs across multiple grid service programs using Leap's universal API
domain: developer.leap.energy · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review developer.leap.energy/docs for the account and device enrollment resources
Register device/meter identifiers against each grid services program the DER participates in
Use the universal dispatch resource to receive and acknowledge events without writing per-program integration logic
Pull performance and baseline data through Leap's metering endpoints for settlement verification
Use the interactive, in-browser API reference to validate request/response shapes before production integration
Known gotchas
The 'universal' API abstraction still requires mapping each underlying program's specific baseline and measurement rules — dispatch semantics like notification lead time and event duration differ by ISO/utility program even when the API shape looks uniform
Enrollment status and program eligibility can change independent of device telemetry, so poll enrollment state rather than assuming a device stays enrolled indefinitely
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?