NinjaBlocks
Ninja Blocks Inc was an Australian Internet-of-Things startup (founded 2012, backed by 500 Global / 500 Startups) behind the Ninja Block and Ninja Sphere home-automation hubs. It offered a cloud-connected platform with a RESTful API (base https://api.ninja.is/rest/v0/) for reading sensor data and controlling actuators, plus first-party client libraries for Node.js, PHP, Ruby, Lua and Arduino, a `ninja-toolbelt` CLI, and OAuth-based authentication. The company ceased operation and its web and API hosts are no longer online; this profile preserves the surviving first-party open-source client libraries and API tooling published to npm and GitHub. Added to the API Evangelist network from the 500 Global portfolio and enriched from public package registries and the github.com/ninjablocks organization.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles NinjaBlocks the way a machine reads it — 1 machine-readable artifact across 1 API, 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 — NinjaBlocks scores 12.5/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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 NinjaBlocks
Each block below is one kind of artifact we hold for NinjaBlocks. 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 1
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.
Ninja Blocks REST API
Historical RESTful API for the Ninja Blocks IoT platform, used to read device/sensor data and actuate devices. No longer operational; documented here from surviving first-party ...
Resources
Every other property we hold for NinjaBlocks — 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.
Build 5
SDKs, sample code, and the tooling you integrate with
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/ninjablocks · machine-readable index on apis.io