GridWonk finds what each utility requires for interconnection, screens application packets against those requirements, and pinpoints deficiencies before they cost a review cycle. This page describes what the documentation covers.
The documentation itself requires an account.
Six areas cover the platform end to end, from role-based onboarding to the API. Every approved account sees all of it.
Role-based onboarding for project developers, utility reviewers, and engineering consultants, plus a shared platform overview.
Console workflows end to end: files, documents, requirements, packets, screening, notices, analytics, settings, and access grants.
The API: authentication, error contracts, async jobs, projects, documents, packets, utilities, requirements, webhooks, keys, and usage.
Claude Code and Codex setup, chatbot channels, PowerClerk, MCP servers, the command-line interface, and webhooks.
Interconnection and platform vocabulary, from interconnection level and tariff to readiness score.
A curated ledger of what shipped and when, written for people evaluating the platform rather than for release tooling.
GridWonk serves three roles in one platform, and the guides differ by what each role owns.
You own applicant preparation. The guides cover creating a project, uploading and confirming working-file roles, running the applicant packet check where it is supported, responding to a utility notice, and resubmitting.
You own the review queue. The guides cover batch intake, the four-stage screening pipeline, readiness scoring, the deficiency notice lifecycle, and resubmission review.
You work through an explicit access grant from a client organization. The guides cover multi-client setup, team roles, scoped cross-organization access, and reporting.
GridWonk takes on the work that slows interconnection down: finding what each utility actually requires, checking applications against it, and turning what is wrong into something fixable.
Follow each utility's published interconnection procedures and the requirements drawn from them, kept current as utilities revise their documents.
Check a complete application packet against the utility's current requirements — before it is submitted, or as it lands in the review queue.
See each finding located inside the actual PDF, with page references and a citation to the utility procedure text it comes from.
Turn findings into scorecards, annotated reports, and deficiency notices ready to send.
Correct a flagged submission in a working copy, export the corrected bundle, and resubmit.
Get answers about findings, requirements, and next steps, with citations back to the source documents.
The platform is technology-neutral: solar, wind, storage, gas, hydro, nuclear, coal, hybrid, and large-load projects all move through the same process.
The full documentation set is available to approved accounts.
Tell us who you are and what you are working on.
Request AccessAlready have an account? Log in to read the docs.
This site supports content negotiation. Request any public marketing page with an Accept: text/markdown header to receive lightweight markdown instead of HTML. The public product index lives at /llms.txt. The documentation itself stays behind the login.
curl -H "Accept: text/markdown" https://gridwonk.com/docs