{
  "id": "p_ogNvxT7Reh2s_Ebf",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_ogNvxT7Reh2s_Ebf",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "Say you run platform engineering, and you have been told that the agents your team is building will need to read credentials from somewhere. The obvious answer is the secrets manager you already know. Before you commit, you want to know how well each candidate describes its own API in public, since an agent can only call what it can read.\n\nThe Encryption area at encryption.apievangelist.com is a good place to look. It covers encryption services, key management systems, HSMs, envelope encryption and end-to-end encryption SDKs. It counts 58 providers and ranks 30 of them. The average Kin Score of those 30 is 44.6. Thirteen are thin, ten are developing, four are strong and three are exemplar.\n\nNow look at where the name you were going to pick lands. HashiCorp Vault is the default answer to where to keep the secrets for a whole generation of platform teams. It is 28th of 30, at 31.0, in the thin band, with 4 APIs. The post is careful about what that means. Vault's API is large and long-standing, but what can be scored from the outside is thin. The gap between how widely it is used and how well it is described publicly is the biggest in the area.\n\nIt is not alone among secrets managers. Akeyless scores 33.3 and is also thin. The OpenBao fork of Vault scores 51.7. The post calls these the infrastructure most agent platforms will be told to read credentials from, which is exactly your situation.\n\nSo who is at the top? You might expect a hyperscaler or a dedicated key vendor. The leader is Paubox, at 75.8, which is exemplar. Paubox is a HIPAA-compliant email and messaging vendor, and it ranks above both hyperscaler key services because its three APIs are documented the way a healthcare integrator needs them. Encryption is part of what Paubox sells, not all of it. Behind it come Amazon KMS at 70.2 and Evervault at 67.9, both exemplar with one API each. Amazon Certificate Manager follows at 66.3, then Virtru at 58.7, IronCore Labs at 55.9 and Fortanix at 55.2, all strong. Google Cloud KMS is developing at 53.2, and Digicert is developing at 40.3.\n\nIf you were tempted to pick the vendor with the most APIs, the post has a warning for you. Count is not depth. Virtru ships 15 APIs, the most in the ranked list, and scores 58.7. Amazon KMS ships one and scores 70.2. A single well-described key-management contract scores higher than a large set of loosely described ones.\n\nThere is a second thing to keep in mind when you read the numbers. Nineteen of the 30 ranked providers ship exactly one API. In encryption that makes sense, because a KMS is one contract with a dozen operations. But it also means a single missing artifact, such as a changelog, an OpenAPI, or a rate-limit page, moves the whole score. A low number can mean one gap that is easy to close. It does not have to mean a poor product.\n\nHere is the turn that matters. An encryption vendor asks you to trust it with your keys. Yet on average, its own API's public contract scores 44.6. The category that sells trust is, as a group, only middling at describing itself. Vault is the sharpest example, since the thing you reach for first is among the least legible from the outside.\n\nWhat you take away is a change in how you shortlist. Compare the contracts as carefully as the cryptography. Do not assume the incumbent is the best documented. Look at Amazon KMS and Evervault before you decide, because they sit in the exemplar band with one API each. And remember that these scores come from what can be seen publicly, not from how Vault behaves inside your own cluster. Use them to decide what to read first, then verify the rest yourself.\n\nRead the original: https://apis.io/2026/11/16/encryption-lists-58-providers-and-hashicorp-vault-scores-31-on-its-own-api/",
  "title": "You are picking the key service your agents will call, and the incumbent is not the best documented",
  "topics": [
    "encryption",
    "key-management",
    "secrets-management",
    "api-documentation"
  ],
  "published_at": "2026-11-16T13:36:58.393Z",
  "expires_at": null,
  "policy_version": "2026.11.14-1"
}
