Apache Curator
Apache Curator is a Java/JVM client library for Apache ZooKeeper, governed by the Apache Software Foundation, that provides a high-level API framework, fluent builders, and pre-built distributed coordination recipes including leader election, distributed locks, barriers, caches, counters, and service discovery. It significantly simplifies writing reliable distributed applications.
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 Curator the way a machine reads it — 40 machine-readable artifacts 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 — Apache Curator scores 46.7/100 (developing), with a separate agent-readiness read of 7/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 Apache Curator
Each block below is one kind of artifact we hold for Apache Curator. 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.
Apache Curator
Curator provides a high-level Java API with fluent builders for ZooKeeper operations, along with pre-built recipes for leader election, distributed locks (shared, reentrant, rea...
Pricing 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 Curator 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 Curator Finops
FINOPSFeatures 8
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.
High-Level ZooKeeper Client
Wraps the raw ZooKeeper client with connection management, retry policies, and error handling for reliable distributed coordination.
Fluent Builder API
Provides a chainable, readable Java DSL for all ZooKeeper CRUD operations including watchers, transactions, and ACLs.
Distributed Coordination Recipes
Pre-built implementations of distributed patterns: leader election, locks, semaphores, barriers, counters, queues, and group membership.
Service Discovery
curator-x-discovery provides a ZooKeeper-based service registry and discovery mechanism with instance registration and lookup.
Asynchronous DSL
curator-async provides a CompletionStage-based async API with O/R modeling and schema migration for ZooKeeper data.
Node Caching
CuratorCache provides an efficient local replica of ZooKeeper subtrees with near-real-time change notifications.
Testing Support
curator-test includes TestingServer (embedded ZooKeeper) and TestingCluster for writing reliable unit and integration tests.
Retry Policies
Configurable retry policies (ExponentialBackoff, BoundedExponentialBackoff, RetryNTimes, etc.) for handling transient failures.
Scroll within the panel for all 8 ·
Semantic 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.
Apache Curator Context
JSON-LDSpectral 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 Curator API Rules
SPECTRALJSON Schema 4
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
DistributedLock
JSON SCHEMALeaderLatchState
JSON SCHEMANodeData
JSON SCHEMAServiceInstance
JSON SCHEMAJSON Structure 4
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Apache Curator Distributed Lock Structure
JSON STRUCTUREApache Curator Leader Latch State Structure
JSON STRUCTUREApache Curator Node Data Structure
JSON STRUCTUREApache Curator Service Instance Structure
JSON STRUCTUREExamples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
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.
Use Cases 6
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.
Distributed Leader Election
Elect a single leader across a cluster for coordinating distributed workloads, using LeaderLatch or LeaderSelector recipes.
Distributed Locking
Prevent concurrent access to shared resources across JVMs using InterProcessMutex and related lock recipes.
Service Registry and Discovery
Register microservices with ZooKeeper and discover them by type using curator-x-discovery.
Distributed Configuration
Store and watch shared configuration data across a cluster with automatic change notifications via NodeCache.
Cluster Membership Tracking
Track which nodes are alive in a distributed cluster using GroupMember and PersistentNode recipes.
Distributed Counters and IDs
Generate globally unique sequential IDs or maintain shared atomic counters across a cluster.
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 ZooKeeper
Curator is built on top of ZooKeeper and requires a running ZooKeeper ensemble.
Apache Kafka
Earlier versions of Kafka used ZooKeeper (managed via Curator) for broker coordination and metadata.
Apache HBase
HBase uses ZooKeeper for master election and region server coordination, often managed via Curator.
Apache Storm
Storm uses Curator for its ZooKeeper-based cluster state management.
Spring Framework
Spring Cloud Zookeeper integrates with Apache Curator for service discovery and distributed configuration.
Maven Central
All Curator modules are published to Maven Central under org.apache.curator group ID.
Resources
Every other property we hold for Apache Curator — 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
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
← All providers · Data indexed from github.com/api-evangelist/apache-curator · machine-readable index on apis.io