Authlete
Authlete is an API-first OAuth 2.0 and OpenID Connect backend service that provides a headless authorization-server engine. It handles the OAuth/OIDC protocol logic and token management so organizations can stand up standards-compliant authorization servers and verifiable-credential issuers without building the protocol layer themselves. Authlete separates the Management APIs (configure services and clients) from the Runtime APIs (power authorization, token, introspection, CIBA, device-flow, federation, and OID4VCI endpoints), and offers managed shared cloud, dedicated cloud, and self-managed deployment across US, Japan, Europe, and Brazil regional clusters. It supports advanced profiles including FAPI / FAPI 2.0, CIBA, PAR, Grant Management, OpenID Federation, Native SSO, and OpenID for Verifiable Credential Issuance, plus regional open-banking standards (Brazil Open Banking, Australia CDR). Backed by 500 Global.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Authlete the way a machine reads it — 26 machine-readable artifacts across 21 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 — Authlete scores 56.0/100 (developing), with a separate agent-readiness read of 72/100 (agent native). 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 Authlete
Each block below is one kind of artifact we hold for Authlete. 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 21
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.
Authlete Authorization Endpoint API
API endpoints for implementing OAuth 2.0 Authorization Endpoint.
Authlete CIBA API
API endpoints for implementing Client-Initiated Backchannel Authentication (CIBA).
Authlete Client Management API
API endpoints for managing OAuth clients, including creation, update, and deletion of clients.
Authlete Device Flow API
API endpoints for implementing OAuth 2.0 Device Flow
Authlete Dynamic Client Registration API
API endpoints for implementing OAuth 2.0 Dynamic Client Registration.
Authlete Federation Endpoint API
API endpoints for implementing OpenID Federation using Authlete.
Authlete Grant Management Endpoint API
API endpoint for implementing OAuth 2.0 grants, including grant management actions like updating and revoking grants.
Authlete Hardware Security Key API
API endpoints for managing hardware security keys (HSK).
Authlete Introspection Endpoint API
API endpoints for implementing OAuth 2.0 Introspection Endpoint.
Authlete Jose Object API
API endpoints for JOSE objects.
Authlete JWK Set Endpoint API
API endpoints for to generate JSON Web Key Set (JWKS) for a service.
Authlete Lifecycle API
The Lifecycle API from Authlete — 1 operation(s) for lifecycle.
Authlete Native SSO API
API endpoints for Native SSO
Authlete Pushed Authorization Endpoint API
API endpoints for implementing OAuth 2.0 Pushed Authorization Requests (PAR).
Authlete Revocation Endpoint API
API endpoint for implementing OAuth 2.0 Revocation Endpoint.
Authlete Service Management API
API endpoints for managing services, including creation, update, and deletion of services.
Authlete Token Endpoint API
API endpoints for implementing OAuth 2.0 Token Endpoint.
Authlete Token Operations API
API endpoints for various token related operations, including creating, revoking and deleting access_tokens with specified scopes.
Authlete UserInfo Endpoint API
API endpoints for implementing OpenID Connect UserInfo Endpoint.
Authlete Utility Endpoints API
API endpoints for various utility operations.
Authlete Verifiable Credential Issuer API
API endpoints for implementing and running a Verifiable Credential Issuer (VCI).
Scroll within the panel for all 21 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
authlete-mcp.yml
MCP SERVERSecurity Posture 3
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 Authlete — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/authlete · machine-readable index on apis.io