Niches · Identity & business verification
Work the manual review queue and override decisions
Four or more companies' docs show a full fit.
What counts as done
The agent lists pending cases with age and reason, reads one case's evidence, and records an approve, decline or override with a reason that appears in an audit trail, all by API.
How agents ask for it: how far behind is KYC review
, approve this applicant, the document was fine
, show me the oldest pending case
, write up this alert for the compliance officer
Does the job 5
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| ComplyAdvantage D IVXS UK Limited (trading as ComplyAdvantage) | Get list of cases, get a case and its alerts, transition a case to a stage, bulk assign and leave notes, all by API, with case states listed by an endpoint. source |
| Didit BB Didit Identity Spain, S.L. | GET /v3/sessions filters by status and date with created_at; PATCH update-status sets Approved, Declined or Resubmitted with a comment saved on the audit trail. source |
| Middesk C Middesk, Inc. | GET /v1/businesses/{id}/review reads the findings, PATCH /v1/businesses/{id} sets a final status, and /v1/actions and /timeline record what happened. source |
| Persona B Persona Identities, Inc. | Cases API sets status and assigns cases, and inquiries can be approved or declined by API, with cases built for investigation and a decision. source |
| Sumsub B Sum and Substance Ltd | Get cases by filters lists cases, Update case status records the decision with stages, and the AML hit review and applicant review history endpoints give the audit trail. source |
Does the job, with a limit 5
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| ComplyCube B Teemo Technology Ltd | Advanced Case Management assigns, stages and records decisions with audit history, described as a Portal workspace; by API only check validation was found. source |
| Entrust Identity Verification (formerly Onfido) D Onfido Ltd | Workflow runs expose tasks and a task complete call, which a manual review step can use; no list of pending reviews by age was found in the spec. source |
| Plaid Identity Verification B Plaid Inc. | IDV pending_review sessions are reviewed in the Dashboard; Monitor hits can be reviewed by API, but the guide describes the Dashboard review as the usual path. source |
| Socure RiskOS B Socure Inc. | REVIEW decisions become cases in a Case Queue with reason codes and the execution trace, and Update an Evaluation State sets decision with notes by API. Listing pending cases by API wasn't found; queues are a Dashboard feature. source |
| Vouched C Vouched Identity, Inc. | Find Jobs filters by status (Warning means needs review) and date, and Update Job Review records a decision by API. No audit-trail field was found in the pages read. source |
Couldn't check 1
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Alloy D First Mile Group, Inc. | Not read: Alloy's Terms of Service forbid robots and automatic data gathering on alloy.com and related sites, so developer.alloy.com was not opened and no independent source covers this. |
Doesn't do this job 5
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Jumio D Jumio Corporation | No case or review endpoint; transaction review and deletion are portal actions. source |
| Shufti C Shufti Pro Limited | No case or review-queue endpoint for verifications was found; review happens in the back office. source |
| Stripe Identity A Stripe, LLC | Review tools and status override are Dashboard functions; no API to list pending reviews or record a decision was found. source |
| Trulioo C Trulioo Information Services Inc. | No case or review-queue endpoint appears in the API index. source |
| Veriff B Veriff OÜ | Manual review is done on the Verifications page of the Customer Portal; no API lists pending cases or records an override. source |
What stops agents finishing
- decision rights stay with a named human under the customer's compliance policy
- case actions only in the dashboard
Around it
Before: identity-verification.read-decision, identity-verification.screen-watchlist. After: human-in-the-loop.request-approval, messaging.send-message.
Where this comes from
Weight 8 of 100 in Identity & business verification: 2 of 34 accounts (an operator's assistant needing a KYC queue tool, an HN request for authorised human overrides); vendor pages for Didit, Sumsub, Persona, Alloy and ComplyAdvantage push agents here
The same as data: /api/v1/use-cases/identity-verification.review-case.json, or the MCP tool get_use_case with id identity-verification.review-case. Other jobs in this category: /api/v1/niches?category=identity-verification.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.