Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

API DirectoryBrowse 10,000+ APIs ready for AI agent integration API ScorecardAssess your APIs for AI-readiness with automated scoring Agentic SandboxSafely simulate AI agents with your production APIs Jentic MiniFree, self-hosted API execution layer for AI agents

CAPABILITIES

IntegrationConnect AI agents to your existing systems WorkflowsDiscover and capture successful agent workflows GovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentation Arazzo EditorBuild and edit multi-step API workflows visually

Developers

GET STARTED

DocumentationGuides and API reference QuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples

Resources

BlogLatest articles and insights Press & MediaBrand assets and press contact Open StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.

Company

About UsOur mission and team CareersJoin our team ContactGet in touch

Sign in Book a Demo

How Jentic Works API Directory API Scorecard Agentic Sandbox Jentic Mini Integration Workflows Governance Arazzo UI Arazzo Editor

Documentation Quickstart GitHub

Blog Press & Media Open Standards Newsletter

About Us Careers Contact

Request a demo Sign Up

Sign up for exclusive Jentic updates

Website

For Developers

Docs
GitHub

Company

About
Blog
Careers
Contact us

© 2026 Jentic. All rights reserved.

Terms & Conditions•Privacy Policy•

IOT APIs | Jentic

APIs/IOT

IOT APIs

Explore APIs in this category. Connect any of them to your AI agent through Jentic.

Browse IOT APIs

Filters

Developer Tools

Communications

Data Enrichment

E Commerce

Productivity

CRM

Payments

Marketing

Media

Finance

Identity Auth

AI/ML

Cloud Infrastructure

Analytics

Security

HR recruiting

Maps Geolocation

Storage

IOT

Healthcare

Education

Social Media

Government

Fintech

Transportation

Business Operations

Collaboration

Gaming

Data Intelligence

Business Tools

Communication

Data

Artificial Intelligence

Backend As A Service

Media Content

Health Fitness

Content Management

Advertising

Project Management

Sales

Email Marketing

Events

Mapping

Reference Data

Business Intelligence

Hospitality

Legal Government

Incident Management

Supply Chain

Business Data

Business

Logistics

Workforce Management

Data Extraction

Human Resources

Design Collaboration

Marketing Advertising

Lifestyle

Payments Fintech

Unknown

Blockchain

Monitoring

Automation

Devops

Geospatial

Database

Hr

Networking

Commerce

A-Z

Most Popular

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs, connect in minutes via MCP, OpenClaw, or Python. One SDK, one credential — every API your agent needs.

1NCE API

Jentic publishes the only available OpenAPI specification for 1NCE API, keeping it validated and agent-ready. The 1NCE API gives developers programmatic control over cellular IoT connectivity, including activating SIMs, querying data and SMS quotas, sending SMS to devices, and triggering connectivity resets across a global cellular network. It exposes 25 endpoints covering SIM lifecycle management, order placement for new SIM cards, product catalog access, usage reporting, and support service requests. The API is designed for fleet operators running embedded devices, asset trackers, and industrial sensors that need lightweight cellular data plans with predictable pricing.

1NCE API

Jentic publishes the only available OpenAPI specification for 1NCE API, keeping it validated and agent-ready. The 1NCE API provides programmatic management of IoT SIM cards, connectivity, and data quotas for large-scale IoT deployments. It covers SIM lifecycle operations including activation, deactivation, top-ups, SMS handling, and real-time connectivity diagnostics across 25 endpoints. The API also supports order management, product catalog access, and customer support ticket creation for 1NCE's flat-rate IoT connectivity platform.

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.

Adafruit IO API

Jentic publishes the only available OpenAPI specification for Adafruit IO API, keeping it validated and agent-ready. Adafruit IO is a hosted IoT data platform that lets makers and small fleets push sensor readings into named feeds, group feeds together, and read history back for dashboards or downstream automation. This compact 13-endpoint surface focuses on the core data path: list and create feeds, publish single or batch data points, fetch the last reading, chart historical data, and group feed updates into one call.

Adafruit 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.

Adafruit 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.

Adafruit IO REST API

Jentic publishes the only available OpenAPI specification for Adafruit IO REST API, keeping it validated and agent-ready. Adafruit IO is a hosted IoT platform built around named feeds, dashboards, blocks, and groups, and the full REST surface exposes 71 endpoints covering account info, throttle and activity inspection, feed and data operations, dashboard layout, and webhook-style triggers. It is the broadest programmatic surface on the platform and pairs with hobbyist hardware such as the Feather, QT Py, and Raspberry Pi over HTTP or MQTT.

AGCO Aftermarket Tools Service API

AGCO Aftermarket Tools Service (ATS) is the dealer-facing API for AGCO's agricultural equipment service ecosystem — tractors, engines, ECUs, and aftermarket diagnostic tools across the Massey Ferguson, Fendt, Valtra, and Challenger brands. The 163-path surface covers engine and ECU records by serial number, license activations and authorization codes for diagnostic tooling, dealer client and user administration, software releases and update groups, content submissions and translation sets, and a reporting layer for service operations.

Alexa For Business

Jentic publishes the only available OpenAPI specification for Alexa For Business, keeping it validated and agent-ready. Alexa for Business gives organisations programmatic control over Alexa devices deployed in conference rooms, hotels, and shared workspaces. The API exposes 93 operations covering rooms, profiles, devices, contacts, address books, skills, skill groups, gateways, and network profiles, plus user enrolment and meeting room management. Note that AWS deprecated the Alexa for Business service in 2023; this catalogue entry remains for legacy fleet operations and migration tooling.

Allegion Credentialing API

Jentic publishes the only available OpenAPI specification for Allegion Credentialing API, keeping it validated and agent-ready. The Allegion Schlage Mobile Credentials API issues, lists, and revokes mobile credentials that unlock Schlage access control devices, and lets callers enumerate the devices in their fleet. Authentication combines a subscription key in the alle-subscription-key header with HTTP basic auth, reflecting Allegion's enterprise integration model. The API is small and focused on the credential lifecycle rather than user management or door-event reporting.

Amazon SageMaker Edge Manager

Jentic publishes the only available OpenAPI specification for Amazon SageMaker Edge Manager, keeping it validated and agent-ready. SageMaker Edge Manager is the dataplane for active edge agents — it lets registered devices fetch their assigned model deployments, send periodic heartbeats with telemetry, and report registration metadata back to the SageMaker control plane. This API is consumed by the Edge Manager agent on each device, not typically called directly by application code, but it is the protocol that drives over-the-air model updates on edge fleets. Note that AWS announced SageMaker Edge Manager is on a deprecation path, so check current status before adopting.

Ambient Weather API

The Ambient Weather API exposes data from personal weather stations connected to the Ambient Weather network. Two GET endpoints let an integration list the stations linked to an account and pull historical or near-real-time observations from a specific station by MAC address. Authentication uses paired query-string keys (applicationKey identifying the integration plus apiKey identifying the user) sent against rt.ambientweather.net/v1. Typical consumers are home-automation dashboards, hyperlocal weather services, and research projects that piggyback on the network's hardware.

AWS Greengrass

Jentic publishes the only available OpenAPI specification for AWS Greengrass, keeping it validated and agent-ready. AWS IoT Greengrass extends AWS onto edge devices so they can run Lambda functions, machine learning inference, and local messaging while staying connected to the cloud for management and analytics. The Greengrass v1 control-plane API manages groups, cores, devices, function definitions, subscription tables, resource definitions, and deployments across 92 operations. It is the orchestration layer for fleet-wide configuration of Greengrass cores running at the edge.

AWS IoT 1-Click Devices Service

Jentic publishes the only available OpenAPI specification for AWS IoT 1-Click Devices Service, keeping it validated and agent-ready. The IoT 1-Click Devices API manages the lifecycle of single-purpose, button-style hardware — claiming devices into an AWS account, querying their methods and events, enabling or disabling them, and unclaiming them when they are returned. With 13 operations it is the device-side counterpart to the 1-Click Projects API used to wire devices into application workflows.

AWS IoT 1-Click Projects Service

Jentic publishes the only available OpenAPI specification for AWS IoT 1-Click Projects Service, keeping it validated and agent-ready. The IoT 1-Click Projects API defines projects and placements that map physical 1-Click devices to specific business workflows — for example, a button at a hotel front desk that triggers a housekeeping request. The API manages projects, placements, device template associations, and per-placement attributes across 16 operations and is the application-side counterpart to the 1-Click Devices API.

AWS IoT Data Plane

Jentic publishes the only available OpenAPI specification for AWS IoT Data Plane, keeping it validated and agent-ready. The IoT Data Plane API is the runtime surface for publishing MQTT messages, reading and updating device shadows, and managing retained messages on AWS IoT Core. It is a focused 7-endpoint API used by applications and backend services that interact with the live state of connected devices rather than configuring the IoT Core platform itself.

AWS IoT Events

Jentic publishes the only available OpenAPI specification for AWS IoT Events, keeping it validated and agent-ready. AWS IoT Events monitors equipment and device fleets for failures or changes in operation by running detector models — state machines that react to incoming telemetry inputs. The control-plane API manages inputs, detector models, alarm models, model versions, and detector model analyses across 26 operations. It is the configuration surface for setting up event-driven automation on top of IoT telemetry.

AWS IoT Jobs Data Plane

Jentic publishes the only available OpenAPI specification for AWS IoT Jobs Data Plane, keeping it validated and agent-ready. AWS IoT Jobs are remote operations — firmware updates, reboots, certificate rotations, configuration pushes — sent to one or more devices connected to AWS IoT. The Jobs Data Plane is the device-facing runtime API that lets devices fetch their pending job executions, mark them in progress, and report success or failure. It is a small 4-endpoint surface focused entirely on the device side of the job lifecycle.

AWS IoT SiteWise

Jentic publishes the only available OpenAPI specification for AWS IoT SiteWise, keeping it validated and agent-ready. AWS IoT SiteWise is a managed service that collects, organises, and analyses data from industrial equipment at scale. It models physical assets such as wind turbines, production lines, and chemical reactors as digital twins, ingests time-series property values from MQTT or OPC-UA gateways, and exposes the data through 73 endpoints covering assets, asset models, properties, gateways, portals, and dashboards. The service runs aggregations on the fly and supports SiteWise Monitor portals so operators can browse live and historical metrics without standing up custom dashboards.

AzureDigitalTwinsManagementClient

Jentic publishes the only available OpenAPI specification for AzureDigitalTwinsManagementClient, keeping it validated and agent-ready. The Azure Digital Twins management API provisions DigitalTwinsInstance resources, attaches event endpoints (Event Grid, Event Hubs, Service Bus), and links integration resources such as IoT Hubs to a twin graph. It is the control plane for setting up the modelling environment in which a digital twin of a physical environment lives, distinct from the data plane that runs queries against twins.

Balena Cloud API

Jentic publishes the only available OpenAPI specification for Balena Cloud API, keeping it validated and agent-ready. Deploy and manage containerized applications across fleets of Linux single-board computers using an OData-based REST API with 82 endpoints. The API covers fleet (application) management, device provisioning and state control, release tracking, environment variable configuration, tagging, API key management, and organization administration — all queryable with $filter, $select, $expand, $orderby, $top, and $skip operators.

BippyBox API

Jentic publishes the only available OpenAPI specification for BippyBox API, keeping it validated and agent-ready. BippyBox is a small IoT notification device that plays a short audio clip and lights an LED in a chosen colour when triggered over the internet. The HTTP API exposes two operations: one to read the user's account data including the list of registered devices, and one to send a notification to a specific BippyBox by combining a sound, a colour, and an optional message. Authentication is a static x-uid header tied to a single user account.

Blues Notehub API

Jentic publishes the only available OpenAPI specification for Blues Notehub API, keeping it validated and agent-ready. Notehub is the Blues cloud service for managing cellular IoT devices built around the Notecard module. The API exposes projects, products, fleets, devices, events, routes, monitors, billing accounts, and usage data, letting integrators provision new devices, group them into fleets, push environment variables, and route incoming Notes to downstream cloud services. Authentication uses Bearer tokens obtained from /oauth2/token using a Personal Access Token or OAuth client credentials.

Blues Notehub API

Jentic publishes the only available OpenAPI specification for Blues Notehub API, keeping it validated and agent-ready. This blues.io listing covers the broader 81-endpoint Notehub surface, including projects, products, fleets, devices, notes, events, routes, monitors, environment variables, firmware updates, billing accounts, and usage data. Notehub is the cloud counterpart to the Blues Notecard cellular module, and the API supports remote firmware delivery, per-device enable and disable, and full lifecycle management for cellular IoT deployments. Authentication uses Bearer tokens obtained from /oauth2/token.

Blynk Cloud Device HTTPS API

Jentic publishes the only available OpenAPI specification for Blynk Cloud Device HTTPS API, keeping it validated and agent-ready. Blynk is an IoT platform with mobile and web dashboards, and the Device HTTPS API lets external systems read and write datastream values, log custom events, query historical data, and check whether a hardware device is currently online. Datastreams are the named virtual pins (V0, V1, etc.) that hardware writes to and dashboards read from. Authentication is per-device — each call carries a token query parameter scoped to a single Blynk device.

Bouncie API

Jentic publishes the only available OpenAPI specification for Bouncie API, keeping it validated and agent-ready. The Bouncie API gives connected-vehicle applications access to user, vehicle, and trip data for any driver who has paired a Bouncie OBD-II device. It exposes both REST endpoints for pulling data on demand and webhook subscriptions that push events such as trip start, trip end, MIL alerts, and low battery in real time. Geo-zone management endpoints let you create application-defined zones that fire programmatic events without surfacing in the user-facing Bouncie app.

Bouncie API

Jentic publishes the only available OpenAPI specification for Bouncie API, keeping it validated and agent-ready. Bouncie is a connected-vehicle platform built around an OBD-II device that streams trip, location, and diagnostic data from a user's vehicle. The API provides authenticated access to user profiles, vehicle inventories, trip histories, geo-zones, locations, and schedules, plus webhook registration for push events. Integrators register applications on the Bouncie Developer Portal and use OAuth 2.0 user authorization to access end-user vehicle data.

Brain Web API

The Brain Web API is the REST surface of Intellifi's Brain platform, a localisation system for items and assets that uses RFID and Bluetooth devices. Across 77 endpoints, the spec covers device and location management, key-value storage, presences and items, blob upload and download, events, and user-defined location rules — the core building blocks for tracking physical assets in a warehouse, retail, or logistics environment. Authentication can be a query API key, a header API key (X-Api-Key), or a session cookie, and the base URL is templated per customer Brain instance.

Carbon REST API

Jentic publishes the only available OpenAPI specification for Carbon REST API, keeping it validated and agent-ready. The Carbon REST API automates Carbon's industrial 3D printing workflow, exposing JWT-authenticated access to a fleet of connected printers, print jobs, and the underlying parts library. Agents can register a JWT, list printers and their statuses, queue and inspect print jobs, and look up parts by ID. The API is the programmatic surface for Carbon's manufacturing platform used by production additive-manufacturing teams.

ClearBlade API

ClearBlade is an industrial IoT platform, and its REST API exposes the platform's full operational surface across systems, devices, collections, code services, message-passing, and developer administration. With over 220 endpoints, the API covers everything from provisioning a new system and registering devices to running data queries, sending MQTT messages, and rotating device keys. Operations are grouped under admin, codes, data, devices, edges, and message-history namespaces, reflecting the platform's multi-tenant edge-and-cloud architecture. It is designed for industrial operators, OEMs, and IoT solution builders who need full programmatic control over a fleet.

Climate FieldView Platform APIs

The Climate FieldView Platform APIs give partners programmatic access to agronomic data captured by Climate FieldView, including field boundaries, farm organizations, planting and harvest operations, scouting observations, soil samples, and machine diagnostics. Partners can upload imagery, prescriptions, and as-applied or as-planted data, and request asynchronous exports of agronomic layers for downstream analytics. Authentication uses OAuth 2.0 authorization code grant with scoped permissions (for example fields:read, asHarvested:write) plus an X-Api-Key header that controls throttling. The platform exposes 28 endpoints anchored at platform.climate.com/v4 covering field, boundary, upload, and export workflows.

Climate FieldView Platform APIs

Jentic publishes the only available OpenAPI specification for Climate FieldView Platform APIs, keeping it validated and agent-ready. The Climate FieldView Platform APIs expose 28 endpoints for managing fields, boundaries, farm organisations, resource owners, agronomic uploads, exports, and operations for digital agriculture workflows. Authentication combines OAuth2 with a per-partner X-Api-Key header that determines a custom usage plan, with throttling enforced as 429 responses. Large agronomic data files are handled via chunked uploads in 5MiB segments up to 500MiB total, and pagination uses X-Limit and X-Next-Token headers.