Vertical AI · Overhead Line Compliance API

A cited answer, not a plausible one.

Real, typed compliance and engineering-compute functions for overhead electric distribution — grade-of-construction, clearance, sag/tension, insulator uplift, guying, grounding, all grounded in NESC, GO-95, and CSA C22.3, not a language model guessing at a code minimum.

quickstart.py
# pip install vertical-ai-sdk
from vertical_ai_sdk import Client

client = Client(api_key="vaico_live_...")

result = client.overhead.nesc.grade(...)
# -> GradeResult(grade="B", rule_refs=["NESC Rule 242"], ...)
Grounded inNESCGO-95CSA C22.3

What we offer today

Overhead line compliance, in full — grade of construction, clearance, sag/tension, guying, and grounding, cited against NESC, GO-95, and CSA C22.3.

Overhead Line

Live

Distribution & transmission line compliance -- grade-of-construction, clearance (including cross-line and span-to-span), conductor sag/tension, insulator uplift, guying, pole setting-depth, grounding, vegetation.

NESCGO-95CSA C22.3 No.1

On the roadmap — not yet available

SubstationGeneration / DER InterconnectionBuilding ElectricalCircuit / GroundingAccessibilityBESSTransmission StructureThermalDatacenter ControlsAI-Factory Equipment DataUndergroundField CaptureLine SitingO-CalcSPIDAcalcPLS-POLE
See the full Overhead function list →

Python SDK

Your own standards, layered on top — without your data ever leaving your infrastructure.

Generic physics and cited regulatory minimums stay server-side, behind the API. A utility's own proprietary thresholds, framing catalogs, and margin policies run entirely client-side through StandardsPack — your own subclass, your own data, never transmitted anywhere.

Read the SDK docs →
standards.py
class AcmeUtilityStandards(OverheadStandardsPack):
    def classify_clearance(self, code_result):
        # our own +2ft margin over NESC's minimum
        return code_result.required + 2.0

Harnesses

A working starting point, not just raw API calls.

MCP toolset

Every function in a domain, exposed as a tool over the open MCP protocol — point Claude, Claude Code, or your own agent at it directly.

Self-serve

Build it yourself

Connect any MCP client, customize with the SDK — no separate onboarding.

Assisted

Or we build it for you

A real chat interface, deployed and wired to your equipment and workflows.

See how harnesses work →

Get a working API key in minutes.

Metered per call, or flattened to one price per pole for field-capture partners — no fixed domain tiers to pick between.

View pricing