Login
sumsub/agent-skills2 files

Sumsub Check Permissions

Fetch the current tenant's allowed entitlements (BackgroundCheckTarget list). Returns JSON `{"allowedChecks":{key:label}}` — a map whose keys are the enabled entitlement keys. Called by sumsub-create-level (and other create-* skills) before building a payload to gate entitlement-required features.

Use this skillView repositoryView on skills.sh
Specification
Skill ID
sumsub/agent-skills/sumsub-check-permissions
Publisher
sumsub
Repository
agent-skills
Installs
0
Files
2
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

sumsub/agent-skills/sumsub-check-permissionsInstalls these files
  • SKILL.md
  • scripts/check_permissions.sh

What this skill tells the agent

Check Permissions

Returns the tenant's allowed entitlements so callers can gate features before making any API writes.

Usage

Run the script and parse the result:

bash ${CLAUDE_SKILL_DIR}/scripts/check_permissions.sh

Output: raw Sumsub response body followed by HTTP <code>.

Success (HTTP 200):

{"allowedChecks": {"REUSABLE_KYC_SDK": "Reusable KYC via API/SDK: ...", "VIDEO_IDENT": "Video Identification: ..."}}
HTTP 200

Error (non-200):

{"description":"Unauthorized","errorName":"...","correlationId":"..."}
HTTP 401
  • allowedChecks — map of permission key → human-readable label for all entitlements enabled for this tenant.
  • Permission keys present as keys of allowedChecks are the allowed entitlements.

How callers should use this

If the HTTP status is not 200, stop immediately — show the error body to the user and do not proceed.

After a successful response, check whether the required BackgroundCheckTarget key is present in allowedChecks. If it is not, stop immediately — do not build or POST the payload. Tell the user which entitlement is missing and that they need to contact their CSM or Sumsub Support to get it enabled.

Entitlement → feature mapping (key examples):

FeatureRequired entitlement
E_KYC docsetE_KYC_TARGET
PROOF_OF_RESIDENCE docsetPOA
E_SIGN docsetE_SIGN_TARGET
deviceIntelligenceSettings.enabled: trueDEVICE_INTELLIGENCE
QUESTIONNAIRE scoringQUESTIONNAIRE_SCORING
QUESTIONNAIRE attachmentsQUESTIONNAIRE_ATTACHMENT
NFC chip readingNFC
Video ident sessionsVIDEO_IDENT
Reusable KYC via SDKREUSABLE_KYC_SDK
Known face searchKNOWN_FACE_SEARCH
AML / watchlist stepWATCHLISTS

More from sumsub

sumsub/agent-skills

Sumsub Analyze Regulation

Analyze a regulation document (PDF or text) and produce a Sumsub configuration plan — mapping regulatory requirements to Sumsub entities (levels, questionnaires, PoA presets, TM rules, workflows, AML resolution rules). TRIGGER when the user provides a regulation PDF, legal act, or compliance requirement document and wants to know what to configure in Sumsub. Acts as the entry point before invoking sumsub-create-level, sumsub-create-questionnaire, sumsub-create-poa-preset, sumsub-create-workflow, sumsub-create-aml-resolution-rules, and other skills. SKIP for direct entity creation requests (no regulatory context) or Sumsub API calls.

sumsub/agent-skills

Sumsub API Auth

Authenticate to the Sumsub API with an App Token + secret key (HMAC-SHA256 request signing). TRIGGER when the user asks to "call / sign / authenticate Sumsub API requests", debugs `401 Unauthorized` / signature errors against `api.sumsub.com`, or needs a working request example with `X-App-Token` / `X-App-Access-Sig` / `X-App-Access-Ts` headers. SKIP only when a more specific skill in this repo (questionnaire/level/workflow/POA-preset/generic) already covers the user's actual task — those skills sign requests the same way and only need this one for auth deep dives.

sumsub/agent-skills

Sumsub API Generic

Catch-all fallback for any Sumsub API task that does NOT match a more specific skill (e.g. `create-sumsub-level`, `sumsub-create-questionnaire`, `sumsub-api-auth`). TRIGGER when the user wants to call, inspect, or debug a Sumsub API endpoint not otherwise covered — fetching applicants, listing levels, reviewing AML hits, exporting data, generating SDK tokens, anything against `api.sumsub.com`. The procedure — locate the right endpoint in the OpenAPI schema, read its request/response shape, build the payload, sign with App Token, and validate. SKIP whenever a narrower Sumsub skill already covers the request.

Use this skill in a project

Open any RiverX project, search the Skills panel for sumsub/agent-skills/sumsub-check-permissions, and install it in one click.

Use this skill