Arduino
Arduino is an open-source electronics platform providing hardware, software, and cloud services for IoT development. The Arduino IoT Cloud REST API enables developers to programmatically manage devices, Things, dashboards, properties, and time-series data in the Arduino Cloud ecosystem. The API uses OAuth2 client credentials for authentication and returns JSON-encoded responses with standard HTTP status codes. SDKs are available in JavaScript, Python, and Go, generated automatically from an OpenAPI specification.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Arduino the way a machine reads it — 56 machine-readable artifacts across 47 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Arduino scores 54.3/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Arduino
Each block below is one kind of artifact we hold for Arduino. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 47
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Arduino binaries_v2 API
The binaries_v2 API from Arduino — 1 operation(s) for binaries_v2.
Arduino cleanup API
The cleanup API from Arduino — 1 operation(s) for cleanup.
Arduino clients_v1 API
The clients_v1 API from Arduino — 4 operation(s) for clients_v1.
Arduino compact_dashboards_v2 API
The compact_dashboards_v2 API from Arduino — 1 operation(s) for compact_dashboards_v2.
Arduino compact_devices_v2 API
The compact_devices_v2 API from Arduino — 1 operation(s) for compact_devices_v2.
Arduino compact_things_v2 API
The compact_things_v2 API from Arduino — 1 operation(s) for compact_things_v2.
Arduino compact_triggers_v1 API
The compact_triggers_v1 API from Arduino — 1 operation(s) for compact_triggers_v1.
Arduino dashboard_shares_v1 API
The dashboard_shares_v1 API from Arduino — 1 operation(s) for dashboard_shares_v1.
Arduino dashboards_v2 API
The dashboards_v2 API from Arduino — 8 operation(s) for dashboards_v2.
Arduino dashboards_v3 API
The dashboards_v3 API from Arduino — 4 operation(s) for dashboards_v3.
Arduino devices_tags_v2 API
The devices_tags_v2 API from Arduino — 1 operation(s) for devices_tags_v2.
Arduino devices_v2 API
Provides a set of endpoints to manage user devices
Arduino devices_v2_certs API
Provides a set of endpoints to manage the certs of a device
Arduino devices_v2_metadata API
Provides a set of endpoints to manage the metadata of a device
Arduino devices_v2_ota API
The devices_v2_ota API from Arduino — 2 operation(s) for devices_v2_ota.
Arduino devices_v2_pass API
Provides a set of endpoints to manage the password of a device
Arduino devices_v2_pubkeys API
Provides a set of endpoints to manage the pubkeys of a device
Arduino devices_v2_tags API
The devices_v2_tags API from Arduino — 2 operation(s) for devices_v2_tags.
Arduino devices_v2_webhooks API
The devices_v2_webhooks API from Arduino — 2 operation(s) for devices_v2_webhooks.
Arduino Iot API
The Iot API from Arduino — 4 operation(s) for iot.
Arduino lora_app_v1 API
The lora_app_v1 API from Arduino — 2 operation(s) for lora_app_v1.
Arduino lora_apps_v1 API
The lora_apps_v1 API from Arduino — 1 operation(s) for lora_apps_v1.
Arduino lora_devices_v1 API
The lora_devices_v1 API from Arduino — 1 operation(s) for lora_devices_v1.
Arduino lora_freq_plan_v1 API
The lora_freq_plan_v1 API from Arduino — 1 operation(s) for lora_freq_plan_v1.
Arduino lora_gw_v1 API
The lora_gw_v1 API from Arduino — 4 operation(s) for lora_gw_v1.
Arduino manage API
A set of api to manage resources externally
Arduino network_credentials_v1 API
The network_credentials_v1 API from Arduino — 2 operation(s) for network_credentials_v1.
Arduino ota API
The ota API from Arduino — 1 operation(s) for ota.
Arduino properties API
The properties API from Arduino — 1 operation(s) for properties.
Arduino properties_v2 API
The properties_v2 API from Arduino — 7 operation(s) for properties_v2.
Arduino property_types_v1 API
The property_types_v1 API from Arduino — 1 operation(s) for property_types_v1.
Arduino series_v1 API
The series_v1 API from Arduino — 5 operation(s) for series_v1.
Arduino series_v2 API
The series_v2 API from Arduino — 5 operation(s) for series_v2.
Arduino supported_v1 API
The supported_v1 API from Arduino — 1 operation(s) for supported_v1.
Arduino sync_v1 API
The sync_v1 API from Arduino — 2 operation(s) for sync_v1.
Arduino templates API
The templates API from Arduino — 1 operation(s) for templates.
Arduino thing_properties_v1 API
The thing_properties_v1 API from Arduino — 6 operation(s) for thing_properties_v1.
Arduino things_tags_v2 API
The things_tags_v2 API from Arduino — 1 operation(s) for things_tags_v2.
Arduino things_v1 API
Provides a set of endpoints to manage the things of a user
Arduino things_v1_tags API
The things_v1_tags API from Arduino — 2 operation(s) for things_v1_tags.
Arduino things_v2 API
The things_v2 API from Arduino — 7 operation(s) for things_v2.
Arduino things_v2_tags API
The things_v2_tags API from Arduino — 2 operation(s) for things_v2_tags.
Arduino timezones API
The timezones API from Arduino — 1 operation(s) for timezones.
Arduino triggers_v1 API
Provides a set of endpoints to manage the triggers of a user
Arduino usage_internal API
The usage_internal API from Arduino — 1 operation(s) for usage_internal.
Arduino usage_v1 API
The usage_v1 API from Arduino — 4 operation(s) for usage_v1.
Arduino users_v1 API
The users_v1 API from Arduino — 3 operation(s) for users_v1.
Scroll within the panel for all 47 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Arduino Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Arduino Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Arduino Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Arduino API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Arduino IoT Cloud API Schemas
JSON SCHEMAExamples 1
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Arduino Iot Cloud Examples
EXAMPLESecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Arduino — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/arduino · machine-readable index on apis.io