HashiCorp Consul
HashiCorp Consul is a distributed, highly available service-networking control plane that automates network configuration, discovers services, enables secure service-to-service communication, and exposes a strongly consistent key/value store. The Consul HTTP API is a REST + JSON service exposed by every Consul agent and server at /v1, gated by the X-Consul-Token header (apiKey) and ACL policies, supporting blocking queries via X-Consul-Index for streaming-style change detection.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles HashiCorp Consul the way a machine reads it — 41 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 — HashiCorp Consul scores 38.9/100 (thin), with a separate agent-readiness read of 22/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from HashiCorp Consul's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/consul/"
title="HashiCorp Consul on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/consul.svg"
alt="HashiCorp Consul Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/consul/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/consul/"
title="HashiCorp Consul on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/consul/card.svg"
alt="HashiCorp Consul Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile HashiCorp Consul
Each block below is one kind of artifact we hold for HashiCorp Consul. 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 14
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.
HashiCorp Consul ACL API
Access Control List management
HashiCorp Consul Agent API
Interact with the local Consul agent
HashiCorp Consul Catalog API
Register and query services and nodes
HashiCorp Consul Config Entries API
Centralized configuration entries
HashiCorp Consul Connect API
Service mesh / Connect CA and intentions
HashiCorp Consul Coordinates API
Network coordinate information
HashiCorp Consul Events API
Fire and list custom user events
HashiCorp Consul Health API
Query health check information
HashiCorp Consul KV Store API
Key/Value store operations
HashiCorp Consul Operator API
Cluster operator endpoints
HashiCorp Consul Sessions API
Session management for distributed locking
HashiCorp Consul Snapshot API
Snapshot and restore operations
HashiCorp Consul Status API
Cluster status information
HashiCorp Consul Transaction API
Atomic key/value transactions
Scroll within the panel for all 14 ·
Open Collections 16
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).
API Collection
OPEN COLLECTIONHashiCorp Consul HTTP ACL API
OPEN COLLECTIONHashiCorp Consul HTTP ACL Agent API
OPEN COLLECTIONHashiCorp Consul HTTP ACL Catalog API
OPEN COLLECTIONHashiCorp Consul HTTP ACL Config Entries API
OPEN COLLECTIONHashiCorp Consul HTTP ACL Connect API
OPEN COLLECTIONHashiCorp Consul HTTP ACL Coordinates API
OPEN COLLECTIONHashiCorp Consul HTTP ACL Events API
OPEN COLLECTIONHashiCorp Consul HTTP ACL Health API
OPEN COLLECTIONHashiCorp Consul HTTP API
OPEN COLLECTIONHashiCorp Consul HTTP ACL KV Store API
OPEN COLLECTIONHashiCorp Consul HTTP ACL Operator API
OPEN COLLECTIONHashiCorp Consul HTTP ACL Sessions API
OPEN COLLECTIONHashiCorp Consul HTTP ACL Snapshot API
OPEN COLLECTIONHashiCorp Consul HTTP ACL Status API
OPEN COLLECTIONHashiCorp Consul HTTP ACL Transaction API
OPEN COLLECTIONScroll within the panel for all 16 ·
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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Consul 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.
Consul 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.
Consul 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.
Consul 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.
HashiCorp Consul API Rules
SPECTRALHashiCorp Consul API Rules
SPECTRALJSON Schema 2
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.
Consul KV Pair
JSON SCHEMAConsul Service Definition
JSON SCHEMASecurity 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 HashiCorp Consul — 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 4
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 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/consul · machine-readable index on apis.io
This is an independent, third-party profile of HashiCorp Consul, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.