What authentication does the Adafruit IO REST API use?

The API supports an X-AIO-Key API key, in either the request header or query string, and an X-AIO-Signature header for signed requests. Through Jentic, both values are stored encrypted in your Jentic One instance and the agent receives a scoped execution handle, so the raw key and signature never appear in prompts.

Can I create dashboards and blocks with the Adafruit IO REST API?

Yes. POST /{username}/dashboards creates a dashboard, and POST /{username}/dashboards/{dashboard_id}/blocks adds chart, gauge, or toggle blocks tied to specific feeds. The full block lifecycle (create, update, delete) is exposed under /{username}/dashboards/{dashboard_id}/blocks/{id}.

What are the rate limits for the Adafruit IO REST API?

Adafruit IO enforces a per-minute throughput cap that depends on the account tier. Use GET /{username}/throttle to read your current remaining capacity, and prefer batch ingest via /{username}/feeds/{feed_key}/data/batch over single-point posts to stay within budget.

How do I create an Adafruit IO dashboard through Jentic?

Run pip install jentic, search Jentic for 'create an Adafruit IO dashboard', load the schema for POST /{username}/dashboards, and execute it with a name. Then chain a search for 'add a block to an Adafruit IO dashboard' to load POST /{username}/dashboards/{dashboard_id}/blocks. Jentic injects the X-AIO-Key from the vault.

Does the Adafruit IO REST API support data retention rules?

Yes. The /{username}/feeds/{feed_key}/data/retain endpoint configures retention behaviour for a feed - useful when you want long-term storage for some feeds but not others, or when you need to cap storage for a constrained tier.

Can I limit what my agent is allowed to do with the Adafruit IO REST API?

Yes. Because you run Jentic One yourself, your own rules decide which Adafruit IO operations and credentials the agent may use, and only the operations you allow are callable. Adafruit IO puts the feed key in the URL path (/{username}/feeds/{feed_key}/...), so a rule can pin the agent to a single feed, letting it batch data into that feed via /{username}/feeds/{feed_key}/data/batch and read its chart via /data/chart and nothing else. Operations are opt-in, so creating dashboards through /{username}/dashboards or adding blocks is not available to the agent unless you explicitly include them.