Encryption

An index and topic collection covering encryption services, key management systems (KMS), hardware security modules (HSM), envelope encryption, end-to-end encryption SDKs, certificate management, and code/data signing. This topic gathers the cryptographic primitives, managed services, and open-source libraries that protect data at rest and in transit across cloud, mobile, web, and supply-chain workloads. It includes managed KMS offerings (AWS KMS, Google Cloud KMS, Azure Key Vault), HSM and enterprise key management platforms, secrets and configuration encryption tooling (HashiCorp Vault, Doppler, SOPS), code- and artifact-signing infrastructure (Sigstore, Cosign, Notary, TUF), end-to-end encrypted messaging protocols (Signal, Matrix), and certificate authority APIs (Let's Encrypt, DigiCert, Amazon Private CA). Distinct from the broader Security topic, this collection focuses specifically on cryptography, keys, certificates, and signing.

Encryption is profiled on the APIs.io network. Tagged areas include Encryption, KMS, HSM, Cryptography, and Key Management.

The Encryption catalog on APIs.io includes 1 JSON-LD context.

Encryption’s developer surface includes developer portal and 1 more developer resources.

🌐 Visit website📡 Profile data on GitHub
9.6/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0
0 APIs 8 Features 7 Use Cases
EncryptionKMSHSMCryptographyKey ManagementCertificate ManagementCode SigningEnd-to-End Encryption

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0
Composite quality — 9.6/100 · minimal
Contract Quality 3.1 / 21
Developer Ergonomics 1.6 / 17
Access Clarity 0.0 / 17
Operational Transparency 0.6 / 11
Contract Governance 0.0 / 10
Discoverability 4.1 / 9
Regulatory Posture 0.7 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/encryption: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Features 8

Notable capabilities this provider offers.

Managed Key Management Services

Cloud KMS offerings like AWS KMS, Google Cloud KMS, and Azure Key Vault provide managed creation, rotation, and lifecycle of cryptographic keys with hardware-backed protection a...

Hardware Security Module APIs

Network-attached HSMs and HSM-backed services such as AWS CloudHSM, Azure Dedicated HSM, and Google Cloud HSM expose tamper-resistant cryptographic operations through PKCS#11 an...

Envelope Encryption Patterns

Envelope encryption wraps data encryption keys (DEKs) with key encryption keys (KEKs) stored in a KMS, enabling scalable encryption of large data sets while centralizing key con...

End-to-End Encryption Protocols

Open protocols like Signal, Matrix Olm/Megolm, and MLS provide forward-secret, deniable end-to-end encryption for messaging, calling, and collaboration applications.

Certificate Lifecycle Automation

ACME-based services like Let's Encrypt, alongside enterprise CAs like DigiCert and Amazon Private CA, automate issuance, renewal, and revocation of TLS and code-signing certific...

Code and Artifact Signing

Sigstore, Cosign, Notary, and TUF provide keyless and key-based signing of container images, binaries, and software packages with transparency-log-backed verification.

Secrets and Configuration Encryption

Tools like HashiCorp Vault, Doppler, and SOPS encrypt secrets, environment variables, and configuration files in transit and at rest, integrating with KMS providers and CI/CD pi...

Open-Source Cryptographic Libraries

Libraries like Google Tink, libsodium, OpenSSL, and BoringSSL provide misuse-resistant primitives for symmetric, asymmetric, AEAD, hashing, and digital signature operations.

Scroll for all 8

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Encryption Context

10 classes · 23 properties

JSON-LD

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

CustomerMasterKey

14 properties

JSON SCHEMA

EncryptRequest

6 properties

JSON SCHEMA

JSON Structure 2

JSON Structure definitions describing this provider's data shapes.

Encryption Cmk Structure

14 properties

JSON STRUCTURE

Encryption Encrypt Request Structure

6 properties

JSON STRUCTURE

Examples 2

Example request and response payloads for these APIs.

Encryption Cmk Example

14 fields

EXAMPLE

Encryption Encrypt Request Example

6 fields

EXAMPLE

Use Cases 7

What developers build with this provider.

Encrypting Data at Rest in the Cloud

Applications use cloud KMS APIs to encrypt database fields, S3 objects, and disk volumes with envelope encryption, ensuring keys never leave a managed boundary while data cipher...

TLS Termination and Certificate Renewal

Web platforms automate TLS certificate provisioning and rotation through ACME (Let's Encrypt) or enterprise CA APIs (DigiCert, Amazon Private CA), keeping in-transit encryption ...

Software Supply Chain Signing

Build pipelines sign container images and binaries with Sigstore/Cosign, anchoring artifacts to transparency logs so downstream consumers can verify provenance before deploying.

End-to-End Encrypted Messaging and Collaboration

Messaging applications integrate Signal protocol, Matrix Olm/Megolm, or MLS to provide forward-secret encryption where neither the service operator nor an attacker can read mess...

Secrets Management for CI/CD

HashiCorp Vault, Doppler, and SOPS encrypt secrets used across CI/CD pipelines, source control, and runtime environments, integrating with cloud KMS for sealed storage and audit...

Tokenization and Payment Cryptography

Payment processors and PCI workloads use services like AWS Payment Cryptography and Apple Pay tokenization to perform PIN translation, card encryption, and EMV operations under ...

Workload Identity and Zero-Trust Cryptography

SPIFFE/SPIRE issue short-lived, cryptographically verifiable workload identities (SVIDs) so services can mutually authenticate without long-lived secrets across multi-cloud envi...

Scroll for all 7

Integrations 8

Pre-built integrations with other platforms and tools.

AWS KMS

Managed key creation, envelope encryption, and HSM-backed cryptographic operations integrated across AWS services and accessible via SDK and REST APIs.

Google Cloud KMS

Multi-region, software- and HSM-backed key management for envelope encryption and signing across GCP services and external KMS scenarios.

Azure Key Vault

Centralized key, secret, and certificate management with HSM-backed key protection and tight integration into Azure services and Entra ID.

HashiCorp Vault

Open-source secrets management with a Transit engine for encryption-as-a-service, PKI engine for certificate issuance, and KMIP server for HSM integration.

Sigstore

Free, keyless software signing infrastructure built around Fulcio (CA), Rekor (transparency log), and Cosign (signing CLI), now broadly used for OSS supply chain integrity.

Let's Encrypt

Free, automated ACME-based certificate authority issuing billions of TLS certificates that underpin in-transit encryption for the public web.

Tink

Google's misuse-resistant cryptography library providing AEAD, MAC, hybrid encryption, and signature primitives with pluggable KMS backends.

Signal Protocol

Forward-secret, end-to-end encryption protocol used by Signal, WhatsApp, and others, providing double-ratchet key derivation and prekey-based async messaging.

Scroll for all 8

Resources

Get Started 1

Portal, sign-up, and the first successful call

Portal
Portal

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization

Source (apis.yml)

apis.yml Raw ↑ 
aid: encryption
name: Encryption
description: An index and topic collection covering encryption services, key management systems (KMS), hardware security modules
  (HSM), envelope encryption, end-to-end encryption SDKs, certificate management, and code/data signing. This topic gathers
  the cryptographic primitives, managed services, and open-source libraries that protect data at rest and in transit across
  cloud, mobile, web, and supply-chain workloads. It includes managed KMS offerings (AWS KMS, Google Cloud KMS, Azure Key
  Vault), HSM and enterprise key management platforms, secrets and configuration encryption tooling (HashiCorp Vault, Doppler,
  SOPS), code- and artifact-signing infrastructure (Sigstore, Cosign, Notary, TUF), end-to-end encrypted messaging protocols
  (Signal, Matrix), and certificate authority APIs (Let's Encrypt, DigiCert, Amazon Private CA). Distinct from the broader
  Security topic, this collection focuses specifically on cryptography, keys, certificates, and signing.
type: Index
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Encryption
- KMS
- HSM
- Cryptography
- Key Management
- Certificate Management
- Code Signing
- End-to-End Encryption
url: https://raw.githubusercontent.com/api-evangelist/encryption/refs/heads/main/apis.yml
created: '2026-05-19'
modified: '2026-05-19'
specificationVersion: '0.19'
apis: []
network:
- name: Amazon KMS
  url: https://raw.githubusercontent.com/api-evangelist/amazon-kms/refs/heads/main/apis.yml
- name: Amazon Payment Cryptography
  url: https://raw.githubusercontent.com/api-evangelist/amazon-payment-cryptography/refs/heads/main/apis.yml
- name: Amazon Private CA
  url: https://raw.githubusercontent.com/api-evangelist/amazon-private-ca/refs/heads/main/apis.yml
- name: Amazon Signer
  url: https://raw.githubusercontent.com/api-evangelist/amazon-signer/refs/heads/main/apis.yml
- name: Apple Pay
  url: https://raw.githubusercontent.com/api-evangelist/apple-pay/refs/heads/main/apis.yml
- name: Azure Key Vault
  url: https://raw.githubusercontent.com/api-evangelist/azure-key-vault/refs/heads/main/apis.yml
- name: Cosign
  url: https://raw.githubusercontent.com/api-evangelist/cosign/refs/heads/main/apis.yml
- name: DigiCert
  url: https://raw.githubusercontent.com/api-evangelist/digicert/refs/heads/main/apis.yml
- name: Doppler
  url: https://raw.githubusercontent.com/api-evangelist/doppler/refs/heads/main/apis.yml
- name: Google Cloud KMS
  url: https://raw.githubusercontent.com/api-evangelist/google-cloud-kms/refs/heads/main/apis.yml
- name: Google Cloud Secret Manager
  url: https://raw.githubusercontent.com/api-evangelist/google-cloud-secret-manager/refs/heads/main/apis.yml
- name: HashiCorp Vault
  url: https://raw.githubusercontent.com/api-evangelist/hashicorp-vault/refs/heads/main/apis.yml
- name: Let's Encrypt
  url: https://raw.githubusercontent.com/api-evangelist/lets-encrypt/refs/heads/main/apis.yml
- name: Lit Protocol
  url: https://raw.githubusercontent.com/api-evangelist/lit-protocol/refs/heads/main/apis.yml
- name: Matrix
  url: https://raw.githubusercontent.com/api-evangelist/matrix/refs/heads/main/apis.yml
- name: Notary Project
  url: https://raw.githubusercontent.com/api-evangelist/notary/refs/heads/main/apis.yml
- name: OpenSSF
  url: https://raw.githubusercontent.com/api-evangelist/openssf/refs/heads/main/apis.yml
- name: OpenWallet Foundation
  url: https://raw.githubusercontent.com/api-evangelist/openwallet-foundation/refs/heads/main/apis.yml
- name: Signal
  url: https://raw.githubusercontent.com/api-evangelist/signal/refs/heads/main/apis.yml
- name: Sigstore
  url: https://raw.githubusercontent.com/api-evangelist/sigstore/refs/heads/main/apis.yml
- name: SOPS
  url: https://raw.githubusercontent.com/api-evangelist/sops/refs/heads/main/apis.yml
- name: SPIFFE
  url: https://raw.githubusercontent.com/api-evangelist/spiffe/refs/heads/main/apis.yml
- name: SSH
  url: https://raw.githubusercontent.com/api-evangelist/ssh/refs/heads/main/apis.yml
- name: Symantec
  url: https://raw.githubusercontent.com/api-evangelist/symantec/refs/heads/main/apis.yml
- name: Symphony
  url: https://raw.githubusercontent.com/api-evangelist/symphony/refs/heads/main/apis.yml
- name: Tink
  url: https://raw.githubusercontent.com/api-evangelist/tink/refs/heads/main/apis.yml
- name: The Update Framework
  url: https://raw.githubusercontent.com/api-evangelist/tuf/refs/heads/main/apis.yml
common:
- type: Portal
  url: https://apievangelist.com
- type: GitHubOrganization
  url: https://github.com/api-evangelist
- type: Features
  data:
  - name: Managed Key Management Services
    description: Cloud KMS offerings like AWS KMS, Google Cloud KMS, and Azure Key Vault provide managed creation, rotation,
      and lifecycle of cryptographic keys with hardware-backed protection and IAM-controlled access.
  - name: Hardware Security Module APIs
    description: Network-attached HSMs and HSM-backed services such as AWS CloudHSM, Azure Dedicated HSM, and Google Cloud
      HSM expose tamper-resistant cryptographic operations through PKCS#11 and REST APIs.
  - name: Envelope Encryption Patterns
    description: Envelope encryption wraps data encryption keys (DEKs) with key encryption keys (KEKs) stored in a KMS, enabling
      scalable encryption of large data sets while centralizing key control.
  - name: End-to-End Encryption Protocols
    description: Open protocols like Signal, Matrix Olm/Megolm, and MLS provide forward-secret, deniable end-to-end encryption
      for messaging, calling, and collaboration applications.
  - name: Certificate Lifecycle Automation
    description: ACME-based services like Let's Encrypt, alongside enterprise CAs like DigiCert and Amazon Private CA, automate
      issuance, renewal, and revocation of TLS and code-signing certificates.
  - name: Code and Artifact Signing
    description: Sigstore, Cosign, Notary, and TUF provide keyless and key-based signing of container images, binaries, and
      software packages with transparency-log-backed verification.
  - name: Secrets and Configuration Encryption
    description: Tools like HashiCorp Vault, Doppler, and SOPS encrypt secrets, environment variables, and configuration files
      in transit and at rest, integrating with KMS providers and CI/CD pipelines.
  - name: Open-Source Cryptographic Libraries
    description: Libraries like Google Tink, libsodium, OpenSSL, and BoringSSL provide misuse-resistant primitives for symmetric,
      asymmetric, AEAD, hashing, and digital signature operations.
- type: UseCases
  data:
  - name: Encrypting Data at Rest in the Cloud
    description: Applications use cloud KMS APIs to encrypt database fields, S3 objects, and disk volumes with envelope encryption,
      ensuring keys never leave a managed boundary while data ciphertext can be stored anywhere.
  - name: TLS Termination and Certificate Renewal
    description: Web platforms automate TLS certificate provisioning and rotation through ACME (Let's Encrypt) or enterprise
      CA APIs (DigiCert, Amazon Private CA), keeping in-transit encryption healthy without manual operations.
  - name: Software Supply Chain Signing
    description: Build pipelines sign container images and binaries with Sigstore/Cosign, anchoring artifacts to transparency
      logs so downstream consumers can verify provenance before deploying.
  - name: End-to-End Encrypted Messaging and Collaboration
    description: Messaging applications integrate Signal protocol, Matrix Olm/Megolm, or MLS to provide forward-secret encryption
      where neither the service operator nor an attacker can read message content.
  - name: Secrets Management for CI/CD
    description: HashiCorp Vault, Doppler, and SOPS encrypt secrets used across CI/CD pipelines, source control, and runtime
      environments, integrating with cloud KMS for sealed storage and audit logging.
  - name: Tokenization and Payment Cryptography
    description: Payment processors and PCI workloads use services like AWS Payment Cryptography and Apple Pay tokenization
      to perform PIN translation, card encryption, and EMV operations under FIPS-validated HSMs.
  - name: Workload Identity and Zero-Trust Cryptography
    description: SPIFFE/SPIRE issue short-lived, cryptographically verifiable workload identities (SVIDs) so services can
      mutually authenticate without long-lived secrets across multi-cloud environments.
- type: Integrations
  data:
  - name: AWS KMS
    description: Managed key creation, envelope encryption, and HSM-backed cryptographic operations integrated across AWS
      services and accessible via SDK and REST APIs.
  - name: Google Cloud KMS
    description: Multi-region, software- and HSM-backed key management for envelope encryption and signing across GCP services
      and external KMS scenarios.
  - name: Azure Key Vault
    description: Centralized key, secret, and certificate management with HSM-backed key protection and tight integration
      into Azure services and Entra ID.
  - name: HashiCorp Vault
    description: Open-source secrets management with a Transit engine for encryption-as-a-service, PKI engine for certificate
      issuance, and KMIP server for HSM integration.
  - name: Sigstore
    description: Free, keyless software signing infrastructure built around Fulcio (CA), Rekor (transparency log), and Cosign
      (signing CLI), now broadly used for OSS supply chain integrity.
  - name: Let's Encrypt
    description: Free, automated ACME-based certificate authority issuing billions of TLS certificates that underpin in-transit
      encryption for the public web.
  - name: Tink
    description: Google's misuse-resistant cryptography library providing AEAD, MAC, hybrid encryption, and signature primitives
      with pluggable KMS backends.
  - name: Signal Protocol
    description: Forward-secret, end-to-end encryption protocol used by Signal, WhatsApp, and others, providing double-ratchet
      key derivation and prekey-based async messaging.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
humanURL: https://apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/encryption"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/encryption/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/encryption/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.