Register for a WebSupervisor account and locate the ComAp-Key subscription key in your profile at portal.websupervisor.net
Review the API reference at ComAp's Cloud API developer portal (comap-websupervisor.developer.azure-api.net)
Use the ComAp-Key plus client_id/client_secret to obtain an OAuth-style bearer token before calling data endpoints
Call endpoints to pull actual/historical values per device, and use the documented control commands (start, stop, faultReset, changeMcb, changeGcb, changeMode) if remote control access is authorized
Optionally use the community-maintained 'comap' Python package (PyPI) as a wrapper around the raw REST calls
Known gotchas
The Cloud API is separate from an on-prem/local WebSupervisor deployment — confirm which one a given site actually runs before assuming cloud endpoints apply
Control commands (start/stop/etc.) are higher-privilege than read-only telemetry — expect stricter authorization scopes for those calls
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?