Adafruit IO APIs for AI Agents
IOTSensor DataMixed ProvenanceAPI keyAgent Ready
For Agents
APIs2 in catalogue
Endpoints89 indexed
AuthAPI key — 1 credential for all 2 APIs
ProvenanceMixed provenance
Across Adafruit IO's APIs an agent can create feeds and ingest sensor readings in batches, group related feeds, read latest and historical data, build dashboards with blocks, and manage triggers, device tokens, and ACL rules for an account.
Adafruit IO is a hobbyist and education-focused IoT cloud built around simple feeds and dashboards for microcontrollers like the Feather, ESP32, and Raspberry Pi. It pairs telemetry ingest with visual dashboards and feed-value triggers under one API key, without requiring firmware or connectivity hardware from the same vendor.
Adafruit IO API Catalog
2 APIs across 1 product group. All share one credential.
Which Adafruit IO API should I use?
| I want to... | Use |
|---|---|
| Read and write feeds, groups, and feed data for basic telemetry | Adafruit IO API |
| Manage dashboards, triggers, tokens, ACL, and webhooks | Adafruit IO REST API |
Install Jentic One Beta
Connect the Adafruit IO APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adafruit IO APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadafruit.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadafruit.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “ingest Adafruit IO sensor feeds and build a dashboard”.
What AI Agents Can Do with Adafruit IO
Each workflow spans multiple Adafruit IO APIs. Jentic routes each operation to the right API automatically.
Ingest telemetry, then chart it on a dashboard
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Adafruit IO by hand means attaching the X-AIO-Key (and X-AIO-Signature for signed requests) on every call and threading the username, feed key, and dashboard id through feeds, groups, dashboards, triggers, tokens, and webhooks. With Jentic One installed, an agent finds either Adafruit IO API in the Jentic directory, adds it to your workspace, and calls both surfaces under one credential.
Permission scoping
Adafruit IO puts the feed key in the URL path (/{username}/feeds/{feed_key}/...), so your own rules in your Jentic One instance can pin the agent to a single feed, letting it batch data in and read its chart while everything else stays off. Higher-impact operations such as creating triggers, rotating tokens, or building dashboards are only callable if you explicitly grant them.
Credential isolation
Your Adafruit IO X-AIO-Key and X-AIO-Signature are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context, and they cover both surfaces from one place.
Intent-based discovery
An agent searches the Jentic directory by intent such as 'read the latest Adafruit IO feed value' or 'create an Adafruit IO dashboard', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
FAQs
Specific to using Adafruit IO APIs through Jentic.
Do the two Adafruit IO APIs use the same account and key?
Yes. Both surfaces sit on the io.adafruit.com/api/v2 base and authenticate with the same X-AIO-Key tied to your Adafruit IO account, so a single key works across feeds, groups, dashboards, triggers, tokens, and webhooks.
Which Adafruit IO API should my agent start with?
Start with the slimmer feed API if you only need to read and write feeds, groups, and feed data. Move to the full REST surface when you need dashboards and blocks, feed-value triggers, device tokens, ACL rules, throttle status, activities, or inbound webhooks.
Can an agent both ingest telemetry and build a dashboard for it?
Yes. An agent can create feeds and batch readings on either surface, then use the full REST surface to create a dashboard and add chart, gauge, or toggle blocks bound to those feeds, so ingest and visualisation are driven from one workflow.
How does Adafruit IO handle rate limits across these APIs?
Adafruit IO enforces a per-minute data throughput cap that depends on the account tier. The full REST surface exposes GET /{username}/throttle to read remaining capacity, and batch ingest endpoints let a device send many readings in one request to stay within budget.
Is an official OpenAPI spec published for these APIs?
Adafruit publishes API documentation but not a structured OpenAPI specification. Jentic generates and maintains validated specs for both Adafruit IO surfaces so agents can call them through structured tooling, with the wider REST surface based on Adafruit's own published spec.
What hardware does Adafruit IO work with?
Adafruit IO is built for maker boards such as the Feather, ESP32, and Raspberry Pi that publish sensor readings to feeds. The APIs cover the cloud side of that flow and do not manage firmware, cellular connectivity, or device provisioning.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.