Apache CouchDB
Apache CouchDB is an open-source distributed document-oriented NoSQL database governed by the Apache Software Foundation. It uses JSON for data storage, a RESTful HTTP/JSON API for all database operations, and the Couch Replication Protocol for multi-primary synchronization across servers, mobile devices, and browsers. CouchDB supports Mango queries, MapReduce views, and offline-first application architectures.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Apache CouchDB the way a machine reads it — 113 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 CouchDB scores 62.2/100 (strong), with a separate agent-readiness read of 54/100 (agent ready). 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.
How we profile Apache CouchDB
Each block below is one kind of artifact we hold for Apache CouchDB. 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 CouchDB Authentication API
Session and authentication management
Apache CouchDB Changes API
Database changes feed
Apache CouchDB Cluster API
Cluster membership and configuration
Apache CouchDB Database API
Database management operations
Apache CouchDB Design Documents API
Design documents, views, and indexes
Apache CouchDB Documents API
Document CRUD and bulk operations
Apache CouchDB Mango API
Mango declarative JSON query API
Apache CouchDB Replication API
Replication management
Apache CouchDB Server API
Server-level information and utilities
Scroll within the panel for all 9 ·
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 Couchdb 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 Couchdb 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.
RESTful HTTP/JSON API
All database operations are performed via a clean HTTP API using JSON, making it accessible from any HTTP-capable client.
Multi-Primary Replication
The Couch Replication Protocol enables seamless bidirectional synchronization across servers, mobile, and browser environments.
Offline-First Architecture
Applications can operate fully offline and sync changes when connectivity is restored, enabled by conflict-aware replication.
Mango Query Language
Declarative JSON-based query language for ad-hoc document queries with index support, similar to MongoDB query syntax.
MapReduce Views
Persistent, incrementally updated secondary indexes defined via JavaScript MapReduce functions stored as design documents.
Changes Feed
Real-time notification feed of all database changes, supporting long-polling, continuous, and event-source modes.
Cluster Support
Built-in clustering with consistent hashing for horizontal scaling and high availability across multiple nodes.
MVCC and ACID
Multi-Version Concurrency Control ensures non-blocking reads; document updates are ACID-compliant at the document level.
Scroll within the panel for all 8 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Apache CouchDB _changes Feed
AsyncAPI 2.6 description of the Apache CouchDB database `_changes` feed. CouchDB exposes a per-database, append-only stream of document mutations at `GET /{db}/_changes` (and `P...
ASYNCAPISemantic 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.
Spectral Rules 3
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 CouchDB API Rules
SPECTRALApache CouchDB API Rules
SPECTRALApache CouchDB API Rules
SPECTRALJSON Schema 24
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.
AllDocsResponse
JSON SCHEMABulkDocsRequest
JSON SCHEMAChangeRow
JSON SCHEMAChangesResponse
JSON SCHEMAClusterSetupResponse
JSON SCHEMACreateIndexRequest
JSON SCHEMACreateIndexResponse
JSON SCHEMADatabaseInfo
JSON SCHEMADocRow
JSON SCHEMADocumentInput
JSON SCHEMADocument
JSON SCHEMAErrorResponse
JSON SCHEMAFindRequest
JSON SCHEMAFindResponse
JSON SCHEMAIndexesResponse
JSON SCHEMAKeysRequest
JSON SCHEMAOkResponse
JSON SCHEMAReplicationRequest
JSON SCHEMAReplicationResponse
JSON SCHEMAServerInfo
JSON SCHEMASessionInfo
JSON SCHEMASessionRequest
JSON SCHEMAViewResponse
JSON SCHEMAWriteResponse
JSON SCHEMAScroll within the panel for all 24 ·
JSON Structure 24
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 Couchdb All Docs Response Structure
JSON STRUCTUREApache Couchdb Bulk Docs Request Structure
JSON STRUCTUREApache Couchdb Change Row Structure
JSON STRUCTUREApache Couchdb Changes Response Structure
JSON STRUCTUREApache Couchdb Cluster Setup Response Structure
JSON STRUCTUREApache Couchdb Create Index Request Structure
JSON STRUCTUREApache Couchdb Create Index Response Structure
JSON STRUCTUREApache Couchdb Database Info Structure
JSON STRUCTUREApache Couchdb Doc Row Structure
JSON STRUCTUREApache Couchdb Document Input Structure
JSON STRUCTUREApache Couchdb Document Structure
JSON STRUCTUREApache Couchdb Error Response Structure
JSON STRUCTUREApache Couchdb Find Request Structure
JSON STRUCTUREApache Couchdb Find Response Structure
JSON STRUCTUREApache Couchdb Indexes Response Structure
JSON STRUCTUREApache Couchdb Keys Request Structure
JSON STRUCTUREApache Couchdb Ok Response Structure
JSON STRUCTUREApache Couchdb Replication Request Structure
JSON STRUCTUREApache Couchdb Replication Response Structure
JSON STRUCTUREApache Couchdb Server Info Structure
JSON STRUCTUREApache Couchdb Session Info Structure
JSON STRUCTUREApache Couchdb Session Request Structure
JSON STRUCTUREApache Couchdb View Response Structure
JSON STRUCTUREApache Couchdb Write Response Structure
JSON STRUCTUREScroll within the panel for all 24 ·
Examples 24
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.
Scroll within the panel for all 24 ·
Security Posture 3
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 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.
Mobile Sync Applications
Sync data between a CouchDB server and PouchDB in mobile/browser apps, supporting offline-first user experiences.
Content Management
Store and retrieve rich JSON documents for CMS, blogs, catalogs, and document management systems.
IoT Data Collection
Edge devices write data locally to CouchDB and replicate to central servers when connected.
Multi-Region Replication
Replicate database contents across geographic regions for low-latency reads and disaster recovery.
User Data Storage
Per-user database pattern for storing isolated user data with built-in CouchDB authentication.
Event Sourcing
Use the changes feed as an event stream for event-driven architectures and audit logging.
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.
PouchDB
Browser and Node.js database that syncs with CouchDB via the Couch Replication Protocol.
IBM Cloudant
IBM Cloudant is a fully managed cloud database service based on Apache CouchDB, API-compatible.
Docker
Official CouchDB Docker images for container-based deployments.
Kubernetes / Helm
Official Helm chart for deploying CouchDB clusters on Kubernetes.
Apache Kafka
CouchDB changes feed can be consumed and bridged to Kafka for event streaming pipelines.
Nginx / Load Balancers
CouchDB clusters are typically fronted by Nginx or HAProxy for SSL termination and load balancing.
Resources
Every other property we hold for Apache CouchDB — 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 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/apache-couchdb · machine-readable index on apis.io