API keys are now available in public beta, allowing users to delegate access to an application’s API. This feature comes with built-in management tools integrated into the Clerk Dashboard. Once API keys are enabled, users can find an API Keys tab in their UserProfile and OrganizationProfile components, where they can create, view, and revoke keys. A dedicated APIKeys component can also be implemented anywhere in the application. Programmatic management of API keys is possible through the Backend SDK, giving developers control over scopes, claims, and expiration settings. The auth() helper allows for API key verification in the backend, with an example provided for Next.js. Key features include user and organization scoping, instant revocation using opaque tokens, defined scopes for access, custom claims for metadata storage, and optional expiration settings. During the beta phase, API keys are free to use. Once the service moves to general availability, a usage-based pricing model will be introduced: $0.001 per key creation and $0.00001 per key verification. Billing won’t activate immediately; users will receive at least 30 days' notice before charges begin. Usage statistics and monitoring tools will be available in the Dashboard for transparency. To get started, resources include a comprehensive API keys guide, a Backend SDK reference for key management, and a tutorial for building a SaaS application using Clerk and API keys. Feedback from users during the beta period is encouraged to improve the feature further. Users can connect through a feedback portal or join discussions in the Discord community for support.