Adafruit IO API APIs
3 APIs160 Endpoints1 Category
Categories
API Catalog
Adafruit IO API
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.
18 endpointsAdafruit IO REST API
Jentic publishes the only available OpenAPI specification for Adafruit IO REST API, keeping it validated and agent-ready. The Adafruit IO REST API exposes the full IoT platform surface — feeds, dashboards and blocks, groups, throttle status, activities, charts, and signed-request authentication. The spec covers 71 endpoints and supports both header and query API key auth (X-AIO-Key) plus an X-AIO-Signature scheme for signed requests. Endpoints under /{username}/feeds include chart, batch, retain, previous, next, first, and last data accessors for finely controlled telemetry retrieval.
71 endpointsAdafruit IO REST API
Adafruit IO is the cloud service paired with Adafruit's maker hardware, used to log sensor data, build dashboards, and trigger automations from connected devices. This REST API exposes feeds, dashboards, blocks, groups, triggers, tokens, ACL, throttle status, and webhook endpoints across 71 operations. Authentication uses the X-AIO-Key header (or query parameter) and an optional X-AIO-Signature for signed requests. The /{username}/groups/{group_key}/feeds/{feed_key}/data/batch path supports batched ingest scoped to a group, and the /{username}/triggers resource lets devices fire automations based on feed values.
Connect Your Agent
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"find live events near a location"
# → Jentic returns the GET /events tool with parameter schema, agent executes.