Clerk
Clerk is a complete user management and authentication infrastructure platform offering embeddable UI components, flexible APIs, and admin dashboards. It provides full-stack authentication including multi-factor authentication, social sign-on, passkeys, organizations for B2B SaaS, billing, session management, and machine-to-machine authentication, with SDKs spanning Next.js, React, Expo, iOS, Android, Go, Python, Ruby, Java, PHP, and C#.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Clerk the way a machine reads it — 144 machine-readable artifacts across 76 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 — Clerk scores 68.5/100 (strong), 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.
How we profile Clerk
Each block below is one kind of artifact we hold for Clerk. 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 76
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.
Clerk Account Portal API
The Account Portal API from Clerk — 1 operation(s) for account portal.
Clerk Active Sessions API
Used to interact with the sessions of the current user.
Clerk Actor Tokens API
Allow your users to sign in on behalf of other users.
Clerk Agent Tasks API
Tasks that allow creating user sessions for agent-based interactions.
Clerk Allow-list / Block-list API
Allow-lists and Block-lists allow you to control who can sign up or sign in to your application, by restricting access based on the user's email address or phone number.
Clerk API Keys API
Endpoints for managing API Keys
Clerk Application Transfers API
An object representing a transfer request for an application between workspaces. The high-level flow for application transfer: 1. The initial workspace can create an application...
Clerk Applications API
An object representing a Clerk application. Each `application` can have multiple `instances`, typically one for development and one for production, each with distinct user pools.
Clerk Backup Codes API
Used to interact with the two factor authentication backup codes of the current user.
Clerk Beta Features API
Modify instance settings that are currently in beta.
Clerk Billing API
Billing-related endpoints for managing statements and payment attempts.
Clerk Checkouts API
Used to interact with the checkout flow.
Clerk Clear Site Data API
The Clear Site Data API from Clerk — 1 operation(s) for clear site data.
Clerk Client API
Used to interact with the Client Object.
Clerk Clients API
The Client object tracks sessions, as well as the state of any sign in and sign up attempts, for a given device.
Clerk Config API
Operations for managing instance configuration. The config API provides a unified interface for reading and updating instance settings, including authentication methods, SSO con...
Clerk Dev Browser API
The Dev Browser API from Clerk — 2 operation(s) for dev browser.
Clerk DevBrowser API
Used to handle dev browsers.
Clerk Domains API
Domains represent each instance's URLs and DNS setup.
Clerk Email Addresses API
A user can be associated with one or more email addresses, which allows them to be contacted via email.
Clerk Email & SMS Templates API
Email & SMS templates allow you to customize the theming and wording of emails & SMS messages that are sent by your instance.
Clerk Enterprise Connections API
An Enterprise Connection holds configuration data required for facilitating an enterprise SSO flow between your Clerk instance and an identity provider.
Clerk Environment API
Used to get and update the current Environment
Clerk External Accounts API
Used to interact with the external accounts of the current user.
Clerk Health API
Used to get the health status of the API.
Clerk Instance Settings API
Modify the settings of your instance.
Clerk Invitations API
Invitations allow you to invite someone to sign up to your application, via email.
Clerk JWKS API
Retrieve the JSON Web Key Set which can be used to verify the token signatures of the instance.
Clerk JWT Templates API
JWT Templates allow you to generate custom authentication tokens tied to authenticated sessions, enabling you to integrate with third-party services.
Clerk M2M Tokens API
Machine to Machine Tokens are used to manage authentication between Machines.
Clerk Machines API
A Machine represents a machine/server/service which can be used in machine-to-machine authentication.
Clerk Members API
Used to interact with the members of an organization. The current user must be an administrator to access them.
Clerk Membership Requests API
Used to interact with the members of an organization. The current user must be an administrator to access them.
Clerk Miscellaneous API
Various endpoints that do not belong in any particular category.
Clerk OAuth Access Tokens API
Endpoints for managing OAuth Access Tokens, which are credentials to access protected resources on behalf of a user.
Clerk OAuth Applications API
OAuth applications contain data for clients using Clerk as an OAuth2 identity provider.
Clerk OAuth2 Callbacks API
Used to receive callbacks from successful OAuth attempts.
Clerk OAuth2 Identity Provider API
Requests for the OAuth2 authorization flow.
Clerk Organization API
Used to interact with an organization and its properties. The current user must be an administrator to access them.
Clerk Organization Creation Defaults API
Used to get suggested defaults when creating a new organization.
Clerk Organization Domains API
Manage organization domains.
Clerk Organization Invitations API
Invite users to an organization.
Clerk Organization Memberships API
Manage member roles in an organization.
Clerk Organization Permissions API
Manage organization permissions that define what members can do within an organization.
Clerk Organization Roles API
Manage custom roles in an organization.
Clerk Organizations API
Organizations are used to group members under a common entity and provide shared access to resources.
Clerk Organizations Memberships API
Used to interact with the current user's organization memberships, invitations and suggestions.
Clerk Passkeys API
Used to interact with the passkeys of the logged in user.
Clerk Payment Attempts API
Used to interact with payment attempts for users and organizations.
Clerk Payment Methods API
Used to interact with payment methods belonging to users and organizations.
Clerk Phone Numbers API
A user can be associated with one or more phone numbers, which allows them to be contacted via SMS.
Clerk Plans API
Used to interact with plans that users and organizations can purchase.
Clerk Proxy Checks API
Check if a user is using a proxy.
Clerk Proxy Health API
The Proxy Health API from Clerk — 1 operation(s) for proxy health.
Clerk Redirect API
The Redirect API from Clerk — 1 operation(s) for redirect.
Clerk Redirect URLs API
Redirect URLs are whitelisted URLs that facilitate secure authentication flows in native applications (e.g. React Native, Expo). In these contexts, Clerk ensures that security-c...
Clerk Role Sets API
Role sets define collections of roles that can be assigned to organization members. Each organization uses one role set to determine the available roles for its members. Role se...
Clerk Roles API
The Roles API from Clerk — 1 operation(s) for roles.
Clerk SAML API
Used in authentication flows using SAML.
Clerk SAML Connections API
A SAML Connection holds configuration data required for facilitating a SAML SSO flow between your Clerk Instance (SP) and a particular SAML IdP.
Clerk Sessions API
The Session object is an abstraction over an HTTP session. It models the period of information exchange between a user and the server. Sessions are created when a user successfu...
Clerk Sign-in Tokens API
Sign-in tokens are JWTs that can be used to sign in to an application without specifying any credentials. A sign-in token can be used at most once and they can be consumed from ...
Clerk Sign Ins API
Used to sign in a user in the current client.
Clerk Sign Ups API
Sign-up objects track the progress of a sign-up attempt and store any field collected from user input.
Clerk Statements API
Used to interact with billing statements for users and organizations.
Clerk Subscription Items API
Used to interact with subscription items belonging to users and organizations.
Clerk Subscriptions API
Used to interact with subscriptions belonging to users and organizations.
Clerk Testing Tokens API
Tokens meant for use by end-to-end test suites in requests to the Frontend API, so as to bypass bot detection measures.
Clerk TOTP API
Used to interact with One Time Password authenticators of the current user.
Clerk User API
Used to interact with the properties of the current user.
Clerk Users API
The user object represents a user that has successfully signed up to your application.
Clerk Waitlist API
Used to interact with the waitlist.
Clerk Waitlist Entries API
Manage waitlist entries.
Clerk Web3 Wallets API
Used to interact with the web3 wallets of the logged in user.
Clerk Webhooks API
You can configure webhooks to be notified about various events that happen on your instance.
Clerk Well Known API
Well-known endpoints like JWKS, deep linking, and openid-configuration.
Scroll within the panel for all 76 ·
Open Collections 4
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).
Clerk Backend API
OPEN COLLECTIONClerk Frontend API
OPEN COLLECTIONClerk Platform API
OPEN COLLECTIONClerk Webhook Events
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.
Clerk Com 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.
Clerk Com Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Clerk Com Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Clerk API Rules
SPECTRALClerk API Rules
SPECTRALJSON Schema 14
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Clerk ActorToken
JSON SCHEMAClerk Client
JSON SCHEMAClerk EmailAddress
JSON SCHEMAClerk Invitation
JSON SCHEMAClerk JWTTemplate
JSON SCHEMAClerk OAuthApplication
JSON SCHEMAClerk Organization
JSON SCHEMAClerk OrganizationInvitation
JSON SCHEMAClerk OrganizationMembership
JSON SCHEMAClerk PhoneNumber
JSON SCHEMAClerk SAMLConnection
JSON SCHEMAClerk Session
JSON SCHEMAClerk SignInToken
JSON SCHEMAClerk User
JSON SCHEMAScroll within the panel for all 14 ·
JSON Structure 14
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Clerk Actortoken Structure
JSON STRUCTUREClerk Client Structure
JSON STRUCTUREClerk Emailaddress Structure
JSON STRUCTUREClerk Invitation Structure
JSON STRUCTUREClerk Jwttemplate Structure
JSON STRUCTUREClerk Oauthapplication Structure
JSON STRUCTUREClerk Organization Structure
JSON STRUCTUREClerk Organizationinvitation Structure
JSON STRUCTUREClerk Organizationmembership Structure
JSON STRUCTUREClerk Phonenumber Structure
JSON STRUCTUREClerk Samlconnection Structure
JSON STRUCTUREClerk Session Structure
JSON STRUCTUREClerk Signintoken Structure
JSON STRUCTUREClerk User Structure
JSON STRUCTUREScroll within the panel for all 14 ·
Examples 26
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Clerk Actortoken Example
EXAMPLEClerk Client Example
EXAMPLEClerk Emailaddress Example
EXAMPLEClerk Invitation Example
EXAMPLEClerk Jwttemplate Example
EXAMPLEClerk Organization Example
EXAMPLEClerk Phonenumber Example
EXAMPLEClerk Session Example
EXAMPLEClerk Signintoken Example
EXAMPLEClerk User Example
EXAMPLEScroll within the panel for all 26 ·
Security 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 Clerk — 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 2
Portal, sign-up, and the first successful call
Documentation 16
Reference material describing how the API behaves
Scroll within the panel for all 16 ·
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 16
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 16 ·
Build 17
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 17 ·
Access & Security 4
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 5
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/clerk-com · machine-readable index on apis.io