Particle
Particle is an integrated IoT Platform-as-a-Service that provides cellular, Wi-Fi, and Bluetooth hardware modules alongside a comprehensive cloud platform for building and managing connected devices at scale. The Particle Device Cloud exposes a REST API that enables developers to call device functions, read variables, publish and subscribe to events, manage firmware OTA updates, and administer product fleets. Authentication uses OAuth 2.0 bearer tokens, and the platform supports JavaScript, iOS, Android, and Windows SDKs as well as a command-line interface. Particle's pricing model is based on Data Operations consumed per month, with plans ranging from a free prototyping tier through paid block-based plans to enterprise contracts.
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 — 34 machine-readable artifacts across 25 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 54.4/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.
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 25
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 Authentication API
The Authentication API from Particle — 3 operation(s) for authentication.
Particle Configuration API
The Configuration API from Particle — 2 operation(s) for configuration.
Particle Customers API
The Customers API from Particle — 3 operation(s) for customers.
Particle Devices API
The Devices API from Particle — 9 operation(s) for devices.
Particle Diagnostics API
The Diagnostics API from Particle — 4 operation(s) for diagnostics.
Particle Env API
The Env API from Particle — 4 operation(s) for env.
Particle Events API
The Events API from Particle — 6 operation(s) for events.
Particle Firmware API
The Firmware API from Particle — 3 operation(s) for firmware.
Particle FleetHealth API
The FleetHealth API from Particle — 5 operation(s) for fleethealth.
Particle Groups API
The Groups API from Particle — 5 operation(s) for groups.
Particle Integrations API
The Integrations API from Particle — 3 operation(s) for integrations.
Particle Ledger API
The Ledger API from Particle — 6 operation(s) for ledger.
Particle Location API
The Location API from Particle — 3 operation(s) for location.
Particle Logic API
The Logic API from Particle — 7 operation(s) for logic.
Particle OAuth API
The OAuth API from Particle — 2 operation(s) for oauth.
Particle Organizations API
The Organizations API from Particle — 3 operation(s) for organizations.
Particle ProductFirmware API
The ProductFirmware API from Particle — 4 operation(s) for productfirmware.
Particle Products API
The Products API from Particle — 5 operation(s) for products.
Particle Quarantine API
The Quarantine API from Particle — 2 operation(s) for quarantine.
Particle Search API
The Search API from Particle — 2 operation(s) for search.
Particle Secrets API
The Secrets API from Particle — 2 operation(s) for secrets.
Particle ServiceAgreements API
The ServiceAgreements API from Particle — 7 operation(s) for serviceagreements.
Particle Sims API
The Sims API from Particle — 5 operation(s) for sims.
Particle Team API
The Team API from Particle — 1 operation(s) for team.
Particle User API
The User API from Particle — 2 operation(s) for user.
Scroll within the panel for all 25 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Particle IoT GraphQL Schema
This document describes a conceptual GraphQL schema for the Particle IoT platform. Particle exposes its Device Cloud capabilities primarily through a REST API at `https://api.pa...
GRAPHQLPricing 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 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 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.
Particle Context
JSON-LDSecurity 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.
Get Started 1
Portal, sign-up, and the first successful call
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 1
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 4
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 · machine-readable index on apis.io