Logto
Logto is an open source identity infrastructure platform with authentication, authorization, user management, and multi-tenancy supporting OIDC, OAuth, and SAML.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Logto the way a machine reads it — 46 machine-readable artifacts across 39 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 — Logto scores 37.6/100 (thin), 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 Logto
Each block below is one kind of artifact we hold for Logto. 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 39
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.
Logto Account center API
Customize your account API settings.
Logto Applications API
Application represents your registered software program or service that has been authorized to access user information and perform actions on behalf of users within the system. ...
Logto Audit logs API
Audit logs are used to track end-user activities in Logto sign-in experience and other flows. It does not include activities in Logto Console.
Logto Authn API
Authentication endpoints for third-party integrations and identity providers.
Logto Captcha provider API
Setup the captcha provider.
Logto Configs API
Endpoints for managing Logto global configurations for the tenant, such as admin console config and OIDC signing keys. See [🔑 Signing keys](https://docs.logto.io/docs/recipes/si...
Logto Connector factories API
Connector factories are used to create connectors. They can be treated as preconfigured templates for connectors.
Logto Connectors API
Connectors are the bridge between Logto and other third-party vendors who provide short message service (SMS), email service, or user information on wildly accepted social media...
Logto Custom phrases API
Endpoints for managing custom phrases that allow you to customize the phrases displayed in the sign-in experience. See [Localized language](https://docs.logto.io/docs/recipes/cu...
Logto Custom profile fields API
An admin feature used to create a customized user profile form, which is used to collect additional user information upon successful registrations.
Logto Dashboard API
Endpoints that power the dashboard page of Console to show the statistics of the current tenant.
Logto Domains API
Custom domain lets you present a consistent brand by having your own domain name on the sign-in and registration pages. See [🌍 Custom domain](https://docs.logto.io/docs/recipes/...
Logto Email templates API
Manage custom i18n email templates for various types of emails, such as sign-in verification codes and password resets.
Logto Experience API
The Experience endpoints allow end-users to interact with Logto for identity verification and profile completion.
Logto Hooks API
Hook enables you to effortlessly receive real-time updates regarding specific events, such as user registration, sign-in, or password reset. See [🪝 Webhooks] to get started and ...
Logto My account API
Account routes provide functionality for managing user profile for the end user to interact directly with access tokens.
Logto One-time tokens API
One-time tokens are used for various authentication and verification purposes. They are typically sent via email and have an expiration time.
Logto Organization invitations API
Organization invitations are used to invite users to join an organization. They are sent via email and contain a link that the user can click to accept the invitation and join t...
Logto Organization roles API
Organization roles are used to define a set of organization scopes that can be assigned to users. Every organization role is a part of the organization template. Organization ro...
Logto Organization scopes API
Organization scopes (permissions) are used to define actions that can be performed on a organization. Every organization scope is a part of the organization template. Organizati...
Logto Organizations API
Organization is a concept that brings together multiple identities (mostly users). Logto supports multiple organizations, and each organization can have multiple users. Every or...
Logto Resources API
Resources (API resources) represent the APIs that you want to protect with Logto. Each resource has a unique indicator (URI) and a set of scopes (permissions). The resources wil...
Logto Roles API
Role management for API resource RBAC (role-based access control). See [🔐 Role-based access control (RBAC)](https://docs.logto.io/docs/recipes/rbac/) to get started with role-ba...
Logto SAML applications API
SAML (Security Assertion Markup Language) applications represent applications that use SAML protocol for single sign-on (SSO). These endpoints allow you to manage SAML applicati...
Logto SAML applications auth flow API
Endpoints for SAML (Security Assertion Markup Language) applications auth flow.
Logto Secrets API
Secrets are used to store sensitive information such as API keys, third-party tokens, and other confidential data in Logto's Secret Vault.
Logto Sentinel activities API
Sentinel activities are used to track and manage user authentication attempts, including successful and failed attempts. Based on your sentinel policy settings, Logto will autom...
Logto Sign-in experience API
Endpoints for customizing Logto sign-in experience. See [🎨 Customize sign-in experience](https://docs.logto.io/docs/recipes/customize-sie/) to learn more about how the configura...
Logto SSO connector providers API
Endpoints for SSO (single sign-on) connector providers. SSO connector providers provide the metadata and configuration templates for creating SSO connectors.
Logto SSO connectors API
Endpoints for managing single sign-on (SSO) connectors. Your sign-in experience can use these well-configured SSO connectors to authenticate users and sync user attributes from ...
Logto Status API
Endpoints for health check.
Logto Subject tokens API
The subject token API provides the ability to create a new subject token for the use of impersonating the user.
Logto Swagger.json API
Endpoints for the Swagger JSON document.
Logto Systems API
Endpoints for system constants and information.
Logto User assets API
Endpoints for managing user uploaded assets.
Logto Users API
Endpoints for user management. Including creating, updating, deleting, and querying users with flexible filters. In addition to the endpoints, see [🧑🚀 Manage users](https://doc...
Logto Verification codes API
Endpoints for handling verification codes. It is helpful when building a custom profile page in your app. See [👤 User profile](https://docs.logto.io/docs/recipes/user-profile/#o...
Logto Verifications API
Endpoints for creating and validating verification records, which can be used in Profile routes.
Logto Well-known API
Well-Known routes provide information and resources that can be discovered by clients without the need for authentication.
Scroll within the panel for all 39 ·
Pricing 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.
Logto 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.
Logto 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.
Logto Finops
FINOPSSecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Logto — 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.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/logto · machine-readable index on apis.io