clerk-backend-api

Execute Clerk Backend REST API requests safely by enforcing bearer authentication with CLERK_SECRET_KEY. The system validates CLERK_BAPI_SCOPES before write operations and requires explicit confirmation for irreversible deletes to prevent accidental destructive actions.

Update user public metadata safely without overwriting existing fields using fast-path templates. The system parses JSON responses to provide clear summaries, ensuring your metadata updates target specific data points without destroying prior information.

Supported Clerk Backend API operations include listing users, creating organizations, inviting members, managing invitations, and deleting user accounts. These authenticated backend operations are executed via curl-based JSON requests with parsed response summaries.

Yes, you need CLERK_BAPI_SCOPES to perform write or delete operations. The system checks these scopes before authorizing write operations and requires explicit confirmation when issuing irreversible delete requests against user accounts.

Yes, you can list users created in the last 7 days using the Clerk Backend API. The skill provides fast-path templates for routine operations like listing users, executing authenticated curl-based JSON requests and parsing the responses.

The Clerk Backend API requires explicit confirmation for deleting user accounts because deletes are irreversible. This guardrail warns you before executing destructive actions, ensuring accidental data loss does not occur during backend management.