Wiliot
Wiliot operates an ambient IoT platform built on battery-free "IoT Pixels" - postage-stamp-sized Bluetooth sensor tags - and a cloud that turns everyday physical items into a continuous, real-time data source for supply-chain visibility ("Physical AI"). Wiliot's Cloud APIs expose three surfaces: a Platform (traceability) API for pixels, assets, categories, locations, zones and events; an Edge API for gateways, bridges and coverage surveys; and a Manufacturing API for pixel ownership, reels, serialization and sensor/tester data. Access uses an API key (or username/password) exchanged for a JWT bearer token, over a versioned REST surface scoped per owner. Official Python SDKs (wiliot-api, wiliot-core, and others) plus a React Native SDK are published.
Wiliot is listed with 3 APIs on the APIs.io network. Tagged areas include Company, IoT, Ambient IoT, Supply Chain, and Asset Tracking.
Wiliot’s developer surface includes documentation, engineering blog, support, authentication, changelog, and 16 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Cisco DevNet Ecosystem (builders on Meraki, Catalyst, ISE, ThousandEyes, Splunk) | builds-on | 17.2 (thin) | - | - |
| Wireless and Wired Connectivity Certification (Thread, USB-IF, Wi-Fi Alliance) | builds-on | 17.2 (thin) | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 3
Individual APIs this provider publishes, each with its own machine-readable definition.
Wiliot Platform (Traceability) API
Manage traceability entities - Pixels (tags), assets, categories, asset types, locations, zones, metadata and events - scoped per owner.
Wiliot Edge API
Manage edge infrastructure - gateways, bridges, verification bridges and debug/coverage surveys.
Wiliot Manufacturing API
Manufacturing operations - pixel ownership changes, reels, tag serialization, shipment approval, payload parse/resolve and sensor/tester data upload.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Source (apis.yml)
Wiliot API — frequently asked questions
Does Wiliot have an API?
Yes. APIs.io lists 3 APIs from Wiliot, including Wiliot Platform (Traceability) API, Wiliot Edge API and Wiliot Manufacturing API.
How do I authenticate with the Wiliot API?
Wiliot uses bearer-token authentication (apiKey/oauth2 · 3 schemes). The details are profiled on APIs.io as Wiliot Authentication.
Is the Wiliot API ready for AI agents?
Wiliot has a Kin Score of 24.9 out of 100 (emerging) and an Agent Readiness score of 2.5 (human-only), scored by API Evangelist on 2026-11-06.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.