Adafruit IO
Adafruit IO is a cloud Internet of Things platform from Adafruit Industries built for makers, hobbyists, students, and STEM educators. It provides feed-based time-series storage, drag-and-drop dashboards with 20+ visualization block types, actions/triggers for SMS/voice/email/webhook notifications, built-in services (time, weather, randomizer, air quality), and a complete REST + MQTT API surface for Adafruit Feather and Metro boards, ESP32 / ESP8266 / Pico microcontrollers, Raspberry Pi, and any other HTTP- or MQTT-capable hardware. First-class Arduino, CircuitPython, and Python client libraries plus the no-code Wippersnapper firmware make it the easiest way for hobbyists to get their projects onto the Internet of Things.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Adafruit IO the way a machine reads it — 72 machine-readable artifacts across 1 API, 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 — Adafruit IO scores 61.3/100 (strong), with a separate agent-readiness read of 24/100 (agent aware). 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.
Put this on your own site. The badge is drawn live from Adafruit 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/adafruit-io/"
title="Adafruit IO on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/adafruit-io.svg"
alt="Adafruit IO Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/adafruit-io/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/adafruit-io/"
title="Adafruit IO on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/adafruit-io/card.svg"
alt="Adafruit 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 Adafruit IO
Each block below is one kind of artifact we hold for Adafruit 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 12
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.
Adafruit IO MQTT API
MQTT broker at io.adafruit.com for publish/subscribe access to Adafruit IO feeds and groups. TLS on port 8883, plaintext on 1883, and MQTT-over-WebSocket on port 443. Authentica...
Adafruit IO Activities API
The Activities API from Adafruit IO — 2 operation(s) for activities.
Adafruit IO Blocks API
The Blocks API from Adafruit IO — 2 operation(s) for blocks.
Adafruit IO Dashboards API
The Dashboards API from Adafruit IO — 2 operation(s) for dashboards.
Adafruit IO Data API
The Data API from Adafruit IO — 14 operation(s) for data.
Adafruit IO Feeds API
The Feeds API from Adafruit IO — 6 operation(s) for feeds.
Adafruit IO Groups API
The Groups API from Adafruit IO — 5 operation(s) for groups.
Adafruit IO Permissions API
The Permissions API from Adafruit IO — 2 operation(s) for permissions.
Adafruit IO Tokens API
The Tokens API from Adafruit IO — 2 operation(s) for tokens.
Adafruit IO Triggers API
The Triggers API from Adafruit IO — 2 operation(s) for triggers.
Adafruit IO Users API
The Users API from Adafruit IO — 2 operation(s) for users.
Adafruit IO Webhooks API
The Webhooks API from Adafruit IO — 2 operation(s) for webhooks.
Scroll within the panel for all 12 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Adafruit IO REST API
POSTMANOpen Collections 13
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAdafruit IO REST Activities API
OPEN COLLECTIONAdafruit IO REST Activities Blocks API
OPEN COLLECTIONAdafruit IO REST Activities Dashboards API
OPEN COLLECTIONAdafruit IO REST Activities Data API
OPEN COLLECTIONAdafruit IO REST Activities Feeds API
OPEN COLLECTIONAdafruit IO REST Activities Groups API
OPEN COLLECTIONAdafruit IO REST Activities Permissions API
OPEN COLLECTIONAdafruit IO REST API
OPEN COLLECTIONAdafruit IO REST Activities Tokens API
OPEN COLLECTIONAdafruit IO REST Activities Triggers API
OPEN COLLECTIONAdafruit IO REST Activities Users API
OPEN COLLECTIONAdafruit IO REST Activities Webhooks API
OPEN COLLECTIONScroll within the panel for all 13 ·
Arazzo Workflows 9
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Adafruit IO Attach Feed to Group
Add an existing feed to a group, then list the group's feeds to confirm membership.
ARAZZOAdafruit IO Batch Ingest and Chart
Bulk upload many data points to a feed, then fetch aggregated chart data for it.
ARAZZOAdafruit IO Build Dashboard with Block
Create a dashboard, add a visualization block to it, then read the block back.
ARAZZOAdafruit IO Create and Verify Trigger
Create a reactive trigger for the user, then read it back to confirm it exists.
ARAZZOAdafruit IO Ensure Feed Exists
Look up a feed by key and create it only when it is missing, then push a value.
ARAZZOAdafruit IO Group Feed Bootstrap
Create a group, add a new feed inside it, then write a data point to that grouped feed.
ARAZZOAdafruit IO Group Multi-Feed Publish
Publish values to several feeds in a group at once, then read one feed's data back.
ARAZZOAdafruit IO Issue and Verify Token
Create a device token for the user, then read it back to confirm it was issued.
ARAZZOAdafruit IO Provision Feed and Seed Data
Create a feed, push an initial data point to it, then read the last value back.
ARAZZOScroll within the panel for all 9 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Adafruit IO GraphQL Schema
Conceptual GraphQL schema for the Adafruit IO IoT cloud platform. Adafruit IO provides feed-based time-series storage, drag-and-drop dashboards, reactive and scheduled triggers,...
GRAPHQLPricing 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.
Adafruit 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.
Adafruit Io Finops
FINOPSFeatures 18
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 18 ·
Semantic 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.
Adafruit Io Context
JSON-LDSpectral Rules 2
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.
Adafruit IO API Rules
SPECTRALAdafruit IO API Rules
SPECTRALJSON Schema 3
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.
JSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Adafruit Io Dashboard Structure
JSON STRUCTUREAdafruit Io Feed Structure
JSON STRUCTUREExamples 3
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.
Security 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 Adafruit 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 5
Portal, sign-up, and the first successful call
Documentation 7
Reference material describing how the API behaves
Scroll within the panel for all 7 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 10
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 10 ·
Build 13
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 13 ·
Access & Security 4
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 6
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/adafruit-io · machine-readable index on apis.io
This is an independent, third-party profile of Adafruit 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.