Call Rhombus From Your Internal Tools, Like Any Other API

Rhombus + Claude Series — Tying Into the Enterprise

Every enterprise engineering team builds internal tools. Scripts that automate onboarding, dashboards that visualize operations, services that bridge the gap between vendor products. When those tools need to integrate a SaaS platform, they hit its API. When they need to integrate the camera system, they usually can’t — because most camera platforms don’t expose one.

This is the quiet reason camera systems don’t participate in enterprise automation. It isn’t a skills problem. It isn’t a priority problem. It’s that the vendor never gave your team a way in. The camera system becomes the one piece of infrastructure your engineering team can’t touch.

Rhombus is built the other way. Every CLI command and every API endpoint is first-class: documented, versioned, and designed to be called from other software.

For the developers:

From Python:

import subprocess, json
cameras = json.loads(subprocess.check_output(
    ["rhombus", "camera", "get-minimal-camera-state-list", "--output", "json"]))

Or hit the REST API directly — over 800 endpoints, all documented, all callable.

The payoff: Your engineering team treats Rhombus like Datadog, Stripe, or any other API-first service. Internal tools wire into it. Custom dashboards pull from it. AI agents call it. The camera system joins the rest of your programmable infrastructure — and the integrations your engineers have been asking for become weekend projects instead of vendor dependencies.