HashiCorp Vault
HashiCorp Vault is an open source tool for securely storing and accessing secrets. A secret is anything you want to tightly control access to, such as API keys, passwords, certificates, and more. Vault provides a unified interface to any secret while providing tight access control via policies and recording a detailed audit log. It supports dynamic secrets, data encryption, PKI, SSH certificate issuance, and identity-based access through a comprehensive REST HTTP API.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles HashiCorp Vault the way a machine reads it — 115 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 — HashiCorp Vault scores 62.2/100 (strong), 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 HashiCorp Vault
Each block below is one kind of artifact we hold for HashiCorp Vault. 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.
Vault HTTP API
The complete Vault HTTP API gives full access to all Vault operations via REST. Includes authentication method APIs (AppRole, LDAP, JWT, Kubernetes, AWS, Azure), secrets engine ...
HashiCorp Vault Auth Methods API
Enable, disable, list, and configure authentication methods.
HashiCorp Vault Health API
Check Vault health and initialization status.
HashiCorp Vault Leases API
Look up, renew, and revoke leases for secrets and tokens.
HashiCorp Vault Policies API
Create, read, update, delete, and list ACL policies.
HashiCorp Vault Secrets Config API
Configure KV v2 engine settings such as max versions and CAS required.
HashiCorp Vault Secrets Data API
Read, write, patch, and delete secret data versions in the KV v2 engine.
HashiCorp Vault Secrets Engines API
Mount, unmount, list, and configure secrets engines.
HashiCorp Vault Secrets Metadata API
Manage metadata and version history for KV v2 secrets.
Scroll within the panel for all 9 ·
Open Collections 2
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).
HashiCorp Vault KV Secrets Engine API
OPEN COLLECTIONHashiCorp Vault System Backend 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.
Vault 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.
Vault 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.
Vault Finops
FINOPSFeatures 10
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.
KV Secrets Engine
Versioned key-value secret storage with soft delete, undelete, and permanent destruction.
Dynamic Secrets
On-demand, time-limited credentials for databases, AWS, Azure, GCP, and other backends.
Data Encryption (Transit)
Encryption-as-a-Service for application data without storing plaintext in Vault.
PKI Certificate Authority
Built-in PKI secrets engine for issuing X.509 certificates with configurable TTLs.
SSH Certificate Issuance
Dynamic SSH certificates and OTPs for secure machine access management.
ACL Policies
Fine-grained HCL-based policies controlling access to any secret path with capabilities.
Auth Methods
Pluggable authentication supporting AppRole, LDAP, JWT/OIDC, Kubernetes, AWS, and more.
Lease Management
All dynamic secrets have TTL-bound leases that can be renewed or revoked on demand.
Audit Logging
Comprehensive audit trail of all API requests and responses for compliance.
MCP Server
Official HashiCorp Vault MCP server enabling AI-assisted secrets management workflows.
Scroll within the panel for all 10 ·
Semantic Vocabularies 2
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.
Vault Kv Context
JSON-LDVault Sys 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 Vault API Rules
SPECTRALHashiCorp Vault API Rules
SPECTRALJSON Schema 23
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.
KvConfigRequest
JSON SCHEMAKvConfigResponse
JSON SCHEMASecretDataRequest
JSON SCHEMASecretDataResponse
JSON SCHEMASecretMetadataRequest
JSON SCHEMASecretMetadataResponse
JSON SCHEMASecretVersionMetadata
JSON SCHEMASecretWriteResponse
JSON SCHEMAVersionsRequest
JSON SCHEMAAuthMethodConfig
JSON SCHEMAAuthMethodsResponse
JSON SCHEMAEnableAuthMethodRequest
JSON SCHEMAEnableMountRequest
JSON SCHEMAHealthResponse
JSON SCHEMALeaseIdRequest
JSON SCHEMALeaseRenewResponse
JSON SCHEMALeaseResponse
JSON SCHEMAMountConfig
JSON SCHEMAMountsResponse
JSON SCHEMAPoliciesListResponse
JSON SCHEMAPolicyRequest
JSON SCHEMAPolicyResponse
JSON SCHEMARenewLeaseRequest
JSON SCHEMAScroll within the panel for all 23 ·
JSON Structure 23
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.
Vault Kv Kv Config Request Structure
JSON STRUCTUREVault Kv Kv Config Response Structure
JSON STRUCTUREVault Kv Secret Data Request Structure
JSON STRUCTUREVault Kv Secret Data Response Structure
JSON STRUCTUREVault Kv Secret Metadata Request Structure
JSON STRUCTUREVault Kv Secret Metadata Response Structure
JSON STRUCTUREVault Kv Secret Version Metadata Structure
JSON STRUCTUREVault Kv Secret Write Response Structure
JSON STRUCTUREVault Kv Versions Request Structure
JSON STRUCTUREVault Sys Auth Method Config Structure
JSON STRUCTUREVault Sys Auth Methods Response Structure
JSON STRUCTUREVault Sys Enable Auth Method Request Structure
JSON STRUCTUREVault Sys Enable Mount Request Structure
JSON STRUCTUREVault Sys Health Response Structure
JSON STRUCTUREVault Sys Lease Id Request Structure
JSON STRUCTUREVault Sys Lease Renew Response Structure
JSON STRUCTUREVault Sys Lease Response Structure
JSON STRUCTUREVault Sys Mount Config Structure
JSON STRUCTUREVault Sys Mounts Response Structure
JSON STRUCTUREVault Sys Policies List Response Structure
JSON STRUCTUREVault Sys Policy Request Structure
JSON STRUCTUREVault Sys Policy Response Structure
JSON STRUCTUREVault Sys Renew Lease Request Structure
JSON STRUCTUREScroll within the panel for all 23 ·
Examples 23
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 23 ·
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 7
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.
Application Secret Injection
Inject database credentials, API keys, and config into applications at runtime via Vault Agent.
Kubernetes Secrets Management
Replace Kubernetes secrets with Vault-managed secrets using the Vault Secrets Operator.
Database Credential Rotation
Automatically rotate database credentials with dynamic secrets engine for zero-knowledge security.
PKI Automation
Automate certificate lifecycle management for internal services and mutual TLS.
CI/CD Secret Injection
Provide short-lived credentials to CI/CD pipelines via AppRole or GitHub Actions OIDC.
Secrets as Code
Manage Vault configuration as code using the Terraform Vault provider.
Compliance and Audit
Meet SOC 2, PCI-DSS, HIPAA, and FedRAMP requirements with immutable audit logs.
Scroll within the panel for all 7 ·
Integrations 8
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Terraform
Terraform Vault provider for managing Vault configuration and policies as code.
Kubernetes
Vault Secrets Operator and Vault Agent Injector for native Kubernetes integration.
GitHub Actions
OIDC-based authentication from GitHub Actions workflows without static credentials.
AWS
Dynamic AWS IAM credentials and EC2/IAM-based authentication methods.
Consul
Native HashiCorp Consul integration for service mesh secrets and ACL tokens.
PostgreSQL
Dynamic database credentials for PostgreSQL with configurable role TTLs.
Nomad
Native HashiCorp Nomad integration for workload identity and secrets.
Ansible
HashiCorp Vault lookup plugin for Ansible playbook secret retrieval.
Scroll within the panel for all 8 ·
Resources
Every other property we hold for HashiCorp Vault — 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
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 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 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/vault · machine-readable index on apis.io