Pricing
Pay for what you call.
No seats, no fixed domain tiers — one flat rate per Overhead function call, bundled pipelines for common workflows, and a flattened per-pole rate for field-capture partners. Team and Enterprise accounts trade metering for a minimum monthly commit. Request access to get current rates and a key.
Per call & pipelines
One rate per call, bundled workflows for less.
Done by hand, a routine compliance check runs $30–$350 in engineer time — not because it's hard, but because it's manual, repetitive, and someone still has to pull up the same table every time (BLS OEWS 2025 electrical-engineering labor rates, loaded for typical consulting overhead). Automating it doesn't replace that judgment — it clears the routine checks off your engineers' desks so their time goes to what actually needs a person: the borderline cases, the design tradeoffs, the conversations with the client. Some calls do more work under the hood than others — a multi-pole line solve isn't a single table lookup — but you're charged for the answer, not for our infrastructure.
Per call, metered
Every Overhead function — grade of construction, clearance, sag/tension, guying, grounding, vegetation, all 37 of them — same rate, no calculator.
Clearance Validation
The full clearance-walk suite on one pole or line section — ground/structure, conductor-to-conductor, span-to-span, and cross-line, whichever apply.
- ✓GO-95 or NESC Pole Clearance Walk
- ✓Span-to-Span Clearance
- ✓Cross-Line Clearance (where applicable)
Example response
{
"pole_id": "P-10432",
"clearance_status": "non_compliant",
"clearance_issues": [
{
"table": "Table 1",
"message": "Primary conductor below required ground clearance",
"attachment_ids": ["ATT-3"],
"actual": 17.8,
"required": 18.5
}
],
"table1_issue_count": 1,
"table2_issue_count": 0
}Clearance Validation + Failure Classification
Everything in Clearance Validation, plus classifying why a violation failed — deficit magnitude, likely cause, severity — not just a pass/fail number.
- ○Everything in Clearance Validation
- ○Failure classification (deficit, likely cause, severity) — real engineering work not yet built
Planned response shape (not yet real)
{
"pole_id": "P-10432",
"clearance_status": "non_compliant",
"clearance_issues": [ /* ...same as Clearance Validation... */ ],
"failure_classification": {
"attachment_id": "ATT-3",
"deficit_ft": 0.7,
"likely_cause": "conductor sag underestimated at design temperature",
"severity": "moderate"
}
}Clearance Validation + Failure Classification + Remediation Proposals
Everything above, plus a proposed fix for each real violation — a raised attachment, a guy set at a bearing, a corrected span — not just a diagnosis.
- ○Everything in Failure Classification
- ○Remediation proposals (specific, actionable fixes) — real engineering work not yet built
Planned response shape (not yet real)
{
"pole_id": "P-10432",
"clearance_status": "non_compliant",
"clearance_issues": [ /* ... */ ],
"failure_classification": { /* ...same as above... */ },
"remediation_proposals": [
{
"attachment_id": "ATT-3",
"action": "raise_attachment",
"target_height_ft": 18.6,
"estimated_cost_class": "low"
}
]
}Per pole, streamlined
Field Capture Partners
Drone-collection ingestion, circuit + framing classification, load-case verification, and Clearance Validation — the baseline compliance bundle, one flat per-pole rate instead of five metered calls. Volume discounts scale with your annual pole count.
| Tier 1 | Up to 10,000 poles/yr |
| Tier 2 | 10,000 – 49,999 poles/yr |
| Tier 3 | 50,000 – 249,999 poles/yr |
| Tier 4 | 250,000+ poles/yr |
Team / Enterprise
A minimum monthly commit drawn down against metered usage, instead of tracking every call — for teams that want predictable billing without giving up the per-call model.
- ✓Minimum monthly commit, drawn down against metered usage — no per-call bookkeeping
- ✓Volume discounts on per-call, per-pole, and pipeline rates at scale
- ✓Early access to roadmap domains and pipelines before general availability
How access works
Every key is scoped to exactly the jurisdictions it's calling — NESC, GO-95, or CSA, or all three. A key is issued to one purchasing organization — engineering firms working across multiple utility clients should talk to us about a Team/Enterprise agreement rather than sharing one key across them.
Want more than the API?
Any of this can also come as a harness — the same API and scope, plus a real MCP toolset you can point your own agent at, or have us build and deploy a chat interface for you. Same key either way.