Apache ZooKeeper
Apache ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services for distributed systems. It provides a hierarchical key-value store (znodes), watches for change notifications, ephemeral nodes for presence detection, and sequential nodes for leader election and distributed locking. ZooKeeper exposes a Java/C client API and an HTTP Admin Server API for monitoring and management. It is widely used by Kafka, Hadoop, HBase, Storm, and other distributed systems.
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 Apache ZooKeeper the way a machine reads it — 32 machine-readable artifacts across 6 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 ZooKeeper scores 49.7/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 Apache ZooKeeper
Each block below is one kind of artifact we hold for Apache ZooKeeper. 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 6
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 ZooKeeper Client API
The ZooKeeper client API provides Java and C language bindings for distributed coordination operations. Operations include create (create znodes), delete, exists (check existenc...
Apache ZooKeeper Cluster API
Cluster and ensemble information
Apache ZooKeeper Configuration API
Server configuration information
Apache ZooKeeper Health API
Server health checks
Apache ZooKeeper Monitoring API
Server statistics and metrics
Apache ZooKeeper Watches API
ZooKeeper watch information
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 ZooKeeper Admin Server 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 Zookeeper 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 Zookeeper Finops
FINOPSFeatures 7
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.
Hierarchical Namespace
Tree-structured znode namespace similar to a filesystem for organized configuration storage.
Watch Notifications
Client watches on znodes trigger one-time callbacks on change events for reactive patterns.
Ephemeral Nodes
Nodes that disappear when the creating client session expires for presence detection.
Sequential Nodes
Auto-incrementing sequential znodes for implementing distributed queues and leader election.
Atomic Operations
Compare-and-set and multi-operation batches for consistent distributed state updates.
ACL Security
Per-znode access control lists for authentication and authorization of znode operations.
Observer Mode
Read-only observer servers for scaling read throughput without affecting write quorum.
Scroll within the panel for all 7 ·
Spectral 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.
Apache ZooKeeper API Rules
SPECTRALSecurity 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 5
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.
Leader Election
Distributed leader election using ephemeral sequential znodes for coordination.
Distributed Configuration Management
Centralized configuration storage with watch-based change notification to services.
Service Registry and Discovery
Service registration and lookup using ephemeral znodes as presence indicators.
Distributed Locking
Distributed mutex and read/write locks using ephemeral sequential znode recipes.
Cluster Coordination
Kafka broker coordination, HBase region server management, and Hadoop NameNode fencing.
Integrations 6
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
ZooKeeper (legacy) for Kafka broker metadata and controller election (replaced by KRaft).
Apache HBase
ZooKeeper for HBase region server coordination and master election.
Apache Hadoop
ZooKeeper for HDFS NameNode HA fencing and YARN ResourceManager HA.
Apache Storm
ZooKeeper for Storm Nimbus coordination and worker heartbeat tracking.
Apache Solr
ZooKeeper for SolrCloud cluster coordination, configuration, and leader election.
Apache Curator
High-level ZooKeeper client with recipes for common distributed patterns.
Resources
Every other property we hold for Apache ZooKeeper — 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
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 3
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
← All providers · Data indexed from github.com/api-evangelist/apache-zookeeper · machine-readable index on apis.io