clerk-backend-api

What it does

• For common operations (list users, create org, invite, update metadata, delete user): use the FAST PATH above — do NOT fetch specs first.
• Always disregard endpoints/schemas related to platform.
• Always confirm before performing write requests (POST/PUT/PATCH/DELETE).
• For metadata operations, always explain all three types (public, private, unsafe) and recommend the appropriate one.
• Pagination: always use limit + offset and mention that results may be paginated for large datasets.
• Use direct curl commands for all API calls — never use scripts/execute-request.sh.
• ${path} — e.g. /users/{userid}

Requirements & configuration

• currentUser() makes a real API call that counts against rate limits. Use auth() for just the session claims — it reads from the token without an API call.

Configuration: ARGUMENTSCLERK_SECRET_KEYCLERK_BAPI_SCOPESUSER_IDORG_IDEMAILRESPONSE