Path Robotics
Path Robotics is a Columbus, Ohio autonomous welding robotics company founded in 2018 by brothers Andy and Alex Lonsberry (CEO and CTO) out of Case Western Reserve University. The company builds AI-powered intelligent welding cells that automate metal fabrication for defense shipyards, utility and energy infrastructure, data centers, and heavy industry. Its core technology is Obsidian, a physical-AI reinforcement-learning agent trained inside Path's proprietary Weld World Model on tens of millions of welded inches; Obsidian runs at the edge of each cell and makes real-time, seam-by-seam welding decisions using a sensor stack of two cameras plus four lasers that deliver sub-millimeter 360-degree awareness around the torch. Path markets the cells with a CapEx-free consumption model and reports 97%+ first-pass yield, 4x productivity, and 30% lower welding costs across customers including HII (America's largest military shipbuilder), Saronic, LAD Services, Tycrop, Mine Rite Technologies, and Millerbernd. In April 2026 Path announced Rove, a mobile welding system mounted on a quadruped platform, extending its addressable geometry beyond fixed-cell applications. The company has raised approximately $271M across Seed through Series D from Drive Capital, Matter Venture Partners, Tiger Global, Addition, and Yamaha Motor Ventures, with the most recent $100M Series D closing in October 2024. Path Robotics has no public developer API, SDK, or webhook surface; its GitHub organization contains roughly 50 repositories that are almost entirely upstream open-source forks (ROS, protobuf, abseil, ceres-solver, pytorch3d, etc.) used as internal build dependencies rather than published developer artifacts. Revenue is earned through welding-cell deployments, services, and the consumable weld-output model — not API monetization.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Path Robotics the way a machine reads it — 2 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Path Robotics scores 11.2/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Path Robotics
Each block below is one kind of artifact we hold for Path Robotics. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Path Robotics Context
JSON-LDSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Path Robotics — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 6
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/path-robotics · machine-readable index on apis.io