Adafruit IO API

Name: Adafruit IO API API
Brand: Adafruit IO API
Availability: InStock

★ Only Publicly Available SpecIOTSensor DataapiKey18 EndpointsREST

For Agents

Read and write sensor telemetry, manage feeds and groups, and look up account data on Adafruit IO.

Quickstart

Get started with Adafruit IO API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"read the latest value from an Adafruit IO feed"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Adafruit IO API API.

Create and list feeds for sensor telemetry via /{username}/feeds

Read the latest data point from a feed at /{username}/feeds/{feed_key}/data/last

Submit batch sensor readings to a feed via /{username}/feeds/{feed_key}/data/batch

Pull historical feed data through /{username}/feeds/{feed_key}/data and /{username}/feeds/{feed_key}/data/{id}

GET STARTED

Start building with Adafruit IO API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Adafruit IO API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Adafruit IO API, keeping it validated and agent-ready. Adafruit IO is a cloud service for connected devices and the Internet of Things, exposing endpoints for feeds, groups, batched data points, and the authenticated user. The spec covers 18 operations under three tags — feeds, groups, and user — with the API key passed in the X-AIO-Key header. Feeds support last-value reads and batch ingest, which suit microcontroller-based projects that buffer telemetry.

Use Cases

Patterns agents use Adafruit IO API API for, with concrete tasks.

★ Microcontroller telemetry ingest

Hobbyist and educational IoT projects use Adafruit IO to log sensor data from a Feather, ESP32, or Raspberry Pi. The microcontroller (or an agent on its behalf) creates feeds via /{username}/feeds and posts readings in batches to /{username}/feeds/{feed_key}/data/batch. Batch ingest reduces the number of TLS handshakes a memory-constrained device has to perform.

POST a batch of 30 temperature readings to /{username}/feeds/temp/data/batch and confirm the count in the response

Live dashboard polling

Smart-home and weather-station dashboards poll Adafruit IO for the latest values. An agent or front-end calls /{username}/feeds/{feed_key}/data/last for each feed in the dashboard and renders the result. Grouping related feeds via /{username}/groups simplifies the read pattern to a single group key per panel.

Fetch the last value of each feed in group 'weather-station' and render a dashboard summary

Historical analysis

Researchers and tinkerers analyse historical sensor data — for example averaging temperature over a week or charting humidity trends. An agent can pull /{username}/feeds/{feed_key}/data with a date range, aggregate the values, and feed them into a notebook or analytics tool. This avoids exporting CSVs by hand from the Adafruit IO UI.

GET /{username}/feeds/temp/data with start_time and end_time and compute the daily average

AI agent integration

Makers building agent assistants for their lab or smart home wire Adafruit IO into Jentic alongside notification APIs. The X-AIO-Key lives in the Jentic vault and the agent searches by intent — e.g. 'read the latest soil moisture' — without juggling raw keys in the conversation context.

Search Jentic for 'read latest Adafruit IO feed value', load the schema, and execute it for feed_key 'soil-moisture'

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for adafruit io api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/{username}/feeds

List feeds

POST

/{username}/feeds

Create a feed

POST

/{username}/feeds/{feed_key}/data

Add a data point

POST

/{username}/feeds/{feed_key}/data/batch

Batch add data points

GET

/{username}/feeds/{feed_key}/data/last

Get the latest data point

GET

/{username}/feeds/{feed_key}/data

Get historical feed data

GET

/{username}/groups

List groups

GET

/{username}/user

Get authenticated user

GET

/{username}/feeds

List feeds

POST

/{username}/feeds

Create a feed

POST

/{username}/feeds/{feed_key}/data

Add a data point

POST

/{username}/feeds/{feed_key}/data/batch

Batch add data points

GET

/{username}/feeds/{feed_key}/data/last

Get the latest data point

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Adafruit IO X-AIO-Key values are stored encrypted in the Jentic vault. Agents receive scoped execution handles, so the raw key never enters the agent's prompt context or logs.

Intent-based discovery

Agents search Jentic by intent, e.g. 'read latest Adafruit IO feed' or 'send a batch of sensor readings', and Jentic returns the matching operation with its input schema.

Time to first call

Direct Adafruit IO integration: a few hours for auth and feed wiring. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Particle API

End-to-end IoT platform with hardware, cloud, and OTA firmware updates.

Choose Particle when the project needs over-the-air firmware updates and SIM connectivity, which Adafruit IO does not provide.

Alternative

Blynk API

Mobile-first IoT platform with drag-and-drop dashboard builder.

Pick Blynk when end users will primarily interact via a mobile app rather than the Adafruit IO web UI.

Complementary

Adafruit IO REST API

Wider 71-endpoint Adafruit IO REST surface including dashboards, blocks, and webhooks.

Use the larger Adafruit IO REST API when you need dashboard, block, or webhook management beyond feeds and groups.

FAQs

Specific to using Adafruit IO API API through Jentic.

Why is there no official OpenAPI spec for Adafruit IO API?

Adafruit IO does not publish an OpenAPI specification in this trimmed shape. Jentic generates and maintains this spec so that AI agents and developers can call Adafruit IO API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Adafruit IO API use?

Adafruit IO uses an API key in the X-AIO-Key header, generated from the user's Adafruit IO profile page. Through Jentic, the X-AIO-Key value is stored encrypted in the Jentic vault and the agent receives a scoped execution handle, so raw keys never appear in prompts.

Can I send batch sensor readings with the Adafruit IO API?

Yes. POST to /{username}/feeds/{feed_key}/data/batch with an array of data points to ingest several readings in a single request. This reduces the number of TLS handshakes a memory-constrained microcontroller has to perform compared with single-point POSTs.

What are the rate limits for the Adafruit IO API?

Adafruit IO enforces a per-minute data throughput limit that depends on the account tier (free vs IO Plus). The OpenAPI spec does not declare exact numbers — see Adafruit's IO docs for the current ceiling, and use batch ingest to stay within budget.

How do I read the latest sensor value through Jentic?

Run pip install jentic, search Jentic for 'read latest Adafruit IO feed', load the schema for GET /{username}/feeds/{feed_key}/data/last, and execute it with the username and feed_key. Jentic injects the X-AIO-Key from the vault.

Does the Adafruit IO API support grouping multiple feeds?

Yes. /{username}/groups lets you create and list groups, and a feed can be associated with a group so that related feeds (e.g. all sensors on a weather station) can be queried as a single unit.