Obtain API credentials (client ID and client secret) from Arcadia's developer portal; exchange them for an access token via the OAuth 2.0 client credentials flow at the token endpoint.
Initiate a user credential or OAuth-based utility connection for a customer by calling the credentials or OAuth link endpoints, directing the customer to authorize data access with their utility.
Once connected, retrieve the list of utility accounts for the customer via GET /accounts, then fetch statement (bill) data for a specific account using the statements endpoint.
Pull interval meter data via the intervals endpoint for a given account, specifying date range parameters to bound the query.
Handle pagination in responses using the cursor or page tokens returned in the response envelope, and subscribe to webhooks for new statement or interval data events to avoid polling.
Known gotchas
Arcadia's coverage and data latency vary by utility; some utilities deliver data in near-real-time while others batch-deliver days after the billing period ends — build retry and backfill logic rather than assuming timely delivery.
Access tokens have a short expiry; failing to implement token refresh logic causes intermittent 401 errors in long-running pipelines — always check token expiry and refresh proactively.
Interval data gaps are common when a utility's data collection system has outages or when a customer switches rate plans; treat missing intervals as expected rather than exceptional conditions and document gap-filling strategies.
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