canonical: https://jentic.com/apis/io.adafruit.com/adafruit-io # Io Adafruit Adafruit IO API Adafruit IO is an IoT data platform API for storing and retrieving time-series data through feeds, groups, and dashboards. Applications create feeds, push data records to them, and read back the latest values, full history, or chart-ready series. Groups organize related feeds, and batch endpoints record multiple data points at once for connected devices and sensors. ## For AI agents Lets an AI agent write and read IoT time-series data on Adafruit IO through feeds and groups, including latest values, history, and batch data records. ## Scope Does not handle device firmware, provisioning, or user account management. Use it for storing and retrieving IoT feed data only. ## Capabilities - Create feeds and organize them into groups - Push data records to a feed from a device or sensor - Read the latest value, full history, or chart data for a feed - Record multiple data points in a single batch request - List and manage feeds and groups for an account ## Use cases ### Sensor data logging A connected device needs somewhere to send its readings. Adafruit IO accepts data records on a feed, keeps the time-series history, and returns the latest value on demand, so a device or gateway can log measurements without running its own store. Batch records let a device flush several readings in one call. Example prompt: Push a temperature reading to a feed and confirm it was recorded ### Dashboard and history retrieval A monitoring view needs the latest and historical values for a set of feeds. Adafruit IO returns the last data point, the full history, and chart-ready series for a feed, letting an application render live tiles and trend charts from stored data. Groups keep related feeds together for a single view. Example prompt: Fetch the last data point and the recent history for a feed to render a chart ### AI agent device monitoring An AI agent monitoring devices can read feed values, spot anomalies, and log derived readings back. The agent pulls the latest data for a feed, evaluates it, and writes a status record, with each feed operation gated behind what the operator has allowed. Read-only access keeps monitoring separate from write rights. Example prompt: Read the latest value for a feed, evaluate a threshold, and write a status record to another feed ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/{username}/feeds` | List all feeds for the account | | POST | `/{username}/feeds` | Create a new feed | | GET | `/{username}/feeds/{feed_key}/data` | Get all data for a feed | | POST | `/{username}/feeds/{feed_key}/data` | Create a new data record on a feed | | GET | `/{username}/feeds/{feed_key}/data/last` | Get the last data point on a feed | | GET | `/{username}/groups` | List all groups | ## Key resources - **Feeds** — Create, list, update, and delete feeds for an account - **Data** — Create, batch, and read feed data including latest, history, and chart series - **Groups** — List and create groups and record data for multiple feeds at once ## Why Jentic - **Setup:** Wiring Adafruit IO by hand means provisioning an AIO key, keying every path to your username, and threading the key through each feed and data call. Install Jentic One once, import the API from the Jentic API Directory, and store the credential once for your agent to reuse. - **Permission scoping:** Scope your agent to read-only data operations, and, because the feed key is a path parameter, restrict it to specific feeds. You decide which operations are callable, so an agent can read values without creating or deleting feeds. - **Credential handling:** Your Adafruit IO key is stored once, encrypted, by your own Jentic One instance and injected only at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents find Adafruit IO through Jentic's intent search: a query such as 'log IoT sensor data to a feed' matches the feed and data operations, which the agent then calls with your stored credential. ## Related APIs - **Particle** — IoT device management and data platform for connected products - **PubNub** — Realtime messaging and streaming for connected devices - **Zapier** — Automation across thousands of apps ## FAQ ### What can an AI agent do with the Adafruit IO API? An agent can create feeds, push data records from devices or sensors, read the latest value, history, and chart data, record data in batches, and organize feeds into groups. It covers storing and retrieving IoT time-series data. ### How does the Adafruit IO API authenticate? It authenticates with an API key sent in an X-AIO-Key header on each request. Jentic injects the key at execution time so it stays out of the agent's context. ### Can I limit what my agent is allowed to do with the Adafruit IO API? Yes. Your Jentic One instance decides which operations an agent may call, so you can allow read-only data access while withholding feed creation and writes. Because the feed key is a path parameter, you can also restrict an agent to specific feeds. ### Does the Adafruit IO API have rate limits? Yes. Data-modifying actions count against a rate limit of 30 requests per minute on the free tier and 60 per minute on IO+. Plan an agent's write frequency to stay within your tier. ### How do I connect the Adafruit IO API to my AI agent with Jentic? Install Jentic One with its setup script, import the Adafruit IO API from the Jentic API Directory, and store your key once. Your agent can then call the feed and data operations you allow.