Apache Storm
Apache Storm is a free and open-source distributed real-time computation system that makes it easy to reliably process unbounded streams of data at scale. It provides a simple programming model (topologies with spouts and bolts), guaranteed message processing, horizontal scalability, and fault tolerance. Storm integrates with queuing and database technologies including Apache Kafka and Apache Cassandra and is governed by the Apache Software Foundation.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Apache Storm the way a machine reads it — 31 machine-readable artifacts across 9 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 — Apache Storm scores 40.7/100 (thin), 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 Apache Storm
Each block below is one kind of artifact we hold for Apache Storm. 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 9
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.
Apache Storm Topology API
The Storm Topology API provides Java and other language bindings for building real-time processing topologies composed of spouts (data sources) and bolts (processing units). It ...
Apache Storm Cluster API
The Cluster API from Apache Storm — 2 operation(s) for cluster.
Apache Storm Drpc API
The Drpc API from Apache Storm — 2 operation(s) for drpc.
Apache Storm History API
The History API from Apache Storm — 1 operation(s) for history.
Apache Storm Nimbus API
The Nimbus API from Apache Storm — 1 operation(s) for nimbus.
Apache Storm Owner Resources API
The Owner Resources API from Apache Storm — 1 operation(s) for owner resources.
Apache Storm Supervisor API
The Supervisor API from Apache Storm — 2 operation(s) for supervisor.
Apache Storm Topology API
The Topology API from Apache Storm — 14 operation(s) for topology.
Apache Storm Topology Workers API
The Topology Workers API from Apache Storm — 1 operation(s) for topology workers.
Scroll within the panel for all 9 ·
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).
Apache Storm UI REST 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.
Apache Storm 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.
Apache Storm Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Guaranteed Message Processing
At-least-once processing guarantees through ack/fail tracking mechanism.
Scalable Topologies
Horizontally scalable stream processing topologies with configurable parallelism.
Trident API
High-level micro-batch processing abstraction with stateful streaming and exactly-once semantics.
DRPC
Distributed Remote Procedure Calls for synchronous distributed computation.
Windowing Operations
Tumbling and sliding window processing over bounded time or count windows.
Multi-Language Support
Topology components written in Java, Python, Ruby, and other languages via Multilang protocol.
Security Posture 2
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.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Real-Time Analytics
Continuous computation over live event streams for operational dashboards.
ETL Processing
Real-time data transformation and enrichment pipelines.
Machine Learning Scoring
Online scoring of ML models against streaming feature data.
Fraud Detection
Low-latency fraud detection rules applied to transaction streams.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Apache Kafka
Kafka Spout for consuming messages from Kafka topics as Storm data sources.
Apache Cassandra
CassandraBolt for writing processed stream data to Cassandra.
Apache Hive
HiveBolt for streaming inserts into Apache Hive tables.
Redis
Redis integration for stateful lookups and caching in Storm bolts.
Elasticsearch
ElasticsearchBolt for indexing stream data into Elasticsearch.
Resources
Every other property we hold for Apache Storm — 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 2
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
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/apache-storm · machine-readable index on apis.io