Developer docs

Build with the Vertical AI engineering APIs. Conversational gateways for both agents, plus focused HTTP services for parsing, classification, loading, clearance, sag, ampacity, fault current, and more.

The platform is organized as a small set of HTTP services on top of two shared engineering models: the Universal Pole Model for overhead distribution and the Universal Vault Model for underground. Parsers produce these documents, analyzers consume them, and exporters write them back out into the source format. If you're integrating with more than one API, read the Universal Pole Model reference first — every overhead service speaks it.

Most teams start with one of the conversational gateways — they orchestrate the underlying tools for you — and drop down to the individual services when they need a single piece of behavior in a larger pipeline.

All services authenticate the same way (a bearer API key) and return JSON. The gateways stream Server-Sent Events so chat UIs can show tool calls and intermediate results as they arrive.

Get started

Getting started

What you can build, what you need (API key + base URL), a 30-second curl example.

Authentication

Bearer token header, where keys come from, scoping rules.

Universal Pole Model

The shared JSON document every overhead service speaks. Read this once and the rest of the docs become reference.

Overhead — parsers and on-ramps

Everything that turns a source file or capture into a Universal Pole Model.

SPIDA API

Parse SPIDAcalc payloads into UPM and generate SPIDA-compatible output. The most mature parser today.

PLS API

.frm-catalog-driven generation: parse .pol (+ optional .loa) into UPM; emit a .pls.zip bundle (POL + LOA + .cri + .wnd) that PLS-CADD imports with no missing-sidecar warnings.

O-Calc API

Parse O-Calc .pplx payloads into UPM. Catalog-free direct-writer generation through the format-bridge service handles 61/61 corpus files cleanly.

Field Capture API

Ingest drone, photogrammetry, LIDAR, and field-survey data into UPM. The on-ramp for everything that isn't a PLA file.

ESRI / ArcGIS API

Bidirectional ArcGIS sync — pull a polygon of poles in, push analyzed results back out.

Overhead — analyzers

Every analyzer accepts a UPM document and returns the same document with findings, proposals, or computed fields enriched.

Overhead gateway

Server-Sent Events chat that orchestrates the overhead tool catalog. Streams tool calls and outputs.

Clearance API

CPUC GO-95 + NESC C2 + midspan separation checks. Pole-level and span-level.

Loading API

Code-aligned grade, district, conductor tensions, sag temperatures, and the published anchor-strength check (discrete plate/PISA tables + non-PISA catalog + PISA chart).

Sag API

Static sag with terrain ribbon, per-conductor case-4 verdicts, and forecast-driven storm sweep (Tomorrow.io → NWS → Open-Meteo provider chain, jurisdiction-aware GO-95 vs NESC base).

Classification API

Circuit voltage, framing configuration, guying validation, midspan span-clearance.

Standards API

Per-utility construction standards as a queryable rules library. Ingest PDFs, validate poles against utility-specific rules.

QA/QC API

Batch orchestration — upload a project, run every analyzer across every pole, get per-pole loading + storm summaries (every pole, not just flagged ones) plus a portfolio-level scorecard.

Overhead tool catalog

Full MCP tool catalog across pole assembly, clearance, sag, ESRI, joint-use, USD, and more.

Overhead — workflows

Higher-level services that consume findings from the analyzers and produce documents, cost estimates, or portfolio plans.

Concurrent work orders

Git-style branch / review / merge for one physical pole. Analysis-aware merge classifies data vs engineering conflicts; a reviewer resolves by choosing one work order or adding a remediation so both fit, then advances the pole-of-record.

Joint-Use API

JP Form 2 rendering, FCC §1.1411 OTMR timeline, FCC §224 attachment rates, make-ready scope-of-work bundles.

Replacement Cost API

Material, labor, and lifecycle cost estimates per pole. Drives BEAD per-payer cost-causation splits.

Replacement Planning API

Portfolio-scale phased planning — group adjacent poles into projects, respect budget envelopes, prioritize the highest-value fixes.

Underground

Underground is split into a conversational gateway (live) and six standalone calculator APIs that are extracting from the underground agent over the next few releases. Preview pages describe what each will do.

Underground gateway

SSE chat that orchestrates the 68 underground tools. Vault, conduit, ampacity, fault current, network topology.

Ampacity API

Preview

Neher-McGrath cable ampacity with soil, depth, and grouping corrections. Preview.

Fault Current API

Preview

ICEA cable fault withstand, concentric neutral duty, and IEEE 1584 arc flash. Preview.

Conduit Fill API

Preview

NEC Chapter 9 conduit fill % and three-cable jam detection. Preview.

Pulling Tension API

Preview

Cable pulling tension through bends with intermediate vault placement. Preview.

Duct Bank API

Preview

Layout optimization, multi-circuit derating, concrete encasement, trench dimensions. Preview.

Vault Sizing API

Preview

Catalog selection, NEC 110.34 working space, bending radius, padmount clearances. Preview.

Underground tool catalog

68 MCP tools across vault, conduit, ampacity, fault current, duct bank, and conversion studies.

Need access?

API keys are issued per organization. Email hello@epcstudio.io with your team and intended use case and we'll get you a sandbox key.