Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

The Things Network (BYOK) — connector documentation

  • MCP endpoint: https://byok-thethingsnetwork.connectorbay.com/mcp
  • REST API: POST https://byok-thethingsnetwork.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-thethingsnetwork.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own The Things Network The Things Stack API key (starts with NNSXS.; give it read rights only), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-thethingsnetwork.connectorbay.com/health · Tool schemas: https://byok-thethingsnetwork.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-thethingsnetwork · agent@connectorbay.com

What The Things Network (BYOK) is for

The Things Network (BYOK) lets an AI assistant read your own The Things Network data through the The Things Network API with a key you supply (The Things Stack API key (starts with NNSXS.; give it read rights only)). Read-only: 9 tools (list_applications, get_application, list_end_devices, get_end_device, count_end_devices, list_gateways, get_gateway, get_gateway_connection_stats, list_frequency_plans). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to eu1.cloud.thethings.network, nam1.cloud.thethings.network, au1.cloud.thethings.network. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by The Things Network. The Things Network and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which LoRaWAN applications do I have on The Things Network?"
  • "Show the details of The Things Network application my-sensors"
  • "Which devices are registered in my-sensors and when were they last seen?"
  • "Show the details of device sensor-01 in my-sensors"
  • "How many devices are in my-sensors?"
  • "Which LoRaWAN gateways do I own on The Things Network?"

What it does

  • list_applications: List the applications you can access with id, name, description and dates.
  • get_application: Get one application's name, description, dates and end device limit.
  • list_end_devices: List the end devices registered in an application with ids, EUIs, name, last seen time, battery, LoRaWAN version and frequency plan.
  • get_end_device: Get one end device's ids, EUIs, name, last seen time, battery, LoRaWAN version, frequency plan and model.
  • count_end_devices: Count the end devices registered in an application.
  • list_gateways: List the gateways you can access with id, EUI, name, frequency plan and visibility flags.
  • get_gateway: Get one gateway's id, EUI, name, frequency plan, update channel, model and visibility flags.
  • get_gateway_connection_stats: Get live statistics of a gateway's connection: connect and disconnect time, last uplink and last status times, uplink and downlink counts and round trip times.
  • list_frequency_plans: List the LoRaWAN frequency plans known to the cluster with id, name and band, optionally for one band or gateways only.

BYOK key

You bring your own The Things Network The Things Stack API key (starts with NNSXS.; give it read rights only) (https://www.thethingsindustries.com/docs/integrations/adding-applications/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to eu1.cloud.thethings.network, nam1.cloud.thethings.network, au1.cloud.thethings.network over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the The Things Network API (eu1.cloud.thethings.network, nam1.cloud.thethings.network, au1.cloud.thethings.network) with a BYOK key; documentation: https://www.thethingsindustries.com/docs/api/reference/http/routes/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by The Things Network. The Things Network and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your The Things Network account.

Built for: Worldwide. Languages: English.