TagoIO
TagoIO is an IoT cloud application development platform that enables businesses to build, deploy, and manage IoT applications with a comprehensive REST API. The platform provides full programmatic control over devices, dashboards, data storage, analysis scripts, alerts, and user management. TagoIO exposes regional REST API endpoints covering device data ingestion, entity management, access control policies, and file storage, all secured with token-based authentication. Plans range from a free tier supporting five devices up to an enterprise-grade TagoDeploy option supporting millions of devices with dedicated cloud instances and customizable rate limits.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles TagoIO the way a machine reads it — 35 machine-readable artifacts across 22 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 — TagoIO scores 65.2/100 (strong), with a separate agent-readiness read of 48/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile TagoIO
Each block below is one kind of artifact we hold for TagoIO. 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 22
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.
TagoIO Access Management API
Roles, permissions, and sharing (Profile Token).
TagoIO Account API
Account-level operations (Profile Token).
TagoIO Backup API
The Backup API from TagoIO — 3 operation(s) for backup.
TagoIO Configuration Param API
The Configuration Param API from TagoIO — 2 operation(s) for configuration param.
TagoIO Dashboards API
Manage dashboards (Profile Token).
TagoIO Device Data API
Endpoints that act as a device using a Device Token (device-level permissions).
TagoIO Device Tokens API
Manage device tokens (Profile Token).
TagoIO Devices API
Manage devices using a Profile Token (admin-level).
TagoIO Dictionary API
Manage Dictionary Slugs and Keys for TagoRUN (Profile Token).
TagoIO Entity API
Manage entities (Profile Token).
TagoIO Entity Data API
Operations specific to managing entitie stored data (Profile Token)
TagoIO Files API
File storage operations (Profile Token).
TagoIO Immutable Device API
Operations specific to immutable device type (Profile Token).
TagoIO Import/Export API
Import/Export Operations for devices (Profile Token).
TagoIO Network Ingest API
Endpoints that act as a network using a Network Token (network-level permissions).
TagoIO Notifications API
Manage notifications (Profile Token).
TagoIO Profile API
Manage your own profile settings (Profile Token).
TagoIO Statistics / Billing API
Usage statistics and billing (Profile Token).
TagoIO Tago RUN API
The Tago RUN API from TagoIO — 2 operation(s) for tago run.
TagoIO Upload API
The Upload API from TagoIO — 1 operation(s) for upload.
TagoIO Users API
Manage TagoRUN users (Profile Token).
TagoIO Widgets API
Manage widgets (Profile Token).
Scroll within the panel for all 22 ·
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 six things the Kin Score reads for commercial clarity.
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.
Tago Io Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Tago Io Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Tago Io Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
TagoIO API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
TagoIO Device Data Item
JSON SCHEMATagoIO Device
JSON SCHEMAExamples 2
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Tago Io List Devices Example
EXAMPLESecurity 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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for TagoIO — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
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/tago-io · machine-readable index on apis.io