clerk-backend-api

Inspect and execute Clerk Backend REST API calls with Bearer authentication.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/koushik-hait/xigenis-landingpage-v1 --skill clerk-backend-api-koushik-hait
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk-backend-api
Source: https://github.com/koushik-hait/xigenis-landingpage-v1/tree/main/.agents/skills/clerk-backend-api
Command: npx skills add https://github.com/koushik-hait/xigenis-landingpage-v1 --skill clerk-backend-api-koushik-hait

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps you browse Clerk Backend REST API capabilities, inspect endpoint schemas, and safely execute authenticated calls for users and organizations without guessing request shapes or parameters.

Core Features & Use Cases

  • Tag and endpoint discovery: Lists available API tags and endpoints, so you can quickly find the right route for your task.
  • Endpoint inspection: Retrieves detailed request/response schemas (including referenced components) for a chosen endpoint.
  • Authenticated execution: Executes REST calls using Bearer auth with CLERK_SECRET_KEY, including safe parsing and response summarization.
  • Write safety guardrails: Enforces mandatory checks for CLERK_SECRET_KEY and CLERK_BAPI_SCOPES before POST/PATCH/PUT/DELETE, and requires explicit confirmation for irreversible DELETE actions.
  • Metadata management: Updates user metadata with correct handling of public_metadata vs private_metadata vs unsafe_metadata to match what you need the client/server to read and write.

Quick Start

Use clerk-backend-api to list users created in the last 7 days by running: /clerk-backend-api GET /users.

Frequently Asked Questions about clerk-backend-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explore and execute Clerk backend REST API calls for user management?

List recently created users in Clerk by running an authenticated GET request against the /users endpoint, using your CLERK_SECRET_KEY for Bearer authentication and parsing the JSON response with pagination-aware listing.

What is the correct way to update user metadata via the Clerk REST API?

Updating user metadata via the Clerk REST API requires selecting the correct metadata type, distinguishing between public_metadata, private_metadata, and unsafe_metadata to match client and server read and write permissions.

How do I safely create Clerk organizations and invite members with specific roles?

Safely create Clerk organizations and invite members by executing POST requests with Bearer authentication, passing mandatory preflight checks for CLERK_BAPI_SCOPES to ensure secure role assignment and member invitation.

Do I need to set CLERK_BAPI_SCOPES for write operations in the Clerk backend API?

Yes, mandatory preflight checks for CLERK_BAPI_SCOPES and CLERK_SECRET_KEY are enforced before executing any POST, PATCH, PUT, or DELETE write operations to ensure secure and authorized Clerk backend API modifications.

How are irreversible DELETE actions handled in the Clerk backend API?

Irreversible DELETE actions in the Clerk backend API require explicit confirmation before execution, ensuring that destructive operations like removing users or organizations are intentionally verified to prevent accidental data loss.