Ok, so currently the hub can make outbound HTTP requests only. This is how LAN integrations are done for Foscam, Radio Thermostat, VLC Thing, just to name a few. There’s however much wider selection of 3-rd party LAN-connected devices with published (or reverse-engineered) API that use simple TCP socket protocol (a.k.a. ‘telnet’). Integration with these devices currently requires setting up a ‘bridge’ (typically a Linux server, e.g. Raspberry Pi) to translate HTTP requests from the hub to TCP socket messages.
The TCP socket feature has been requested numerous times by the community and was finally promised “before the end of the year” (that’s 2014). This promise has not materialized, unfortunately.
Thanks @geko. Your comments and some additional research helped considerable. Much appreciated! Reiterating to check my understanding. . . . the examples you gave are of existing hardware solutions for connecting things to a LAN (via wired or wireless connection), however, they do not support a HTTP layer and therefore will not support a RESTful HTTP API. They do support TCP, a lower level protocol, which can be supported with additional software on existing hub hardware. Right?