Authenticate to the PJM Data Miner 2 REST API at dataminer2.pjm.com using your registered account credentials; obtain a session token via POST /api/auth/login
Query the interconnection queue: GET /api/report/queue?fields=queueNumber,projectName,queueDate,studyPhase,capacityMW,fuelType,countyState and set pageSize=500 to paginate through all active projects
Filter the response for projects in the 'Transition Cycle 1' or 'Cycle 1' study phase (PJM completed Transition Cycle 1 studies in 2025); look for fuelType values that include STORAGE or SOLAR to identify DER-compatible projects
For each project of interest, retrieve the full queue detail: GET /api/report/queuedetail?queueNumber={id} to obtain the assigned POI, transmission owner, and estimated in-service date
Cross-reference the queue data against hosting capacity constraints by calling the PJM eData API for transmission facility loading at the candidate POI substations
Export the filtered queue as CSV for project pipeline tracking; schedule the pull to run weekly using a cron job to catch newly submitted applications (PJM accepts Cycle 1 applications through April 27, 2026)
Known gotchas
PJM Data Miner 2 rate-limits unauthenticated requests; the publicly browsable UI uses the same backend API but authenticated API calls have higher rate limits — always authenticate to avoid 429 errors on bulk pulls
The studyPhase field values changed when PJM transitioned to the FERC Order 2023 cluster process in 2024; legacy phase names like 'System Impact Study' no longer appear for new applications — use the new cluster cycle nomenclature
Queue data is updated nightly, not in real-time; a project that withdrew in the morning may still appear in the API response until the next nightly refresh
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