clerk-backend-api

To run authenticated Clerk Backend API requests and list users, you must provide your CLERK_SECRET_KEY. The Skill formats API responses for easy review, allowing you to safely explore endpoints and execute GET requests.

Yes, you can manage organizations and invite members using the Clerk REST API. The Skill provides fast-path operations for these common tasks while enforcing mandatory scope checks for write operations.

The safest way to explore Clerk v1 API endpoints and schemas is through a guided interface that enforces mandatory checks for write operations. This prevents accidental modifications while you inspect available REST endpoints.

Yes, you need a CLERK_SECRET_KEY to execute POST, PATCH, or DELETE requests against Clerk. The Skill enforces mandatory checks for these write operations to ensure authenticated and secure API execution.

When calling Clerk API endpoints, limitations apply to write operations which require mandatory scope checks. The Skill enforces these precautions automatically, ensuring you only execute authorized POST, PATCH, and DELETE requests.

The Clerk API Explorer handles response formatting by structuring API outputs for easy review. This allows you to quickly inspect user lists, organization details, and endpoint schemas returned from authenticated requests.