Niches · Identity & business verification

Set up or change the verification flow

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
4companies, fit with a limit
16companies carry the tag
12share of the category's work
6first-hand accounts

What counts as done

The requested setting is changed by API or MCP on the existing flow without converting or breaking it, and a new test session in sandbox shows the change; the agent can also explain why sessions are refused from account state (credit, plan limits).

How agents ask for it: only accept Mexican IDs, add a questionnaire to onboarding, set up KYC for our app, why are sessions being refused

Does the job, with a limit 4

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.

ListingWhy
Didit BB
Didit Identity Spain, S.L.
Workflow CRUD by API (PATCH /v3/workflows/{settings_uuid}/ on drafts) and MCP tools, with a deterministic sandbox. acc-09: accepting only Mexican documents was unreachable through the MCP and the workflow was converted; acc-10: refusals misread as low balance. source
Shufti C
Shufti Pro Limited
There is no stored flow: each request carries its own services, country and document supported_types, so a restriction is a parameter. Settings such as callback domains sit in the back office, and no account-state endpoint for refusals was read. source
Stripe Identity A
Stripe, LLC
Verification flows are created and edited in the Dashboard only; by API an agent can pass a verification_flow id or per-session options such as document.allowed_types and require_matching_selfie. No country restriction parameter was found. source
Sumsub B
Sum and Substance Ltd
The MCP server lists and reads verification levels, but no level create or edit endpoint was found in the reference; acc-11 saw the agent API reject every questionnaire update with 400. source

Couldn't check 1

The docs were closed to us, or silent. These carry no mark either way.

ListingWhy
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 11

Listings in the category that do something else, with the reason.

ListingWhy
ComplyAdvantage D
IVXS UK Limited (trading as ComplyAdvantage)
No verification flow to configure; the configurable object is a screening configuration. source
ComplyCube B
Teemo Technology Ltd
Workflows are designed in the Portal (template picker, steps, access restriction lists); no workflow create or edit endpoint appears in the API reference. source
Entrust Identity Verification (formerly Onfido) D
Onfido Ltd
Workflows are built in Workflow Studio; the spec has workflow run and task calls but no workflow create or edit. source
Jumio D
Jumio Corporation
Workflows and Accepted IDs are set per tenant through the portal and Jumio staff; the account API picks a workflow definitionKey but cannot edit it. source
Middesk C
Middesk, Inc.
No verification flow object; checks are chosen per business through orders and packages, and the enhanced sandbox is configured in the Dashboard. source
Persona B
Persona Identities, Inc.
Inquiry templates are configured in the Dashboard; the API lists templates and template versions but no create or edit call was found, and every change makes a new version. source
Plaid Identity Verification B
Plaid Inc.
Checks, country and document lists are set in a template through the Dashboard's Workflow Management editor; the API has only create, get, list and retry. source
Socure RiskOS B
Socure Inc.
Workflows are built in the RiskOS Dashboard Workflow Editor; the MCP server reads workflows but no create or edit endpoint was found. source
Trulioo C
Trulioo Information Services Inc.
Flows are built in Workflow Studio's builder; the Workflow Studio API runs a published flow but no create or edit call was found. source
Veriff B
Veriff OÜ
No API to create or edit flows; live integrations are created by a Solutions Engineer and settings sit in the Customer Portal. Session-level parameters only, and test sessions get no decision unless forced by hand. source
Vouched C
Vouched Identity, Inc.
No flow or template endpoint in the API index; job settings and review happen in the dashboard. source

What stops agents finishing

  • setting only reachable in the dashboard
  • edit endpoint rejects every update (Sumsub acc-11)
  • billing state misread as the cause of refusals (Didit acc-10)
  • self-serve sign-up not offered, demo request first

Around it

Before: code.read-repo. After: identity-verification.verify-person.

Where this comes from

Weight 12 of 100 in Identity & business verification: 4 of 34 accounts (Didit MCP production logs, Sumsub agent skills, Stripe Identity document types, self-serve sign-up); weight held near count

The same as data: /api/v1/use-cases/identity-verification.configure-flow.json, or the MCP tool get_use_case with id identity-verification.configure-flow. Other jobs in this category: /api/v1/niches?category=identity-verification.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.