Integrations & Partners
Vertical AI ingests pole and vault data from the systems your customers already use, runs the engineering passes, and round-trips back. If you build one of those systems, let's shorten the distance between your tool and ours with a real connector.
Who we want to integrate with
We're picking off the integrations that move the most engineering work per connector. If your platform fits one of these categories, you're already on our roadmap — let's talk about pulling it forward.
iOS / Android tools that engineers and field crews use to photograph poles, capture framing, tag attachments, and log conditions. We parse the capture, you stay the system of record in the field.
Photogrammetry, LIDAR, and computer-vision platforms that derive pole geometry, attachment locations, and conductor catenaries from aerial imagery. We turn your point clouds into engineering decisions.
Pole loading analysis vendors. We round-trip files in and out of every major PLA tool and would love deeper hooks — direct project-level sync, headless analysis, or shared catalog management.
ArcGIS shipped. We also want connectors to QGIS, Hexagon, Cadcorp, and the open feature-layer ecosystem. If your platform stores poles, vaults, conduits, or circuits, there's a connector here.
Pole attachment management, joint-use coordination, NJUNS-style ticketing, and rate-card platforms. We already render NCJPA JP Form 2 — we want to plug into the systems where those forms live.
CMMS, EAM, and work-order systems. Push analysis findings, replacement priorities, and HITL fix proposals as work orders without the engineer leaving your tool.
Per-utility construction standards, code books, and compliance corpora. Our standards-RAG service ingests PDFs today; richer connectors to digitized rule libraries are next.
If you sell access to pole, conductor, soil, terrain, or weather datasets, we want them flowing into the loading and sag services without engineers stitching CSVs together.
What a connector looks like
No custom integration framework, no proprietary SDK to learn. The same patterns that make our APIs easy to call make connectors easy to build.
Plain REST endpoints. No proprietary RPC, no enterprise SOAP layer. If you can curl, you can integrate.
Connectors read and write the Universal Pole Model or Universal Vault Model. Once you're mapped, every downstream service speaks your language.
Connectors are exposed as MCP tools so the conversational agent can invoke your platform inside an engineering workflow without custom UI.
When a connector is ready we publish a launch post, a docs page, and a worked example. You get distribution, we get credibility for the integration.
Already shipping
These are in production right now. Every one is a working pattern we'd extend or replicate for the right partner.
| Partner / format | Description |
|---|---|
| SPIDAcalc | Parse + generate, multi-pole, voltage-aware wire chains |
| O-Calc | .pplx parse + generate |
| PLS-POLE / PLS-CADD | .pol parse with optional .loa context |
| Field capture data | Direct parse into Universal Pole Model from drone imagery and field-capture sources |
| ESRI ArcGIS | Feature-layer push, pull, and result sync (poles + attachments + conductors) |
| NCJPA | JP Form 2 PDF rendering, single-pole and replacement-pair |
| Pixar USD | USDA scene assembly with full component library |
| Anthropic Claude | Native tool-use loop driving the conversational agent |
| Vertex AI Agent Engine | Drop-in Gemini-backed alternative behind the same SSE contract |
Email a one-paragraph description of your platform and what your customers need from a Vertical AI integration. We'll come back with scope, timeline, and a co-marketing plan.