The Things Network scores 79.2 on the Kin Score, exemplar band, up from 78.3. Its Agent Readiness is 33.7. That is a 45-point gap between how well the surface is built for a developer and how ready it is for an agent, and it sits in the widest twenty of the 412 exemplar providers scored for agent readiness.
The Things Network is the free, community-operated LoRaWAN network. By its own count it has over 280,000 members and 21,000 gateways across 153 countries, and it runs on The Things Stack, the Apache-2.0 network server that The Things Industries maintains. The same software runs the community network, the paid Cloud tiers, and self-hosted Enterprise installs, so one API surface serves all of them.
What is in the surface
The provider publishes 9 OpenAPI source specs. The catalog splits them into 58 API pages, one per service: the Identity Server, Application Server, Network Server, Gateway Server, Join Server, the Device Repository, the Packet Broker Agent, and the registries that hang off each. All 58 contracts are callable. Around them sit a webhooks AsyncAPI, 6 pricing plans, 7 documented rate limits, a CLI, the lorawan-stack source on GitHub with its release changelog, and a HackerOne disclosure program.
| Facet | Score |
|---|---|
| Operational transparency | 88.9 |
| Developer ergonomics | 81.5 |
| Access clarity | 81.1 |
| Discoverability | 69.6 |
| Contract quality | 67.7 |
| Contract governance | 45.5 |
Operational transparency at 88.9 is what open source buys you. When the server is on GitHub, the changelog, the release history, and the behaviour are all public, and the rubric can see them.
Where the agent score comes from
The agentic access profile maps 329 operations, 172 of them acting, 3 flagged human-in-the-loop. That profile is marked derived: we generated it from the contracts, so it is not credited to The Things Network, and three consent markers across 172 acting operations is our reading, not theirs. The agent skills are derived too. There is no MCP server.
What The Things Network earns on its own is the documentation layer: error semantics, rate-limit signals, reversibility, and OpenAPI examples are all documented, bearer auth is clear, the event surface is described, and a well-known catalog resolves. What is unlit is the entire identity layer for agents: no protected resource metadata, no dynamic client registration, no delegated identity, no consent identity. The scopes artifact reads “OAuth 2.0 · no documented scopes” against five authentication schemes. There is no idempotency, no dry-run mode, and no agent card.
Contract governance at 45.5 is the other soft spot, and the lowest facet on the page.
What would move the number
A LoRaWAN network is a natural agent surface. Devices, gateways and uplinks are exactly what an operations agent would query and provision. The Things Network has the hard part done: callable contracts, public source, clear operations. The cheap next steps are documented OAuth scopes on the servers it already runs, protected resource metadata that points at them, and an MCP server over the Application Server and device registries. Each of those lights a dimension that is dark today, and none of them needs a new API.
See the full profile at apis.io/providers/the-things-network/.