# GridWonk Platform > AI review for interconnection applications. > GridWonk finds what each utility requires, checks complete application packets (documents and CAD drawings) against those requirements, and reports deficiencies with citations before they cost a review cycle. > URL: https://gridwonk.com ## Agent-Friendly Content This site supports content negotiation. Request any marketing page with `Accept: text/markdown` to receive lightweight markdown instead of HTML. Example: ``` curl -H "Accept: text/markdown" https://gridwonk.com/about ``` ## Pages - [Home](https://gridwonk.com/) - [Company](https://gridwonk.com/about) - [Developers](https://gridwonk.com/developers) - [Contact](https://gridwonk.com/contact) - [Documentation](https://gridwonk.com/docs) - [Privacy Policy](https://gridwonk.com/privacy) - [Terms of Service](https://gridwonk.com/terms) ## When to use GridWonk Use this platform when an approved partner needs to screen an interconnection application packet, automate packet intake, monitor document processing, start a packet review, or retrieve cited workflow results. Do not use it to infer utility approval, guess identifiers, bypass organization boundaries, or make a human-only document-role decision. Ask a human before starting paid or consequential write operations. ## Authenticated Resources The following content and execution surfaces require authentication: - **Developer Documentation** — Full platform documentation available at https://docs.gridwonk.com (requires login) - **API execution** — Curated partner packet operations require an explicitly scoped OAuth token; broader API operations may accept an organization API key or scope-less OAuth token - **MCP execution** — Hosted Model Context Protocol tools require the same approved partner access - **Complete API specification** — The broader /api/v1/openapi.json document requires a machine credential Request access: https://gridwonk.com/contact ## Agent Integration API and MCP discovery documents require credentials. Partners retrieve the complete OpenAPI document from /api/v1/openapi.json with an organization API key or scope-less OAuth token; the docs-host discovery documents require an authenticated browser session. Recommended sequence: read this file, request access, retrieve the OpenAPI document with your credential, select a stable operationId, request only the required OAuth scope, validate every input, and honor Retry-After with bounded polling. - [Developer and agent guide](https://gridwonk.com/developers) - [Hosted MCP endpoint](https://gridwonk.com/api/v1/mcp) — authenticated execution - [Contact and access requests](https://gridwonk.com/contact) - [Sitemap](https://gridwonk.com/sitemap.xml) - [Robots.txt](https://gridwonk.com/robots.txt) --- ## Full Page Content # GridWonk Platform > AI review for interconnection applications. GridWonk finds what each utility requires, checks complete application packets (documents and CAD drawings) against those requirements, and reports deficiencies with citations before they cost a review cycle. **URL**: https://gridwonk.com --- ## Application packets are still reviewed manually Utilities are on the clock to respond to each application: queues keep growing, review teams don't, and every withdrawal can send the applications behind it back for another review. Finding the deficiencies by hand is where the time goes: - **Incomplete packets** — A packet missing required documents bounces back. Each round trip costs the developer weeks and puts the same application in front of the utility again. - **Documents that disagree** — The application says one system size; the single-line shows another. Catching the mismatch means cross-checking every document in the packet against the rest. - **Requirements scattered across documents** — What applies to a packet is spread across utility, state, and federal documents, and some requirements are only implied by the application form. Working out which apply to each document is a job in itself. --- ## How Packet Screening Works With GridWonk, the whole packet is checked against that utility's own requirements: missing documents, cross-document mismatches, single-line deficiencies, and site-control issues are flagged before the packet is submitted, or before it reaches an engineer's desk. 1. **Application packet** — Application forms, site control, single-line diagrams, supporting docs. 2. **AI packet screening** — Document completeness, cross-document consistency, single-line diagram, and site control, checked against the utility's own requirements. 3. **Before review** — Deficiencies cited to the utility's procedures, ready to fix before submission or to turn into a deficiency notice. --- ## Who It's For Three roles, one shared review. Everyone works from the same requirements and the same findings. - **Utility interconnection engineers** — Clear application queues faster with more complete reviews. GridWonk identifies deficiencies against your requirements, giving you findings to quickly review, edit, and turn into deficiency notices. - **Project developers** — Submit a clean packet the first time. GridWonk checks your application against the utility's requirements so you can fix deficiencies, recheck, and submit only when your packet is ready for utility review. - **Interconnection consultants** — Deliver better interconnection reviews at scale. Work across client projects through explicit access grants, accelerate application preparation and review, and deliver more complete, actionable results to developers and utilities. --- ## Deficiencies, located on the drawing Upload the CAD drawing (DWG) of your site plan and GridWonk reads the engineering evidence inside it (layers, layouts, coordinate systems, external references). Drawings are checked against the application itself: the address, the equipment, the system size, the point of interconnection. Findings land on the drawing, where an engineer can confirm them. --- ## How It Works 1. **Upload the packet** — Application form, single-line diagram, site plan, site control. 2. **Check against the requirements** — GridWonk checks the packet against the utility's current published requirements, not a generic checklist. 3. **Locate the deficiencies** — GridWonk pinpoints each finding on the page or drawing it comes from, with a citation to the supporting procedure text. 4. **Review the results** — Review scorecards, annotated reports, and detailed findings. Fix issues and re-run the check, or turn the findings into a deficiency notice. --- ## Integrate With Your Existing Systems Bring GridWonk's interconnection review capabilities into your applications, workflows, and AI tools. - **API** — Create projects, upload documents, run reviews, and retrieve findings programmatically. - **MCP server & CLI** — Run GridWonk reviews from AI assistants, developer tools, and the command line. - **Webhooks** — Get notified when reviews complete or processing status changes, without polling. More on the developer platform: https://gridwonk.com/developers --- ## Data Security & Privacy Your data remains confidential, isolated, and under your organization's control. - **Data isolation** — Each organization's data is logically isolated. Access to another organization's data requires explicit, revocable authorization. - **No training on your data** — Your documents, project data, and review results are not used to train AI models. - **Transparent, reviewable results** — Findings cite the applicable utility requirement, are advisory, and remain subject to human review. --- ## Frequently Asked Questions ### What does GridWonk do? GridWonk reviews utility interconnection application packets against each utility's current requirements, identifies deficiencies, and provides findings with citations to the applicable utility procedures. ### Which utilities are supported? GridWonk supports 1,329+ utilities with EIA-assigned utility IDs. Utility-specific requirements coverage depends on the published documents GridWonk has processed and reviewed. ### How is my data handled? Each organization's data is isolated from every other organization's. Your data is not used to train AI models. Findings are advisory and always subject to human review. ### Can my organization get access? GridWonk is working with utilities and project developers today. Email contact@gridwonk.com to discuss getting your organization set up, and tell us what you are working on. ### Can I integrate GridWonk with my own tools? Yes. GridWonk has an API, an MCP server for AI assistants, a command-line interface, and webhooks. Documentation for each is available to approved accounts. --- ## Fewer review cycles, starting with the next packet Tell us who you are and what you are working on, and we'll set up access. - [Request Access](mailto:contact@gridwonk.com) - [Read the docs](https://gridwonk.com/docs) - [Company](https://gridwonk.com/about) (c) 2026 GridWonk --- # About GridWonk > GridWonk builds AI review for utility interconnection applications: finding what each utility requires and catching deficiencies before they cost a review cycle. **URL**: https://gridwonk.com/about --- ## Our Mission - **Reduce delays** — Cut the review cycles caused by deficient interconnection applications. - **Make requirements findable** — Surface what each utility actually requires, from the utility's own published procedures. - **Serve both sides of the queue** — Give utilities and developers the same view of the same requirements and findings. --- ## The Problem At many interconnection authorities, most interconnection applications arrive deficient, and the labor of getting applications to acceptability is a heavy drag on how fast new generation and large loads connect to the grid. The bottleneck isn't just volume; it's that every check spans the whole packet: - Site control documentation - Interconnection application forms - Engineering drawings and single-line diagrams - Formatting and completeness requirements - Utility-specific tariff and procedure compliance Manual review is slow, inconsistent, and expensive. Developers often submit incomplete applications simply because they don't know what's required, and utility review teams absorb the difference. --- ## What GridWonk Does GridWonk keeps track of each utility's published interconnection procedures and the requirements drawn from them, then checks complete application packets (documents and native CAD drawings) against those requirements. Findings come back located on the page or drawing they refer to, with a citation to the procedure text behind them, and flow into reports, deficiency notices, and a fix-and-resubmit workflow. Findings are advisory and built to be checked: every one cites its source, and a person always makes the call. The platform is technology-neutral: solar, wind, storage, gas, hydro, nuclear, coal, hybrid, and large-load projects all move through the same process. --- ## Founders GridWonk was founded by a team that has built and shipped at scale. ### James Lancelot — Chief Executive Officer 12 years at Google leading analytics and technology partnerships, with investment and advisory work across climate tech. ### Dr. Han Wen — Chief Technology Officer PhD in Physics from Stanford University, with a track record of turning conceptual ideas into shipped products across multiple industries. The team's earlier recognition includes the Google for Startups AI Program. --- ## Get in Touch Tell us whether you develop projects, review applications at a utility, or consult across both, and what you are working on. - [Contact Us](mailto:contact@gridwonk.com) - [Read the docs](https://gridwonk.com/docs) (c) 2026 GridWonk --- # Developers > Build on GridWonk: an API, an MCP server for AI assistants, a command-line interface, and webhooks, all running the same interconnection review the console runs. **URL**: https://gridwonk.com/developers The interconnection review that runs in the console is the same one your systems can call: find what a utility requires, screen a packet against it, and read the findings back, from your own code or your own AI tools. Full API, MCP, CLI, and webhook documentation is available to approved accounts. --- ## Four Ways In Pick the surface that fits how you work. They all speak to the same platform and the same review. - **API** — Create projects, upload packet documents, run reviews, and retrieve findings and reports over HTTPS with JSON responses and typed error contracts. - **MCP server** — Connect Claude, or any MCP-capable assistant, to the platform's tools: match utilities, query published requirements, check job status, and run reviews from a conversation. - **CLI** — The same workflows from a terminal or a script: upload, review, and export without writing an integration first. - **Webhooks** — Subscribe to job and document events and get notified when work completes, instead of polling. --- ## Start With a Utility Most integrations begin the same way: resolve the utility you are working with to its canonical record, then everything else (requirements, reviews, findings) hangs off it. ```bash curl -X POST https://gridwonk.com/api/v1/utilities/match \ -H "Authorization: Bearer $API_KEY" \ -H "Content-Type: application/json" \ -d '{"name": "Duke Energy Carolinas", "state": "NC"}' ``` Authentication uses API keys created in the console, or an OAuth client-credentials exchange for partner integrations. Keys are scoped to your organization and can be rate-limited, restricted by endpoint, and revoked at any time. --- ## What You Can Build - Screen a packet automatically when it lands in your intake system, and route the findings to the right reviewer. - Keep your project tracker in step with review status through webhook events. - Let your team's AI assistant answer "what does this utility require?" with the platform's own requirement data. --- ## Data Security & Privacy The same rules as the console, on every surface. - **Organization isolation** — Each organization's data is separated from every other's. Consultants see a client's work only through an explicit, revocable access grant. - **No training on your data** — Your documents and results are never used to train AI models. - **Findings you can check** — Every finding cites the utility's own procedure text, is advisory, and is always subject to qualified human review. --- ## Get an API Key Access is invite-based today. Tell us what you are building and which utilities you work with. - [Request Access](mailto:contact@gridwonk.com) - [Log in to read the docs](https://docs.gridwonk.com) (c) 2026 GridWonk --- # Contact the Team Use this page to request platform access, discuss a developer integration, ask about a utility workflow, report an account problem, or explore a partnership. The team can help choose the appropriate starting point for a new organization or machine integration. ## Platform and integration access Email [contact@gridwonk.com](mailto:contact@gridwonk.com) for organization onboarding, REST API access, hosted MCP access, CLI distribution questions, utility integrations, consultant workflows, evaluations, or partnerships. Include your organization name, role, intended workflow, preferred integration surface, and whether the request is for evaluation or production. That context helps route the request without asking you to repeat sensitive details. The team will confirm the applicable organization boundary, scopes, environment, and rollout steps before creating a machine credential. ## Product and account support Email [support@gridwonk.com](mailto:support@gridwonk.com) for login trouble, an existing organization’s access, API or MCP errors, unexpected packet workflow state, billing questions, or a suspected service incident. Include the affected surface, approximate time and time zone, HTTP status or safe error code, and a request identifier when one is available. Do not email API keys, OAuth tokens, passwords, signed upload links, private customer documents, or raw interconnection packets. A request identifier and a description of the observed behavior are normally enough to begin diagnosis. The support team can provide a secure next step if additional evidence is required. ## Before contacting us - Read the [developer and agent guide](/developers) for discovery, OAuth scopes, safe retries, and the recommended agent sequence. - Read [agent instructions](/llms.txt) when configuring an automated crawler or tool-using agent. - Use the [platform documentation](/docs) for the human workflow and product concepts. For privacy requests, review the [Privacy Policy](/privacy) and use the contact method stated there. For contractual terms and acceptable use, review the [Terms of Service](/terms). --- # GridWonk Platform Documentation > Product, API, and integration documentation for GridWonk Platform: console workflows, the API, integrations, and an interconnection glossary. Request access to read the full set. **URL**: https://gridwonk.com/docs 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. --- ## What's Inside the Documentation Six areas cover the platform end to end, from role-based onboarding to the API. Every approved account sees all of it. - **Getting Started** — Role-based onboarding for project developers, utility reviewers, and engineering consultants, plus a shared platform overview. - **Help Center** — Console workflows end to end: files, documents, requirements, packets, screening, notices, analytics, settings, and access grants. - **API Reference** — The API: authentication, error contracts, async jobs, projects, documents, packets, utilities, requirements, webhooks, keys, and usage. - **Integrations** — Claude Code and Codex setup, chatbot channels, PowerClerk, MCP servers, the command-line interface, and webhooks. - **Glossary** — Interconnection and platform vocabulary, from interconnection level and tariff to readiness score. - **Changelog** — A curated ledger of what shipped and when, written for people evaluating the platform rather than for release tooling. --- ## Start Here by Role GridWonk serves three roles in one platform, and the guides differ by what each role owns. ### Project Developers 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. ### Utility Reviewers You own the review queue. The guides cover batch intake, the four-stage screening pipeline, readiness scoring, the deficiency notice lifecycle, and resubmission review. ### Engineering Consultants 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. --- ## What You Can Get Done 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. - **Track utility requirements** — Follow each utility's published interconnection procedures and the requirements drawn from them, kept current as utilities revise their documents. - **Screen application packets** — Check a complete application packet against the utility's current requirements — before it is submitted, or as it lands in the review queue. - **Pinpoint deficiencies** — See each finding located inside the actual PDF, with page references and a citation to the utility procedure text it comes from. - **Report and notify** — Turn findings into scorecards, annotated reports, and deficiency notices ready to send. - **Fix and resubmit** — Correct a flagged submission in a working copy, export the corrected bundle, and resubmit. - **Ask questions as you go** — 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. --- ## Request Access The full documentation set is available to approved accounts. Tell us who you are and what you are working on. - [Request Access](mailto:contact@gridwonk.com) — Tell us your role, organization, and what you are evaluating - [Log in to read the docs](https://docs.gridwonk.com) — For existing accounts --- ## For AI Agents This site supports content negotiation. Request any public marketing page with an `Accept: text/markdown` header to receive lightweight markdown instead of HTML. ``` curl -H "Accept: text/markdown" https://gridwonk.com/docs ``` - [llms.txt](/llms.txt) — Public site content as plain text for LLMs - The documentation itself, the API reference, and the MCP tool catalog require authentication. Contact us for access. (c) 2026 GridWonk --- # Privacy Policy > Last updated: September 17, 2026 (summary of Privacy Policy v2.3.0) **URL**: https://gridwonk.com/privacy > **This page is a plain-language summary for convenience.** The complete, binding Privacy > Policy (v2.3.0, effective September 17, 2026) is published at https://gridwonk.com/privacy and > governs in the event of any difference. GridWonk is the platform brand; the data controller / > processor entity is GridBoost, Inc., a Delaware corporation. --- ## 1. What We Collect Account information (name, email, organization, hashed credentials), the documents your organization uploads for interconnection review (Customer Data), and usage data (logs, metrics, telemetry) that is anonymized and aggregated so it identifies neither you nor your data. ## 2. How We Use It - To provide, maintain, and support the platform — processing your documents to generate deficiency findings and reports in real time. - To secure the service (authentication, audit logging, incident response). - To improve the platform using only aggregate, de-identified data. - **Never to train AI models on your data.** We explicitly prohibit the use of Customer Data for training, fine-tuning, or improving any AI model, whether operated by us or by a third-party model provider. Our AI providers process data under enterprise API terms that prohibit training on it and do not persistently store it beyond the API request. ## 3. Security AES-256 encryption at rest, TLS 1.2+ in transit, row-level security isolating each organization's data, role-based access control with MFA on administrative accounts, and tamper-resistant audit logging. ## 4. Sharing We do not sell personal information. Data is shared only with the infrastructure and AI sub-processors needed to run the service, each bound to protections at least as strong as ours, and as required by law. ## 5. Retention and Deletion After account or agreement termination: a 60-day export window, deletion from active systems within 90 days after that window, and purge from operational backups within a further 90 days. AI processing logs are deleted after 90 days; audit logs are kept 3 years. Confirmed breaches are reported to affected customers within 72 hours. ## 6. Your Rights You may access, correct, export, or delete your personal data, and opt out of non-essential communications. Contact [privacy@gridwonk.com](mailto:privacy@gridwonk.com); we respond within 30 days. CCPA/CPRA and other jurisdiction-specific rights are detailed in the full policy. The platform is not intended for users under 18. ## 7. Contact Email: [privacy@gridwonk.com](mailto:privacy@gridwonk.com) (c) 2026 GridBoost, Inc. GridWonk is the product brand of GridBoost, Inc. --- # Terms of Service > Last updated: September 17, 2026 (summary of Terms of Service v2.3.0) **URL**: https://gridwonk.com/terms > **This page is a plain-language summary for convenience.** The complete, binding Terms of > Service (v2.3.0, effective September 17, 2026) are published at https://gridwonk.com/terms and > govern in the event of any difference. GridWonk is the platform brand; the contracting entity > is GridBoost, Inc., a Delaware corporation. --- ## 1. The Agreement The Agreement is formed when you click "I Accept" when presented with the Terms, sign an order form referencing them, or use the Cloud Service. It incorporates the Privacy Policy, Acceptable Use Policy, and Data Processing Agreement. We give at least 30 days' notice of material changes. ## 2. The Service GridWonk provides AI-assisted screening and deficiency review of grid interconnection application packets for utilities, developers, and consultants, with multi-organization access controls and row-level data isolation. The platform works with real-world interconnection application materials — application forms, site-control documents, one-line diagrams, engineering studies, and supporting documents. ## 3. Your Data - **You own your data.** Customer Data — including interconnection applications and site control documents you upload — remains yours, and you own the AI outputs generated from it. - **We process it only to provide the service.** Our license to process Customer Data is limited to providing, maintaining, and supporting the Cloud Service, and it ends when your data is deleted. - **We never train AI models on your data.** Customer Data is processed only to generate outputs in real time. This prohibition extends by contract to our third-party AI model providers. Only anonymized, aggregated usage data (which contains no Customer Data) is used to improve the service. - **Retention and deletion.** After termination you have a 60-day window to export your data; it is then deleted from active systems within 90 days, with operational backups purged within a further 90 days. ## 4. AI Outputs AI outputs are advisory only — they are not legal advice, engineering certification, or a utility's official decision, and they require qualified human review before reliance. ## 5. Energy-Sector Terms Critical Energy/Electric Infrastructure Information (CEII) receives enhanced access controls and indefinite confidentiality. Information relating to interconnection applications, grid infrastructure, and utility operations is treated as Confidential Information. ## 6. Acceptable Use The Acceptable Use Policy (https://gridwonk.com/legal/aup) prohibits, among other things, unauthorized access attempts, bulk extraction, and using the service or its outputs to build or train competing models. ## 7. Warranties, Liability, Governing Law The full Terms set out warranties, disclaimers, liability caps, and dispute resolution. The Agreement is governed by Delaware law. ## 8. Contact Email: [contact@gridwonk.com](mailto:contact@gridwonk.com) (c) 2026 GridBoost, Inc. GridWonk is the product brand of GridBoost, Inc. ---