It definitely introduces a new precedent, interacting with a non-local API. It's not far from the

curl

or

curl_tls

tables, but those are more utility/general purpose; enough so to call this new table 'unique' for osquery. It's good to note the AWS API tables too, although they use local APIs and the transport being HTTP is mostly an implementation detail in that sense.