Apache HBase
Apache HBase is an open-source, distributed, versioned, non-relational database modeled after Google's Bigtable. It provides random, real-time read/write access to big data and runs on top of Apache Hadoop HDFS, offering a REST API (Stargate), Thrift API, and Java client API for table and cell-level operations.
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 HBase the way a machine reads it — 57 machine-readable artifacts across 5 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 HBase scores 51.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 HBase
Each block below is one kind of artifact we hold for Apache HBase. 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 5
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 HBase Java Client API
Java client API for all HBase data operations including table administration, filters, coprocessors, batch operations, and async client for high-throughput workloads.
Apache HBase Regions API
Region information
Apache HBase Rows API
Row and cell operations
Apache HBase Scans API
Table scanning operations
Apache HBase Tables API
Table management operations
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 HBase 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 Hbase 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 Hbase 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.
Wide-Column NoSQL Storage
Store sparse, semi-structured data in a distributed wide-column table model inspired by Google Bigtable.
REST API (Stargate)
HTTP REST gateway for language-agnostic table and row operations using JSON or XML.
Thrift API
High-performance Thrift interface for cross-language HBase access with compact binary encoding.
Row-Level Consistency
Strong consistency guarantees for single-row get, put, and delete operations.
Coprocessors
Server-side coprocessor framework for custom observers and endpoints analogous to stored procedures.
HBase Shell
JRuby-based interactive shell for administrative and data manipulation operations.
Scanner API
Flexible server-side scan API with filters, time ranges, and column family projections.
Replication
Asynchronous multi-cluster replication for disaster recovery and geographic distribution.
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 Hbase Rest Context
JSON-LDSpectral Rules 2
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 HBase API Rules
SPECTRALApache HBase API Rules
SPECTRALJSON Schema 8
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.
Cell
JSON SCHEMACellSet
JSON SCHEMAClusterVersion
JSON SCHEMAColumnFamily
JSON SCHEMAScanner
JSON SCHEMATableList
JSON SCHEMATableRegions
JSON SCHEMATableSchema
JSON SCHEMAScroll within the panel for all 8 ·
JSON Structure 8
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.
Hbase Rest Cell Structure
JSON STRUCTUREHbase Rest Cellset Structure
JSON STRUCTUREHbase Rest Clusterversion Structure
JSON STRUCTUREHbase Rest Columnfamily Structure
JSON STRUCTUREHbase Rest Scanner Structure
JSON STRUCTUREHbase Rest Tablelist Structure
JSON STRUCTUREHbase Rest Tableregions Structure
JSON STRUCTUREHbase Rest Tableschema Structure
JSON STRUCTUREScroll within the panel for all 8 ·
Examples 8
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.
Hbase Rest Cell Example
EXAMPLEHbase Rest Cellset Example
EXAMPLEHbase Rest Scanner Example
EXAMPLEHbase Rest Tablelist Example
EXAMPLEScroll within the panel for all 8 ·
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 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.
Time-Series Data Storage
Store high-velocity time-series sensor or log data with row keys designed for time range scans.
Event Logging
Persist event streams from web applications or IoT devices for analytics and audit.
User Profile Storage
Store sparse user profile attributes at scale with efficient random access by user ID.
Graph Storage Backend
Use HBase as a backend storage engine for graph databases like Apache TinkerPop/JanusGraph.
Machine Learning Feature Store
Store and serve pre-computed ML features at low latency for online prediction.
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 Hadoop HDFS
HBase uses HDFS as its underlying distributed file system for WAL and HFile storage.
Apache Phoenix
SQL skin over HBase providing JDBC access, secondary indexes, and query optimization.
Apache Spark
Spark-HBase connector for reading and writing HBase tables as Spark DataFrames.
Apache Hive
HBase storage handler for using HBase tables as external Hive tables.
Apache Flink
Flink HBase connector for reading and writing HBase tables in streaming pipelines.
Resources
Every other property we hold for Apache HBase — 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 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
← All providers · Data indexed from github.com/api-evangelist/apache-hbase · machine-readable index on apis.io