Kinde
Kinde is an authentication and user management platform for SaaS and B2B applications - handling sign-up and login, multi-factor authentication, organizations, roles and permissions, feature flags, and usage-based billing. The Kinde Management API programmatically manages a Kinde business over a subdomain-scoped base URL (https://{yourbusiness}.kinde.com/api/v1), authenticated with a Bearer JWT obtained via the OAuth2 client_credentials flow from a machine-to-machine (M2M) application. Almost everything available in the Kinde admin UI - users, organizations, roles, permissions, feature flags, applications, connections, APIs and scopes, subscribers, properties, webhooks, and billing - is available through the API.
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 Kinde the way a machine reads it — 36 machine-readable artifacts across 27 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 — Kinde scores 41.2/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 Kinde
Each block below is one kind of artifact we hold for Kinde. 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 27
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.
Kinde API Keys API
The API Keys API from Kinde — 3 operation(s) for api keys.
Kinde APIs API
The APIs API from Kinde — 6 operation(s) for apis.
Kinde Applications API
The Applications API from Kinde — 7 operation(s) for applications.
Kinde Billing Agreements API
The Billing Agreements API from Kinde — 1 operation(s) for billing agreements.
Kinde Billing Entitlements API
The Billing Entitlements API from Kinde — 1 operation(s) for billing entitlements.
Kinde Billing Meter Usage API
The Billing Meter Usage API from Kinde — 1 operation(s) for billing meter usage.
Kinde Business API
The Business API from Kinde — 1 operation(s) for business.
Kinde Callbacks API
The Callbacks API from Kinde — 2 operation(s) for callbacks.
Kinde Connected Apps API
The Connected Apps API from Kinde — 3 operation(s) for connected apps.
Kinde Connections API
The Connections API from Kinde — 2 operation(s) for connections.
Kinde Directories API
The Directories API from Kinde — 2 operation(s) for directories.
Kinde Environment variables API
The Environment variables API from Kinde — 2 operation(s) for environment variables.
Kinde Environments API
The Environments API from Kinde — 6 operation(s) for environments.
Kinde Feature Flags API
The Feature Flags API from Kinde — 2 operation(s) for feature flags.
Kinde Identities API
The Identities API from Kinde — 1 operation(s) for identities.
Kinde Industries API
The Industries API from Kinde — 1 operation(s) for industries.
Kinde MFA API
The MFA API from Kinde — 1 operation(s) for mfa.
Kinde Organizations API
The Organizations API from Kinde — 27 operation(s) for organizations.
Kinde Permissions API
The Permissions API from Kinde — 2 operation(s) for permissions.
Kinde Properties API
The Properties API from Kinde — 2 operation(s) for properties.
Kinde Property Categories API
The Property Categories API from Kinde — 2 operation(s) for property categories.
Kinde Roles API
The Roles API from Kinde — 7 operation(s) for roles.
Kinde Search API
The Search API from Kinde — 1 operation(s) for search.
Kinde Subscribers API
The Subscribers API from Kinde — 2 operation(s) for subscribers.
Kinde Timezones API
The Timezones API from Kinde — 1 operation(s) for timezones.
Kinde Users API
The Users API from Kinde — 11 operation(s) for users.
Kinde Webhooks API
The Webhooks API from Kinde — 4 operation(s) for webhooks.
Scroll within the panel for all 27 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Kinde Management API
OPEN COLLECTIONPricing 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.
Rate 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.
Kinde So 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.
Kinde So Finops
FINOPSSecurity Posture 4
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 Kinde — 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 1
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 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/kinde-so · machine-readable index on apis.io