Particle
Particle is an end-to-end IoT platform combining cellular and Wi-Fi connectivity, hardware modules (Photon, Boron, Tracker, B-SoM, M-SoM), firmware, and a Device Cloud. The Particle Device Cloud exposes a REST API for fleet management, device control, cloud functions and variables, webhooks and integrations, OTA firmware updates, SIM management, and customer and product administration.
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 Particle the way a machine reads it — 25 machine-readable artifacts across 17 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 — Particle scores 49.5/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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 Particle
Each block below is one kind of artifact we hold for Particle. 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 17
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.
Particle Device Cloud API
The Particle Device Cloud REST API is the primary interface to the Particle platform. Use it to claim and manage devices, list and call cloud functions, read cloud variables, su...
Particle OAuth 2.0 API
OAuth 2.0 endpoints for creating, listing, and deleting access tokens used to authenticate against the Particle Device Cloud API.
Particle Devices API
List, claim, rename, and inspect Particle devices, request remote diagnostics and vitals, and control device signal LEDs.
Particle Functions and Variables API
Invoke cloud-callable firmware functions and read cloud-exposed variables on Particle devices.
Particle Events API
Publish events from the cloud to devices and subscribe to a Server-Sent Events stream of device, product, or public events.
Particle Webhooks and Integrations API
Create and manage webhooks and integrations that forward device events to external services such as Azure IoT Hub, Google Cloud Pub/Sub, and arbitrary HTTP endpoints.
Particle Products API
Manage product fleets including importing and listing devices, configuring OAuth clients, and orchestrating OTA firmware releases across product devices.
Particle SIM Cards API
List, activate, deactivate, and inspect Particle cellular SIM cards including data usage and network status.
Particle Access Tokens API
The Access Tokens API from Particle — 3 operation(s) for access tokens.
Particle Clients API
The Clients API from Particle — 2 operation(s) for clients.
Particle Devices API
The Devices API from Particle — 5 operation(s) for devices.
Particle Diagnostics API
The Diagnostics API from Particle — 3 operation(s) for diagnostics.
Particle Oauth API
The Oauth API from Particle — 1 operation(s) for oauth.
Particle Products API
The Products API from Particle — 2 operation(s) for products.
Particle Serial Numbers API
The Serial Numbers API from Particle — 1 operation(s) for serial numbers.
Particle Sims API
The Sims API from Particle — 3 operation(s) for sims.
Particle User API
The User API from Particle — 2 operation(s) for user.
Scroll within the panel for all 17 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Particle Cloud API
OPEN COLLECTIONPricing 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.
Particle Io 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.
Particle Io Finops
FINOPSSecurity Posture 3
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 Particle — 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
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 4
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/particle-io · machine-readable index on apis.io