# Set up or change the verification flow

> Set up or change the verification flow: 0 companies fully do it, 4 with a limit, 16 carry the tag. Every listing in Identity & business verification with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/identity-verification.configure-flow/
- Markdown: https://www.anchorterminal.com/niches/identity-verification.configure-flow/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/identity-verification.configure-flow/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/identity-verification.configure-flow/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

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

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 4 | 16 | 12 | 6 |

## 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

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.

- **Didit (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.
- **Shufti (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.
- **Stripe Identity (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.
- **Sumsub (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.

## Couldn't check

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

- **Alloy (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.

- not this job: ComplyAdvantage (IVXS UK Limited (trading as ComplyAdvantage)): No verification flow to configure; the configurable object is a screening configuration.
- not this job: ComplyCube (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.
- not this job: Entrust Identity Verification (formerly Onfido) (Onfido Ltd): Workflows are built in Workflow Studio; the spec has workflow run and task calls but no workflow create or edit.
- not this job: Jumio (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.
- not this job: Middesk (Middesk, Inc.): No verification flow object; checks are chosen per business through orders and packages, and the enhanced sandbox is configured in the Dashboard.
- not this job: Persona (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.
- not this job: Plaid Identity Verification (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.
- not this job: Socure RiskOS (Socure Inc.): Workflows are built in the RiskOS Dashboard Workflow Editor; the MCP server reads workflows but no create or edit endpoint was found.
- not this job: Trulioo (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.
- not this job: Veriff (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.
- not this job: Vouched (Vouched Identity, Inc.): No flow or template endpoint in the API index; job settings and review happen in the dashboard.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/identity-verification.configure-flow.json, or the MCP tool get_use_case with id identity-verification.configure-flow. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
