Developer Platform
Parse pole files, run code-aligned analysis, and produce permit-ready findings — all over HTTP. The engineering logic lives in the API; you decide what to build on top.
Example
Pass a pole's attachment heights and voltage classes. Get back a GO-95 / NESC verdict per separation pair — pass, fail, and exactly how many inches of margin remain.
curl https://api.vertical.ai/v1/clearance/check \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"code": "GO95",
"district": 2,
"attachments": [
{ "label": "Primary 12kV", "height_ft": 34.5, "voltage_class": "primary" },
{ "label": "Neutral", "height_ft": 31.0, "voltage_class": "neutral" },
{ "label": "Comm bundle", "height_ft": 28.5, "voltage_class": "comm" }
]
}'{
"verdict": "FAIL",
"checks": [
{
"pair": "Neutral → Comm bundle",
"required_in": 40,
"actual_in": 30,
"margin_in": -10,
"rule": "GO-95 Table 1 Case 4",
"verdict": "FAIL"
},
{
"pair": "Primary 12kV → Neutral",
"required_in": 30,
"actual_in": 42,
"margin_in": 12,
"rule": "GO-95 Table 1 Case 4",
"verdict": "PASS"
}
]
}What you can build
The same APIs power completely different product types. These are applications we have built ourselves — each one is an example of a different integration pattern, not a product you're required to use.
Integration pattern: LLM with API tools
An LLM that calls our APIs as tools in response to natural-language requests. Engineers ask questions in plain English; the model decides which analyses to run and surfaces the findings as a structured reply.
Integration pattern: batch pipeline
Upload a SPIDA or O-Calc project; the pipeline fans out to every analyzer in parallel and returns a portfolio scorecard — per-pole verdicts, violation counts, and proposed fixes ranked by severity. No LLM in the loop.
Integration pattern: version-controlled workflow
A full supervisor UI where multiple engineers work on the same pole line concurrently — with branch, review, and merge semantics. Analysis results from the APIs are stored per version and diffed at merge time to classify data vs. engineering conflicts.
Integration pattern: geometry export + viewer
Export any pole to a USD or IFC scene and drop it into a field AR viewer, iTwin BIM platform, or Omniverse simulation. The pole model API drives the geometry; the clearance and sag APIs annotate it with analysis findings.
Architecture
Every overhead API reads and writes the Universal Pole Model — a normalized JSON document. Parsers produce it from source files; analyzers annotate it with findings; exporters write it back out. Chain as many stages as your workflow requires.
Parsers
Analyzers
Workflows
5+
File Parsers
SPIDA · PLS · O-Calc · ESRI
25+
REST APIs
parse · analyze · export
213
Agent Tools
overhead + underground MCP surface
175+
Test Files
covering engineering rules
API Surface
All overhead services accept a Universal Pole Model and return the same document enriched with findings, proposals, or computed fields.
CPUC GO-95 (Tables 1 & 2), NESC C2 (232, 235), and CSA C22.3 electrical clearance checks. Pole-level and midspan.
ReferenceCode-aligned grade, district, conductor tensions, sag temperatures, and published anchor-strength tables.
ReferenceTerrain-aware catenary with Google elevation ribbon. Per-conductor case-4 verdicts. Forecast-driven storm sweep.
ReferenceCircuit voltage, framing configuration (horizontal / triangular / deadend), guying validation.
ReferenceBatch orchestration — run every analyzer across an entire project in one job, get a portfolio scorecard.
ReferencePer-utility construction standards as a queryable rules library. Validate poles against utility-specific overlays.
ReferenceJP Form 2 rendering, FCC §1.1411 OTMR timeline, §224 attachment rates, make-ready scope bundles.
ReferenceMaterial, labor, and lifecycle cost estimates per pole. Drives BEAD per-payer cost-causation splits.
ReferencePortfolio-scale phased planning — group adjacent poles into projects, prioritize by code violation severity.
ReferenceThe underground domain operates on the Universal Vault Model. Six standalone calculator APIs are available in preview.
Neher-McGrath cable ampacity with soil, depth, and grouping corrections. Emergency overload ratings.
ReferenceICEA cable fault withstand, concentric neutral duty, and IEEE 1584 arc flash incident energy.
ReferenceNEC Chapter 9 fill percentage and three-cable jam detection (D/d 2.8–3.2 danger zone).
ReferenceSegment-by-segment pull tension through bends, sidewall pressure check, intermediate vault placement.
ReferenceCatalog selection (padmount + PMH switchgear), NEC 110.34 working space, bending radius.
ReferenceLayout optimization, multi-circuit derating, concrete encasement, trench dimensions.
ReferenceLive demos
These demos run entirely client-side with sample data — no API key required. They use the same physics the backend runs on real pole data.