Let's Encrypt
Let's Encrypt is a free, automated, and open certificate authority run by the Internet Security Research Group affiliated with the Linux Foundation. It provides TLS certificates to secure the web, having issued billions of certificates to enable HTTPS for websites worldwide via the ACME protocol.
Let’s Encrypt publishes 7 APIs on the APIs.io network, including Account API, Authorization API, Certificate API, and 4 more. Tagged areas include Certificates, Linux Foundation, Security, TLS, and ACME.
Let’s Encrypt’s developer surface includes documentation, engineering blog, and 5 more developer resources.
Kin Score
APIs 7
Individual APIs this provider publishes, each with its own machine-readable definition.
Let's Encrypt Account API
ACME account creation and management
Let's Encrypt Authorization API
Domain control authorizations
Let's Encrypt Certificate API
Issued certificate retrieval and revocation
Let's Encrypt Challenge API
Validation challenges (HTTP-01, DNS-01, TLS-ALPN-01)
Let's Encrypt Directory API
Discovery document listing ACME resources
Let's Encrypt Nonce API
Anti-replay nonces for JWS-signed requests
Let's Encrypt Order API
Certificate issuance orders
Scroll for all 7
Open Collections 9
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONLet's Encrypt ACME Account API
OPEN COLLECTIONLet's Encrypt ACME API
OPEN COLLECTIONLet's Encrypt ACME Account Authorization API
OPEN COLLECTIONLet's Encrypt ACME Account Certificate API
OPEN COLLECTIONLet's Encrypt ACME Account Challenge API
OPEN COLLECTIONLet's Encrypt ACME Account Directory API
OPEN COLLECTIONLet's Encrypt ACME Account Nonce API
OPEN COLLECTIONLet's Encrypt ACME Account Order API
OPEN COLLECTIONScroll for all 9
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Lets Encrypt Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Lets Encrypt Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API
Source (apis.yml)
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/providers/lets-encrypt"
curl "https://apis.io/api/v1/providers?limit=25"
curl "https://apis.io/api/v1/providers/lets-encrypt/operations?limit=25"
curl "https://apis.io/api/v1/providers/lets-encrypt/evidence"
Discovery needs no key. Ratings and market analysis are Pro.