Didit

@Didit check our prepaid credit balance and show me the auto-refill threshold before I launch the next batch of verifications.

Your organization currently holds 2,450 Didit credits. Auto-refill is enabled with a threshold of 500 credits—when your balance drops below that level, the system will automatically purchase 5,000 credits using the payment method on file. Each standard KYC verification consumes approximately 10–15 credits depending on the workflow configuration and document types submitted.

This example demonstrates read-only billing visibility before you commit to credit-consuming operations. Useful for cost control when planning bulk verification campaigns. Requires the Didit API key to have billing:read scope; does not trigger any charges or side effects.

@Didit create a new KYC verification session using our 'Standard Identity' workflow for user emma.chen@example.com and give me the hosted URL.

Verification session created successfully. Session ID: vs_8x3kLm9pQr2. The hosted verification URL is https://verify.didit.me/s/vs_8x3kLm9pQr2—send this link to Emma Chen so she can complete identity document upload, liveness check, and address proof. An invitation email was not sent automatically; you must share the URL directly. This session will consume credits only when the user submits documents and Didit runs the verification checks.

This write action provisions a billable resource and returns a URL your end user must visit. The MCP does not send the invitation email unless you explicitly request it in the prompt. Verify your workflow ID and user email are correct before running—session creation is immediate and may decrement your credit balance once the user starts.

@Didit pull all user profiles created in the last 30 days, then summarize how many passed, failed, or are still pending verification.

Didit returned 47 user profiles. Of those, 34 users passed verification (status: approved), 8 failed due to document mismatch or liveness issues (status: rejected), and 5 remain in pending status awaiting manual review or additional documents. Note that Didit's List Users endpoint does not support date-range filters, so this summary reflects all profiles in your account; I filtered by creation timestamp client-side to isolate the last 30 days.

This synthesis example pairs the MCP's list capability with AI reasoning to produce a status breakdown. Be aware that Didit does not offer server-side filtering—large account datasets may require pagination and client-side filtering, which can be slow. The MCP fetches raw profile arrays; the AI performs the aggregation and date logic.

When Didit fits a regulated onboarding flow with light volume

A 6-person fintech startup runs KYC on 40-60 new users per month and needs audit trails for their banking partner. Didit works here because the team can create verification sessions from Switchy, check billing balance before each batch, and pull complete decision reports into a shared context when the compliance lead reviews flagged accounts. The Get Verification Decision and Get User tools give you the full provider record without leaving the workspace, so the ops person and the engineer can triage edge cases together in one thread. The threshold: if you're onboarding 500+ users a month or need real-time webhook orchestration, you'll outgrow the list-and-fetch pattern fast. For early-stage regulated products where a human reviews every decision anyway, this MCP turns Didit's API into a compliance copilot.

Why Didit's KYB tools help marketplace ops at sub-100 seller scale

A marketplace with 30 active sellers uses Didit for business verification before payout approval. The ops lead creates a KYB session in Switchy when a new seller applies, then fetches the business profile and decision report once verification completes. List Businesses and Get Business let the team spot patterns across flagged sellers without opening the Didit dashboard—useful when the trust-and-safety person and the payments engineer need to decide together whether to approve a borderline case. The catch: Didit's list endpoints don't support filters or search, so if you're vetting 200+ businesses a month, you'll spend more time scrolling than deciding. For small marketplaces where every seller gets individual attention, this MCP keeps verification context in the same workspace as your payout and fraud discussions.

When Didit's workflow config lookup speeds multi-client compliance setup

A 4-person compliance consultancy manages KYC workflows for 8 fintech clients, each with different risk appetites and verification requirements. The Get Workflow tool lets the team pull a client's full configuration and pricing into Switchy when scoping a new project or troubleshooting a session failure. Instead of screenshotting the Didit dashboard or asking the client to export settings, the consultant fetches the workflow version in a shared thread and walks the client through trade-offs in real time. The limit: if you're running dozens of workflows or need to diff configurations programmatically, the 10-tool MCP won't give you bulk export or comparison logic. For agencies where each client conversation is bespoke and the workflow config is the source of truth, this MCP turns Didit into a scoping artifact you can reference mid-conversation.