Clerk
Clerk is a user management and authentication provider that supplies sign-in methods, sessions, multi-factor authentication and organisation and role models for multi-tenant applications.
Clerk provides sign-in, session management and organisations as a ready-made service including UI components. For agentic applications the important part is the question of on whose behalf an agent acts — and with which permissions.
Explanation
Authentication is one of the areas where building your own is rarely wise. Clerk encapsulates sign-in paths, session lifecycle and organisation structures — several users belonging to one customer with different roles. In agentic systems this becomes a governance question: an agent calling tools needs an identity. If it acts with the signed-in user's permissions, damage is contained; if it acts with a service key, every access rule is bypassed.
Marketing Relevance
For B2B applications with customer logins, the auth layer determines how quickly a portal can ship. For agents it determines how far a mistake reaches. Both should be settled before the first customer login, not after.
Example
A customer portal gives each customer an organisation with several users. The in-portal assistant fetches reports strictly with the signed-in user's token — so it cannot see another organisation's data even if an instruction tries to trick it into doing so.
Common Pitfalls
The most common mistake is an agent with an all-powerful key: permissions are checked in the UI but bypassed in the tool call. Second mistake: user data lives both at the auth provider and in your own database, with no deletion process covering both sides.
Origin & History
Clerk emerged from 2020 as an answer to the effort of building sign-in yourself in modern frontends and grew alongside React and Next.js applications. From 2024 the focus of many vendors shifted to B2B requirements: organisations, invitations, single sign-on.
Further Resources
Marketing Use Cases
Customer portals with organisations, roles and invitations.
Identity for agents calling tools on behalf of a user.
Multi-factor authentication for internal tools with data access.
Frequently Asked Questions
Do I need Clerk if I already use Supabase Auth?
No. Both solve the same job. Clerk becomes interesting when organisation and B2B features are needed off the shelf; if you already run Postgres with row level security, the built-in solution is usually simpler.
How should an agent be authenticated?
With the identity of the user it works for, and with the same permission checks as the UI. Service keys belong only in flows without a user context — and even there with a narrow scope.
Related Services
Go deeper: Agentic AI Hub · Governance & compliance