Get started with GridWonk
Set up your account, choose a workspace, and prepare an interconnection packet.
GridWonk helps you research utility requirements, prepare application packets, and review cited findings. Public help is available without an account. Your organization's files and reviews require sign-in and current access.
Choose your path
| You are | Start here |
|---|---|
| A developer preparing a packet | Create a developer workspace, then use the developer guide |
| A utility representative | Submit an affiliation claim, then use the utility guide after verification |
| Joining an existing team | Accept your own invitation, verify your email, and complete legal acceptance |
| Using an AI client | Complete workspace setup, then connect the public plugin when available |
| Maintaining an approved integration | Use the API authentication guide and your organization's assigned credentials |
Your first review
- Select the utility, state, and program relevant to your project.
- Read the published requirements and check that automated packet review is supported.
- Create a private project and upload supported files through packet intake.
- Make any document-role or other human confirmations in the website.
- Start an eligible review and follow its status. Read findings with their source citations.
- Correct your packet. Submit only when you are ready and the utility accepts that workflow.
Private review does not send a package to the utility. Formal submission is a separate human action. Review findings do not establish utility approval or a guarantee of interconnection.
Eligible new workspaces have a bounded trial. Preprocessing uses processing allowance, and an unavailable provider or exhausted limit may block a new run. Existing authorized results remain readable.
Files and connections
Use the current packet upload flow. It accepts supported files up to 30 MiB each, with up to 12 files and 120 MiB per batch; additional file-type and page limits apply. The retired inline base64 upload endpoint is not a supported alternative. See upload help.
The public plugin signs you in and asks you to confirm one workspace. When App connected appears, return to the plugin; the confirmation link cannot be reused. Do not share API keys, passwords, or tokens in a conversation. Connected apps shows how to review and revoke its access. Purchases and human decisions stay on the website.
If signup or the public plugin is not yet available, use the access contact shown by the app. Existing partners can continue their authorized integration workflow. See the Help Center for account, packet, and support guides.
Bot Detection on OAuth
GridWonk can block OAuth browser login from cloud provider IP ranges (AWS, GCP, Azure) when the request also has a programmatic User-Agent or other bot signals. Approved server-to-server integrations should use API key authentication instead of browser-based OAuth. Public plugin users should complete sign-in in their own browser; never paste an integration key into a chat. If a normal browser is blocked, contact support. Forwarded IP headers cannot bypass these checks.