Sumsub

Bring your compliance operations into ChatGPT. Connect to your Sumsub account to onboard applicants, generate verification links, and pull live data on identities, businesses, transactions, AML screening cases, and fraud networks—all in plain language. Triage your review queue by risk, assemble due-diligence dossiers, investigate suspicious activity, and draft regulatory reports without clicking through the Dashboard. Turn full-cycle verification into an AI-powered workflow that moves at the speed of conversation.

View in the ChatGPT registry

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Security
Primary Subcategory: Compliance, Risk & Privacy Operations
Secondary Subcategories: Email Clients & Inbox Assistants
Brand: Sumsub
Access: Account required
First tracked: 2026-06-16
Tool count: 17
Geography: US

ChatGPT Plugin Discoverability Score

ChatGPT organic discovery is not live yet

Sumsub is tracked in the ChatGPT Plugin registry. Public organic-discovery measurement is not live for ChatGPT yet, so there is no score to publish today.

Get notified when your score goes live

Enter your work email and we’ll notify you when ChatGPT Plugin organic discovery scoring launches.

No spam. Unsubscribe any time.

Talk to our team

Primary Subcategory

Competing in ChatGPT Compliance, Risk & Privacy Operations

View Category

Listed in alphabetical order

Primary Subcategory

ClearPolicyOrganic discovery is pendingGet the score at launch

ConsentLayerOrganic discovery is pendingGet the score at launch

D&B Risk AnalyticsOrganic discovery is pendingGet the score at launch

IntelligoOrganic discovery is pendingGet the score at launch

SumsubOrganic discovery is pendingGet the score at launch

Score explained

How the Discoverability Score works

Organic discovery scoring for Sumsub on ChatGPT is not live yet. The score will use measured agent conversations when it launches.

InvisibleBuriedEmergingCompetitiveWinning

Organic discovery scoring is pending. Your Plugin score will appear on this scale when measurement goes live.

FoundDiagnostic

Whether Claude found your Plugin in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.

PickedMain score

How often your Plugin appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.

PositionedDiagnostic

What position your Plugin appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.

Read the full scoring methodology Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.

Tools

17 tools agents can invoke

Create a new company (legal-entity) applicant in Sumsub for KYB verification. Use this tool for business onboarding — companies, partnerships, trusts and other legal entities. For natural persons use applicant_create_individual instead. The applicant is registered against the given verification level and returned with its newly-assigned Sumsub id.
applicant_create_company
Create a new individual (natural person) applicant in Sumsub for KYC verification. Use this tool for personal identity verification of people, not legal entities. The applicant is registered against the given verification level and returned with its newly-assigned Sumsub id.
applicant_create_individual
Generate an external WebSDK verification link. Creates a unique URL that directs users to the Sumsub verification flow for a specific verification level. The link has a configurable time-to-live and can be sent via email, SMS, or embedded in custom workflows.
verification_link_create
Get complete applicant data by ID - returns full profile with verification status, documents, and review results
applicant_get
Get the latest AML (Anti-Money-Laundering) screening case for an applicant. Returns the case id; the case review answer; each watchlist hit with its name, entity type, sources (each typed watchlist / media / related, with name and url) and per-hit match status; risk labels (e.g. pep, sanctions, terrorism, crime, adverseMedia, fitnessProbity); and whether ongoing monitoring is enabled.
applicant_aml_case_get
Get current verification status of an applicant - lightweight endpoint that returns only status information without full profile data. Returns verification process status including reviewStatus (init, pending, queued, awaitingUser, onHold, prechecked, completed, or awaitingService), reviewResult (GREEN/RED/YELLOW), processing stage, and moderation comments. Use this when you only need to check status quickly, rather than fetching full applicant data.
applicant_status_get
Get chronological timeline of all events in an applicant's verification journey (audit trail). Returns paginated list of events in reverse chronological order (newest first) including: applicant creation, document uploads, review actions, status changes, AML checks, notes added, tags modified, and system actions. Each event includes timestamp, event type, actor (who/what triggered it), and event-specific details. Critical for audit trails, compliance documentation, troubleshooting verification delays, and understanding applicant journey. Use offset for pagination through long timelines.
applicant_timeline_get
Get single questionnaire by its unique text ID. Returns complete questionnaire definition with sections, questions, and configuration. Use this to retrieve specific questionnaire details by ID (e.g., 'palmut', 'kyc-basic').
questionnaire_get
Get a single KYT transaction by ID, optionally including its review notes. Returns the full transaction — scoring, review status, and transaction details. Pass includeNotes=true to also fetch and embed a `notes` array of analyst notes attached to the transaction (each note has its text, author, timestamp, and tags).
transaction_get
Get single verification level configuration by ID with complete step configuration, document requirements, and AML settings
verification_level_get
Answers a single user question about Sumsub using the official Sumsub documentation knowledge base. Call this whenever the user asks "how do I…", "how does X work in Sumsub", "where do I configure…", or otherwise needs procedural guidance about Sumsub — verification levels, applicant workflows, KYC/AML configuration, API integration, dashboard settings, webhooks, sandbox setup, transaction monitoring, etc. Pass the user's exact question (rephrased into a complete English sentence if needed) as the `question` argument; the tool returns a Markdown answer with linked source pages.
how_to_sumsub
Get fraud network analysis for an applicant showing connections to other applicants through shared identifiers. Returns fraud network data including related applicants, risk indicators, common factors (email, device fingerprint, phone, IP address, document numbers), and network statistics for fraud detection and prevention.
applicant_fraud_network_list
List applicants. Required `type` selects individual (KYC) or company (KYB). Optional filters: searchTerm (text search by name/applicantId/externalUserId/email/phone), country, date range, platform, review `status` (single value from the applicant lifecycle enum), level, externalUserId, clientId, rejectLabels, tags. Returns applicants with verification statuses, rejection reasons, and pagination.
applicant_list
Get questionnaires configured in the dashboard. Returns questionnaire definitions with their IDs, names, sections, and question items. Use questionnaire_get to get a single questionnaire by ID.
questionnaire_list
List, filter and search KYT transactions. Returns a paginated list of transactions matching the given criteria, each with scoring, review status, amount, currency, direction, parties and Travel Rule details. Filtering supports three combinable styles: (1) a high-level status preset via 'kytStatus'; (2) named filters combined with AND — transaction type, direction (in/out), date range (dateFrom/dateTo), amount range, risk score range, currency code, review status, confirmation, VASP counterparty, Travel Rule status, masking flag, platform event type, applicant; (3) an advanced 'criteria' tree using $or/$and and the operators =, <>, >, >=, <, <=, $contains over field paths such as data.type, data.info.direction, data.info.currencyCode, data.txnDate, score, review.reviewStatus, review.reviewResult.reviewAnswer, travelRuleInfo.status, etc. Supports free-text search (searchTerm).
transaction_list
Get paginated summaries of verification level configurations. Returns lightweight list items for discovery and navigation. Use verification_level_get for the full configuration of one level. Not the applicant-workflow routing graph.
verification_level_list
Report a capability gap in the Sumsub MCP server. You MAY call this tool when you: - looked for a tool that doesn't exist, - got incomplete results from a tool, - had to approximate the user's request, or - hit a parameter/format limitation. Describe the gap in abstract terms. Do NOT copy user PII, applicant IDs, transaction IDs, names, or chat contents into the arguments — use placeholders ("a specific applicant", "a recent transaction") instead of real values.
feedback

Sumsub FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Sumsub alternatives on ChatGPT?

As of 2026-08-14, Sumsub competes with ClearPolicy, ConsentLayer, D&B Risk Analytics, Intelligo in ChatGPT Compliance, Risk & Privacy Operations, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.