Kontakt.io
Kontakt.io is an AI-powered real-time location system (RTLS) and IoT platform for healthcare operations, founded in 2013 with offices in New York and Krakow. Its Kio Cloud platform combines BLE/UWB tags, badges, gateways and sensors with software for asset tracking, staff safety, patient flow, room and seat occupancy, and environmental telemetry. Developers integrate through the Kontakt.io Developer Center, which publishes four OpenAPI contracts: a Device Management API for provisioning, configuring and firmware-upgrading devices, a Location & Occupancy API for real-time and historical positions, presences, occupancy and telemetry plus a Streams API for event subscriptions, a Spaces API, and an Entity Management Integration API for batch import of staff and asset entities. Kio Cloud runs in US and UK regions and ships iOS and Android SDKs.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Kontakt.io the way a machine reads it — 38 machine-readable artifacts across 8 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 — Kontakt.io scores 61.9/100 (strong), 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-04 · rubric v0.23.0
Put this on your own site. The badge is drawn live from Kontakt.io'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/kontaktio/"
title="Kontakt.io on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/kontaktio.svg"
alt="Kontakt.io Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/kontaktio/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/kontaktio/"
title="Kontakt.io on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/kontaktio/card.svg"
alt="Kontakt.io 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 Kontakt.io
Each block below is one kind of artifact we hold for Kontakt.io. 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 30
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.
Kontakt.io Buildings API
The Buildings API from Kontakt.io — 2 operation(s) for buildings.
Kontakt.io Campuses API
The Campuses API from Kontakt.io — 2 operation(s) for campuses.
Kontakt.io Colocations API
The Colocations API from Kontakt.io — 1 operation(s) for colocations.
Kontakt.io Command API
Commands are a special type of Configs used for initiating some management tasks, e.g. entering bootloader mode
Kontakt.io Config API
Pending configs represent new values for beacon settings that should be applied to actual devices via e.g. Kontakt.io Administration Apps. Creating a new config does not automat...
Kontakt.io Device (3rd party) API
NOTE: this set of endpoints has been superseded by External Devices functionality. These endpoints provide a way to integrate 3rd party Bluetooth-enabled scanning devices into K...
Kontakt.io Device API
The Device resource represents Kontakt.io devices assigned to a particular Kontakt.io Panel account, as well as devices shared with that account from different accounts.
Kontakt.io Device (Portal Beam) API
These endpoints are designed to assist with storing metadata associated with Portal Beams
Kontakt.io Device tags API
The device tags
Kontakt.io Eddystone API
Helper resources for working with Eddystone beacons
Kontakt.io Entity Integration API
The entity-integration API from Kontakt.io — 2 operation(s) for entity-integration.
Kontakt.io External Device API
External Device feature is a method of adding arbitrary external devices to the system. Such devices have MAC, unique id, and other virtual attributes, but they cannot be manage...
Kontakt.io Firmware API
Firmware resources
Kontakt.io Floors API
The Floors API from Kontakt.io — 1 operation(s) for floors.
Kontakt.io Footfall Spaces API
The Footfall Spaces API from Kontakt.io — 1 operation(s) for footfall spaces.
Kontakt.io Gateways API
The Gateways API from Kontakt.io — 1 operation(s) for gateways.
Kontakt.io Location Images API
The Location Images API from Kontakt.io — 1 operation(s) for location images.
Kontakt.io Manager API
Managers represent user accounts that can manage Kontakt.io Devices. Everyone can freely create an account on [Kontakt.io Web Panel](https://panel.kontakt.io) and then use it to...
Kontakt.io Occupancy API
The Occupancy API from Kontakt.io — 1 operation(s) for occupancy.
Kontakt.io Occupancy: Footfall API
The Occupancy: Footfall API from Kontakt.io — 2 operation(s) for occupancy: footfall.
Kontakt.io Occupancy: Room API
The Occupancy: Room API from Kontakt.io — 2 operation(s) for occupancy: room.
Kontakt.io Occupancy: Seats API
The Occupancy: Seats API from Kontakt.io — 2 operation(s) for occupancy: seats.
Kontakt.io Order API
An Order represents all devices that have been purchased in Kontakt.io Web Store in a single transaction. Before these devices can be used with Kontakt.io platform, they need to...
Kontakt.io Positions API
The Positions API from Kontakt.io — 2 operation(s) for positions.
Kontakt.io Presences API
The Presences API from Kontakt.io — 2 operation(s) for presences.
Kontakt.io Proximities API
List of iBeacon Proximity UUIDs used on beacons belonging to a Manager
Kontakt.io Rooms API
The Rooms API from Kontakt.io — 2 operation(s) for rooms.
Kontakt.io Spaces API
The Spaces API from Kontakt.io — 2 operation(s) for spaces.
Kontakt.io Stream API
The Stream API from Kontakt.io — 9 operation(s) for stream.
Kontakt.io Telemetry API
The Telemetry API from Kontakt.io — 1 operation(s) for telemetry.
Scroll within the panel for all 30 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
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.
Kontaktio 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.
Kontaktio Streams Events
ASYNCAPISecurity 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.
Resources
Every other property we hold for Kontakt.io — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
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/kontaktio · machine-readable index on apis.io
This is an independent, third-party profile of Kontakt.io, 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.