Etcd
etcd is a CNCF graduated distributed, reliable key-value store used as the backing store for all Kubernetes cluster data. It provides strong consistency guarantees using the Raft consensus algorithm, supporting watch operations, lease-based TTLs, and atomic compare-and-swap transactions. etcd is designed for high availability and stores critical configuration data for 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 Etcd the way a machine reads it — 96 machine-readable artifacts across 10 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 — Etcd scores 55.1/100 (developing), with a separate agent-readiness read of 48/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Etcd
Each block below is one kind of artifact we hold for Etcd. 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 10
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.
etcd gRPC API
The etcd v3 API is a gRPC-based interface providing key-value operations (put, get, delete, range), watch streams for change notifications, lease management for TTL-based keys, ...
etcd Concurrency API
The etcd concurrency API provides distributed primitives built on top of the core key-value store, including distributed mutexes (locks), leader election, and software transacti...
etcd Metrics API
etcd exposes a Prometheus-compatible metrics endpoint that provides operational insights into the etcd cluster, including request rates, latency histograms, disk I/O statistics,...
etcd v2 HTTP API
The original etcd v2 API exposed a RESTful HTTP interface for key-value operations using a hierarchical directory structure. This API has been deprecated in favor of the v3 gRPC...
Etcd Auth API
Authentication and authorization management for users and roles
Etcd Cluster API
Cluster membership management including member add, remove, and list
Etcd KV API
Key-value store operations including put, get, delete, and range queries
Etcd Lease API
Lease management for TTL-based key expiration
Etcd Maintenance API
Maintenance operations including snapshots, defragmentation, and status
Etcd Watch API
Watch operations for streaming key change notifications
Scroll within the panel for all 10 ·
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).
etcd HTTP Gateway 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.
Etcd Plans Pricing
PLANSRate 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.
Etcd 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.
Etcd Finops
FINOPSSemantic 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.
Etcd 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.
Etcd API Rules
SPECTRALJSON Schema 76
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.
AlarmMember
JSON SCHEMAAlarmRequest
JSON SCHEMAAlarmResponse
JSON SCHEMAAuthDisableResponse
JSON SCHEMAAuthEnableResponse
JSON SCHEMAAuthenticateRequest
JSON SCHEMAAuthenticateResponse
JSON SCHEMAAuthRoleAddRequest
JSON SCHEMAAuthRoleAddResponse
JSON SCHEMAAuthRoleDeleteRequest
JSON SCHEMAAuthRoleDeleteResponse
JSON SCHEMAAuthRoleGetRequest
JSON SCHEMAAuthRoleGetResponse
JSON SCHEMAAuthRoleGrantPermissionRequest
JSON SCHEMAAuthRoleGrantPermissionResponse
JSON SCHEMAAuthRoleListResponse
JSON SCHEMAAuthRoleRevokePermissionRequest
JSON SCHEMAAuthRoleRevokePermissionResponse
JSON SCHEMAAuthUserAddRequest
JSON SCHEMAAuthUserAddResponse
JSON SCHEMAAuthUserChangePasswordRequest
JSON SCHEMAAuthUserChangePasswordResponse
JSON SCHEMAAuthUserDeleteRequest
JSON SCHEMAAuthUserDeleteResponse
JSON SCHEMAAuthUserGetRequest
JSON SCHEMAAuthUserGetResponse
JSON SCHEMAAuthUserGrantRoleRequest
JSON SCHEMAAuthUserGrantRoleResponse
JSON SCHEMAAuthUserListResponse
JSON SCHEMAAuthUserRevokeRoleRequest
JSON SCHEMAAuthUserRevokeRoleResponse
JSON SCHEMACompactionRequest
JSON SCHEMACompactionResponse
JSON SCHEMACompare
JSON SCHEMADefragmentResponse
JSON SCHEMADeleteRangeRequest
JSON SCHEMADeleteRangeResponse
JSON SCHEMAError
JSON SCHEMAHashResponse
JSON SCHEMAetcd Key-Value Store
JSON SCHEMAKeyValue
JSON SCHEMALeaseGrantRequest
JSON SCHEMALeaseGrantResponse
JSON SCHEMALeaseKeepAliveRequest
JSON SCHEMALeaseKeepAliveResponse
JSON SCHEMALeaseLeasesResponse
JSON SCHEMALeaseRevokeRequest
JSON SCHEMALeaseRevokeResponse
JSON SCHEMALeaseTimeToLiveRequest
JSON SCHEMALeaseTimeToLiveResponse
JSON SCHEMAMember
JSON SCHEMAMemberAddRequest
JSON SCHEMAMemberAddResponse
JSON SCHEMAMemberListResponse
JSON SCHEMAMemberPromoteRequest
JSON SCHEMAMemberPromoteResponse
JSON SCHEMAMemberRemoveRequest
JSON SCHEMAMemberRemoveResponse
JSON SCHEMAMemberUpdateRequest
JSON SCHEMAMemberUpdateResponse
JSON SCHEMAMoveLeaderRequest
JSON SCHEMAMoveLeaderResponse
JSON SCHEMAPermission
JSON SCHEMAPutRequest
JSON SCHEMAPutResponse
JSON SCHEMARangeRequest
JSON SCHEMARangeResponse
JSON SCHEMARequestOp
JSON SCHEMAResponseHeader
JSON SCHEMAStatusResponse
JSON SCHEMATxnRequest
JSON SCHEMATxnResponse
JSON SCHEMAWatchCreateRequest
JSON SCHEMAWatchEvent
JSON SCHEMAWatchRequest
JSON SCHEMAWatchResponse
JSON SCHEMAScroll within the panel for all 76 ·
JSON Structure 1
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.
Etcd Structure
JSON STRUCTURESecurity 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.
Resources
Every other property we hold for Etcd — 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 2
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 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/etcd · machine-readable index on apis.io