Install Jentic One Beta

Connect the Hubble Platform API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hubble Platform API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubble.com%2Fhubble" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubble.com%2Fhubble" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Hubble Platform API.

Retrieve an organization's packets between start and end times, optionally for one device_id

Decode raw advertisements into packets with the decode endpoint

GET STARTED

Start building with Hubble Platform API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Hubble Platform API for, with concrete tasks.

★ Agent fleet status checks

An AI agent supporting a Hubble device fleet needs to answer which devices reported recently and what they sent. Through Jentic it finds the list-devices and packet operations by intent, filters devices by their most recent packet time, and pulls packets for any device that looks quiet, with the JWT bearer key held by your own instance.

Call GET /v2/org/{org_id}/devices with sort_field set to most_recent_packet_ts and sort_ascending true, then GET /v1/org/{org_id}/packets with device_id set to the first device returned and a start time 24 hours ago

Bulk device provisioning

Rolling out trackers to a new site means registering many devices at once. POST /v2/org/{org_id}/devices takes n_devices up to 1,000 with the required encryption setting, plus names, tags, and install_locations, and batch update and batch delete operations change or retire devices in groups.

Call POST /v2/org/{org_id}/devices with n_devices 50, the required encryption setting, and tags set to warehouse-east, then confirm with GET /v2/org/{org_id}/devices

Packet delivery by webhook

Applications that act on device data should not poll. A webhook endpoint registered with a url and max_batch_size receives decrypted packets in batches, the test endpoint sends a sample delivery, and webhook metrics show how deliveries are going.

Call POST /v1/org/{org_id}/webhooks with url set to your ingest endpoint and max_batch_size 100, then POST /v1/org/{org_id}/webhooks/{webhook_id}/test

Satellite pass planning

Field teams testing coverage want to know when a satellite will be overhead. The passes endpoint takes a latitude and longitude with optional min_altitude_angle and days_ahead and returns upcoming passes, and the ephemeris endpoint returns the orbital elements behind them.

Call GET /v1/org/{org_id}/satellite/passes with latitude 53.35 and longitude -6.26 and days_ahead 2, then list the pass times

Key Endpoints

40 endpoints — the hubble platform api manages an organization's devices on the hubble network and the packet data they send.

METHOD

PATH

DESCRIPTION

GET

/v2/org/{org_id}/devices

List devices

POST

/v2/org/{org_id}/devices

GET

/v1/org/{org_id}/packets

Retrieve packets

POST

/v1/org/{org_id}/packets/decode

Decode packets

POST

/v1/org/{org_id}/webhooks

Create a webhook endpoint

GET

/v1/org/{org_id}/satellite/passes

Upcoming satellite passes

POST

/v1/org/{org_id}/key

Provision an API key

GET

/v2/org/{org_id}/devices

List devices

POST

/v2/org/{org_id}/devices

GET

/v1/org/{org_id}/packets

Retrieve packets

POST

/v1/org/{org_id}/packets/decode

Decode packets

POST

/v1/org/{org_id}/webhooks

Create a webhook endpoint

GET

/v1/org/{org_id}/satellite/passes

Upcoming satellite passes

POST

/v1/org/{org_id}/key

Provision an API key

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Hubble by hand means creating a scoped JWT key, carrying org_id in the URL path, paging with the Continuation-Token header, and staying under per-endpoint and per-organization rate limits. Through Jentic you install once, import Hubble from the API Directory, store the key once, and your agent calls it.

Permission scoping

Hubble puts the organization and device ids in the URL path (/v2/org/{org_id}/devices/{device_id}), so a rule can pin your agent to one organization, or one device, and the operations you pick. You choose the operations it may call, so destructive ones like batch device deletion or API key provisioning are not included unless you add them.

Credential isolation

Your Hubble API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list my devices' or 'next satellite pass', and Jentic returns the matching Hubble operation with its input schema so the agent fills org_id, device_id, and time ranges correctly without browsing the reference docs.

FAQs

Specific to using Hubble Platform API through Jentic.

What authentication does the Hubble Platform API use?

Per its OpenAPI spec, the Hubble Platform API uses HTTP bearer authentication with a JWT API key created in the Hubble dashboard, and most paths also need your org_id. Keys can be limited to scopes such as read-devices, write-devices, or read-packets, and a key created without scopes gets all of them. Packet webhooks you host receive an HTTP-X-HUBBLE-TOKEN header so you can verify deliveries.

Can I register many devices at once with the Hubble Platform API?

Yes. POST /v2/org/{org_id}/devices registers between 1 and 1,000 devices per call with n_devices and a required encryption setting, and can set names, tags, eid_rotation, and install_locations. PATCH and DELETE on the same path update or remove devices in bulk.

What are the rate limits for the Hubble Platform API?

The spec states a leaky bucket limit of three requests per second per endpoint and 15 requests per second in total for your organization. Going over returns a 429, and Hubble recommends backoff retry logic.

Is there a Hubble MCP server?

You don't need an MCP server to give your agent Hubble. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the device, packet, and satellite operations it needs, discovered on demand rather than loaded into its context up front.

How do I retrieve device packets through Jentic?

Search Jentic for 'retrieve hubble device packets', load GET /v1/org/{org_id}/packets, and pass start and end times with an optional device_id, following the Continuation-Token header to page. Your instance attaches the bearer key at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Hubble Platform API?

Yes. For example, allow only GET /v2/org/{org_id}/devices/{device_id} and GET /v1/org/{org_id}/packets for your org id, and the agent can check devices and read their packets but cannot delete devices, provision API keys, or invite users, and its calls are logged.

Hubble Platform API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyIOTDevice Managementbearer40 EndpointsREST

For Agents

Register and update Hubble devices, pull or decode their packets, set up packet webhooks, check upcoming satellite passes, and read organization metrics and billing.

Use for: List all devices in my Hubble organization, Retrieve the packets a device sent in the last 24 hours, Register 50 new devices with tags for a warehouse deployment, Check when the next satellite pass is over my site

Not supported: Does not manufacture or flash device firmware, provide cellular connectivity, or analyse packet contents for you. Use for managing Hubble devices, their packet data, and organization settings only.

The Hubble Platform API manages an organization's devices on the Hubble network and the packet data they send. It registers new devices with their encryption settings in batches of up to 1,000, updates names, tags, and install locations, retrieves packets by time range or device_id, and decodes raw advertisements. Webhook endpoints receive decrypted packets in batches up to a configured max_batch_size, satellite endpoints return the ephemeris and upcoming passes over a latitude and longitude, and organization tooling covers scoped API keys, users and invitations, platform metrics, and billing usage and invoices.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4

84%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

35%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

18%

Example Density

How richly the API is illustrated with examples.

96%

Example Validity

Percentage of examples that conform to their schemas.

74%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C+Signals: 4

74%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

61%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

71%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Hubble Platform API to your agent

Capabilities

Start building with Hubble Platform API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hubble Platform API

Jentic AI Readiness Score

Hubble Platform API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness