Hubble Network
Hubble Network is a Seattle-based IoT connectivity company, founded in 2021 by Alex Haro (Life360) and Ben Wild (Amazon Sidewalk), building a dual-stack global network that any standard Bluetooth Low Energy 5.0+ chip can reach with no modem and no custom radio hardware. The Terrestrial Network aggregates 100M+ BLE scanning gateways across 2,500+ cities, and a low-Earth-orbit Satellite Network is rolling out on the same silicon. The platform is built API-first: the Hubble Platform (Cloud) API at api.hubble.com covers device registration and lifecycle, encrypted packet retrieval and streaming, packet webhooks, platform metrics, organization and user administration, scoped API keys, and billing. Hubble publishes a public OpenAPI definition, an open-source Device SDK in C, a Python SDK/CLI, gateway SDKs for Linux, iOS and Android, and an official Claude Code agent skill for its Cloud API.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Hubble Network the way a machine reads it — 33 machine-readable artifacts across 7 APIs, 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 — Hubble Network scores 71.6/100 (exemplar), with a separate agent-readiness read of 51/100 (agent ready). 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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Hubble Network's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hubble-network/"
title="Hubble Network on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hubble-network.svg"
alt="Hubble Network Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/hubble-network/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hubble-network/"
title="Hubble Network on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hubble-network/card.svg"
alt="Hubble Network Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Hubble Network
Each block below is one kind of artifact we hold for Hubble Network. 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.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Hubble Network API Keys API
The API Keys API from Hubble Network — 4 operation(s) for api keys.
Hubble Network Billing API
The Billing API from Hubble Network — 6 operation(s) for billing.
Hubble Network Devices API
The Devices API from Hubble Network — 3 operation(s) for devices.
Hubble Network Organizations API
The Organizations API from Hubble Network — 4 operation(s) for organizations.
Hubble Network Packet Webhooks API
The Packet Webhooks API from Hubble Network — 3 operation(s) for packet webhooks.
Hubble Network Packets API
The Packets API from Hubble Network — 2 operation(s) for packets.
Hubble Network Platform Metrics API
The Platform Metrics API from Hubble Network — 4 operation(s) for platform metrics.
Scroll within the panel for all 7 ·
Open Collections 8
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONHubble Platform API Keys API
OPEN COLLECTIONHubble Platform Billing API
OPEN COLLECTIONHubble Platform Devices API
OPEN COLLECTIONHubble Platform Organizations API
OPEN COLLECTIONHubble Platform Packet Webhooks API
OPEN COLLECTIONHubble Platform Packets API
OPEN COLLECTIONHubble Platform Platform Metrics API
OPEN COLLECTIONScroll within the panel for all 8 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Hubble Network Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Hubble Network Packet Webhooks
ASYNCAPIJSON Schema 10
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Hubble API Key
JSON SCHEMAHubble Billing Subscription
JSON SCHEMAHubble Device
JSON SCHEMAHubble Error Response
JSON SCHEMAHubble Invitation
JSON SCHEMAHubble Organization User
JSON SCHEMAHubble Organization
JSON SCHEMAHubble Packet Batch
JSON SCHEMAHubble Packet
JSON SCHEMAHubble Packet Webhook
JSON SCHEMAScroll within the panel for all 10 ·
Security Posture 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Hubble Network — 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 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 6
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 8
Status, limits, changes, and where to get help
Scroll within the panel for all 8 ·
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
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/hubble-network · machine-readable index on apis.io
This is an independent, third-party profile of Hubble Network, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.