How do I install the Sumsub Check Permissions skill?

Run npx skillmds@latest add sumsub/sumsub-check-permissions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sumsub Check Permissions safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sumsub Check Permissions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sumsub Check Permissions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sumsub Check Permissions?

sumsub (@sumsub) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sumsub Check Permissions by sumsub — Agent Skill

Name: Sumsub Check Permissions
Rating: 4.5 (4 reviews)
Author: sumsub

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.

sumsub Updated Sep 10, 2026

File contents

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):

Feature	Required entitlement
`E_KYC` docset	`E_KYC_TARGET`
`PROOF_OF_RESIDENCE` docset	`POA`
`E_SIGN` docset	`E_SIGN_TARGET`
`deviceIntelligenceSettings.enabled: true`	`DEVICE_INTELLIGENCE`
`QUESTIONNAIRE` scoring	`QUESTIONNAIRE_SCORING`
`QUESTIONNAIRE` attachments	`QUESTIONNAIRE_ATTACHMENT`
NFC chip reading	`NFC`
Video ident sessions	`VIDEO_IDENT`
Reusable KYC via SDK	`REUSABLE_KYC_SDK`
Known face search	`KNOWN_FACE_SEARCH`
AML / watchlist step	`WATCHLISTS`

---name: sumsub-check-permissionsdescription: 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.---# Check PermissionsReturns the tenant's allowed entitlements so callers can gate features before making any API writes.## UsageRun the script and parse the result:```bashbash ${CLAUDE_SKILL_DIR}/scripts/check_permissions.sh```Output: raw Sumsub response body followed by `HTTP <code>`.Success (HTTP 200):```json{"allowedChecks": {"REUSABLE_KYC_SDK": "Reusable KYC via API/SDK: ...", "VIDEO_IDENT": "Video Identification: ..."}}HTTP 200```Error (non-200):```json{"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 thisIf 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):| Feature | Required entitlement ||---|---|| `E_KYC` docset | `E_KYC_TARGET` || `PROOF_OF_RESIDENCE` docset | `POA` || `E_SIGN` docset | `E_SIGN_TARGET` || `deviceIntelligenceSettings.enabled: true` | `DEVICE_INTELLIGENCE` || `QUESTIONNAIRE` scoring | `QUESTIONNAIRE_SCORING` || `QUESTIONNAIRE` attachments | `QUESTIONNAIRE_ATTACHMENT` || NFC chip reading | `NFC` || Video ident sessions | `VIDEO_IDENT` || Reusable KYC via SDK | `REUSABLE_KYC_SDK` || Known face search | `KNOWN_FACE_SEARCH` || AML / watchlist step | `WATCHLISTS` |

Frequently asked questions