the missing infrastructure layer

Make physical capabilities callable.

Agents already have tools for the digital world — email, CRM, payments, scheduling. We give them tools for reality: one stable function surface over cameras, sensors, locks and edge AI.

▸ awaiting call… simulated call10 device kinds
02the shift

Agents are moving from software into the physical world.

Today they operate digital systems. Next they operate physical environments — and every one of them will need somewhere real to reach.

today · digital
EmailCRMPayments SupportScheduling
reached over APIs and webhooks — an interface someone already built for them
next · physical
SeeSenseListen LocateControl
reached over cameras, sensors, locks and machines — where no such interface exists
03the problem

Below every agent, the physical world is fragmented.

A camera, a leak probe and a vibration sensor share no vendor, no protocol and no data model. Nothing sits between the agent and any of them.

ten kinds · ten data models · ten separate ways to be offline

04what happens today

So every software company becomes a hardware integrator.

Partner with vendors. Integrate APIs and protocols. Deploy and provision. Manage a fleet. Then write your own abstraction — again, and again, and again.

property software
Partner with lock vendors
Integrate APIs & protocols
Deploy + provision
Manage devices
Build custom abstraction
grant_access() · detect_leak()
restaurant software
Partner with camera vendors
Integrate APIs & protocols
Deploy + provision
Manage devices
Build custom abstraction
check_queue() · detect_arrival()
maintenance software
Partner with sensor vendors
Integrate APIs & protocols
Deploy + provision
Manage devices
Build custom abstraction
machine_running() · detect_anomaly()

the same physical stack, rebuilt from zero in every vertical

05the layer

Agents call capabilities — not devices.

One stable tool surface across changing hardware, vendors and protocols. The layer absorbs the churn so the agent never has to see it.

ai agents
ClaudeGPTVertical agentsCustom agents
physical capability layer
observe_space(space_id) count_people(space_id) detect_arrival(space_id) grant_access(door_id) machine_running(asset_id) detect_leak(space_id) temperature(space_id) detect_anomaly(asset_id)
one surface · stable across vendors, protocols and hardware refreshes
whatever is actually installed
CamerasSensorsEdge AI Access controlMachinesGateways
06how it lands

One integration. Any physical endpoint.

We abstract the infrastructure that is already on site, and deploy nodes where nothing is. The intent is that one integration with a vertical SaaS or an operator reaches every location they already serve.

before
Camera integration
Sensor integration
Lock integration
Edge runtime
Device management
Custom abstraction
with the layer
Physical Capability API · MCP
existing hardware certified kit partner install
whichever of the three a site already happens to be
07the pattern

A new layer appears whenever software needs a stable interface to a fragmented world.

It has happened three times. Each one hid a mess nobody wanted to own. It has not happened yet for the physical world.

layer 01

Internet

Information
what it hid
TCP/IP · DNS
HTTP · ISPs
peering · routing
layer 02

Stripe

Payments
what it hid
acquirers · card networks
PCI · chargebacks
payouts · reconciliation
layer 03

Twilio

Communications
what it hid
carriers · SS7
shortcodes · numbering
deliverability
layer 04 · forming

Us

Physical capabilities
what it hides
onvif · modbus · zigbee
lorawan · osdp · mqtt
edge models · provisioning
devices · sensors · edge ai

Make physical capabilities callable.

If you are building agents that need to reach a real place — or you already run the hardware in one — we should talk.

Get API access