Head to head · Identity verification · October 2026 research run

Middesk vs Veriff

Veriff scores 64.8 (B) on agent readiness against Middesk's 57.5 (C), and leads in 5 of 7 scored categories. Middesk leads on agent ergonomics. Both do identity verification.

Best identity and business verification APIs for AI agents · All 119 verification comparisons

Which one, for what

Middesk C

Best for An agent onboarding or re-checking US businesses for a bank, lender or marketplace that already holds a Middesk contract, with registry, TIN, sanctions and lien data in one object.

Ahead on

  • Agent ergonomics, 56 against 43

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No public price. Fees are set in an order form, and every docs page ends with a prompt to contact sales

Veriff B

Best for A team that needs document and selfie verification with public per-verification prices and a trial, and that can run a webhook receiver and HMAC signing.

Ahead on

  • Reliability, 67 against 62
  • Security & auth, 63 against 56
  • Payments & pricing, 60 against 15
  • Maintenance & community, 74 against 64
  • Transparency & trust, 69 against 62

Watch for

No server-side SDK and no MCP server. Official packages cover only browser and mobile capture

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Veriff +45

Middesk 15

No x402, MPP or L402 (0). No public price. Fees are set in an order form and middesk.com/pricing returns 404 (0). A sandbox with mock data comes with an account, and the vendor's plugin README says trial accounts issue test keys. We couldn't establish how a trial is opened or whether it needs a card, so half credit (10). Access starts with a demo request and a dashboard sign-in (0). All per the 8 October check, not re-read on 4 November. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Veriff 60

No x402, MPP or L402 (0). Per-verification prices are public, at $0.80, $1.39 and $1.89 with monthly minimums of $49, $99 and $209, and add-ons priced per verification (20). A 15-day trial of up to 50 sessions with no card, plus free test integrations. The trial starts after the account holder passes identity verification (20). Signup is a browser flow and keys come from the Customer Portal (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Agent ergonomics Middesk +13

Middesk 56

List endpoints return a simplified business item, and a few reads take include, but the full Business object is large (the Markdown reference page for create business is 1.4 MB) and field selection through GraphQL is early access. The MCP server has eleven tools per the vendor's README (14). page and per_page with has_more and total_count, and filters on signals, mail and sub-accounts. The spec shows no filters on the business list (15). Errors are a JSON array of messages with an optional parameter, with no machine-readable codes (12). No idempotency key header. external_id is an idempotency key for sub-accounts only, lien continuations return the one in flight, and MCP annotations couldn't be read (8). Only name and addresses are required to create a business, but no official SDK was found in any language (7). All per the 8 October check, not re-read on 4 November.

Veriff 43

No field selection. The decision response is large and its content depends on the integration's configuration, with person, media and watchlist data on separate endpoints (10). No endpoint lists sessions and no pagination or filtering was found, so every read needs a stored session ID (6). Errors return status fail with a numeric code and message, with tables explaining each code (16). No idempotency key on POST /v1/sessions, so a retry creates a second session. Reads are safe to repeat (5). The minimum request is an empty verification object, but most calls need an HMAC signature whose input differs by method, and there is no server-side SDK in any language, only signing samples in JavaScript, C#, PHP and Python (6).

Maintenance & community Veriff +10

Middesk 64

Latest changelog entry 5 October 2026, 30 days before 4 November, per the 8 October check, not re-read on 4 November (30). Nine dated entries between 20 July and 5 October, at least three of them after 6 August (20). Closed service with a weekly changelog, a help centre and support in standard hours under the terms. No public issue tracker or community channel was found (9). No official SDK, and the MCP server isn't in the official registry. The middesk/plugins repository (plugins at 0.1.0, no tags or releases) has five commits from 16 September to 8 October 2026, the last two editing the verify skills (3). No published packages, and the plugins repository has no CI (2).

Veriff 74

Release notes dated 30 October 2026 (Android SDK 14.0.1 and React Native SDK 14.0.1), after Android and iOS SDK 14.0.0 on 26 October (30). Nine dated releases since 4 August, among them iOS 10.5.0 and 10.5.1, Flutter 7.1.0 and 7.2.0, Cordova 4.0.0 and the 14.0 SDKs (20). Closed service with dated release notes and per-page changelogs. Support articles sit behind a Customer Portal login and we found no public developer forum (9). Mobile and web capture SDKs are current, but there is no server-side client or MCP server (10). @veriff/js-sdk 2.0.0 dates from September 2025 and @veriff/incontext-sdk 2.5.0 from August 2025, per the 8 October check, not re-read on 2 November. CI wasn't checked (5).

Security & auth Veriff +7

Middesk 56

Revocable API keys split by environment, sub-account keys managed through the API, and OAuth 2.0 with read_only and read_write scopes and a revoke endpoint. OAuth access tokens don't expire, there's no consent screen, and an API key carries full account access (24). A read_only token is limited to GET, the sandbox is a separate host and key, and an IP allowlist applies. The MCP server advertises only read_write, and no approval step for billable writes was found in the API (12). Responses carry text from websites, adverse media and an LLM-written analyst summary, and no guidance on prompt injection was found (3). Actions record who changed a business and what changed, and a timeline endpoint lists events. No log of API calls for the operator was found (7). SOC 2 Type II audited annually and a Vanta trust centre. No security.txt, disclosure policy or bug bounty found (10). All per the 8 October check, not re-read on 4 November.

Veriff 63

An API key plus HMAC-SHA256 signatures with a shared secret that never travels. Up to five secrets per integration, shown once, with documented rotation and deletion. No scopes, and session creation needs only the API key (22). No read-only credential. Test and live integrations are separate, DELETE is off by default and capped at 10 in 24 hours, and Enterprise plans can restrict the Public API by IP allowlist (10). Responses carry text extracted from documents and watchlist and adverse media hits, with no injection guidance found (3). An Activity Log in the Customer Portal since 4 May 2026 and a webhooks tab per session (10). ISO/IEC 27001:2022 with 27017 and 27018, SOC 2 Type II, Cyber Essentials and a bug bounty on Intigriti paying 50 to 6,000 euros. security.txt returns 404 (18).

Transparency & trust Veriff +7

Middesk 62

Closed service with public terms last updated 21 August 2026, and MIT plugins (15). The terms bar training generative AI models on customer data and limit ML training to de-identified data. The privacy policy of 2 November 2025 keeps data as long as necessary with no periods, and no public DPA was found (14). The API change policy promises advance notice and an opt-out for breaking changes without a notice period, the terms give 60 days' notice before data is withdrawn, and the changelog labels breaking changes (10). Socure is named for identity checks. No subprocessor list or data location was found outside the trust centre, which we couldn't read (4). All per the 8 October check, not re-read on 4 November.

Veriff 69

Closed service. The terms of service page returned no terms text to our fetch on 8 October and wasn't re-read on 2 November, so licence clarity rests on the pricing page and privacy notice (10). The privacy notice, last updated 16 April 2026, describes Veriff as processor for customers, and the pricing page gives retention of 3 or 6 months by plan and 2 years as an add-on. The notice also says session data may be used for machine learning under the customer contract, and no public DPA was found, per the 8 October check (20). Fields are marked deprecated in the spec with dated changelog entries, such as matchStatus on 8 July 2026, and a backwards compatible changes list is published. The status page gave notice on 9 September 2026 that the legacy API and session hosts close on 9 December 2026, with the new hosts running in parallel. No written notice period was found (13). A sub-processor list is linked from the privacy notice but needs JavaScript, and AWS is named for backups (8).

Reliability Veriff +5

Middesk 62

Graded on the REST API with the hosted-service lines, per the 8 October check, not re-read on 4 November. Middesk's website terms bar any automated use of the Site, including robots and data gathering tools, and this run pauses such hosts pending a ruling. status.middesk.com is a Statuspage site on Middesk's own domain, per the 8 October check (20). The 8 October incident reading came from the page's /api/ path, which its robots.txt disallows, so it is struck, and with nothing readable today the window from 6 August is unread (5). 20 requests a second per customer is published (15). 429 is a documented status with Retry-After for sandbox business creation, and safe retries are documented for sub-account creation (external_id) and lien continuations. No general idempotency key was found, so this is safe-retry guidance on some writes (12). No SLA in the public terms (0). REST v1 is generally available (10).

Veriff 67

Graded on the Public API v1 with the hosted lines. Statuspage at status.veriff.com with API, End User Flow, Verification Decisions, Webhooks and Station components by region (20). Nine incidents between 4 August and 2 November 2026, each partial by its own text. Six were delayed decisions for some sessions or the US region (6 August, 1 and 4 September, 1, 27 and 28 October), and the 28 October update says API performance wasn't affected. On 26 August a subset of end users saw errors in the verification flow for about 22 minutes, on 7 October webhooks for expired and abandoned sessions were degraded, and on 23 October address parsing was degraded for nearly six hours. Minor only, so 20 on the checklist, where the 8 October check gave 15 for frequency (20). Session creation is capped at 30 a minute on Self-Serve and 600 on Enterprise, and deletion at 10 in 24 hours. No figures found for other endpoints (12). The spec documents a 429 with code 1004. No Retry-After, backoff guidance or idempotency key found, though webhooks retry for a week and polling the decision endpoint is the documented fallback (5). No SLA found on the pricing, security or Trust Centre pages (0). GA (10).

Score by category

CategoryWeightMiddeskVeriffEdge
Reliability16%6267Veriff +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8282even
Agent ergonomics13%5643Middesk +13
Security & auth14%5663Veriff +7
Payments & pricing10%1560Veriff +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6474Veriff +10
Transparency & trust7%6269Veriff +7
Negative events≤1500
TotalC 57.5/100B 64.8/100

Facts side by side

FactMiddeskVeriff
KindHTTP APIHTTP API
VendorMiddesk, Inc.Veriff OÜ
Hosted endpointhttps://api.middesk.com/v1no (local only)
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPaidPay per use
x402nono
LicenceProprietary service under Middesk's Business Verification Terms and Conditions. The Claude Code and Codex plugins on GitHub are MITProprietary service. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk)
Tools exposed11none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-052026-10-30
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date given2026-04-16
Customer content may train modelsyesyes
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity2 stars32 stars, 110k npm/wk
Agent reviewsnone3.3/5 (4)

How the scores have moved

Verdicts

Middesk

A public OpenAPI 3.1 contract for 87 operations, llms.txt, Markdown docs and a dated weekly changelog make the REST API readable to an agent, and OAuth has a read-only scope. Access is sales-led. No price, self-serve signup or official SDK was found, and the hosted MCP server rejects sandbox keys.

Veriff

Per-verification prices are public from $0.80, with a 15-day trial of 50 sessions and no card. Each endpoint page is Markdown with an OpenAPI 3.0 fragment. There is no server SDK, MCP server or idempotency key, most calls need an HMAC signature, and legacy API hosts close on 9 December 2026.

Before you call either

Middesk

  1. Match the key to the host. mk_test keys work only at https://api-sandbox.middesk.com/v1 and mk_live keys only at https://api.middesk.com/v1
  2. Name the orders on POST /v1/businesses. Omitting them places a verification order plus every package the account runs automatically, all billed
  3. Send address_line1 and address_line2. The API ignores address_line_1 without an error
  4. A 201 means the business was created, not verified. Wait for the business.updated webhook or poll until status leaves pending
  5. Stay under 20 requests a second per account, and in sandbox wait the seconds in Retry-After after a 429 on business creation

Veriff

  1. Take the base URL from the integration's API keys page. Send X-AUTH-CLIENT on every call and store verification.id from POST /v1/sessions
  2. Sign POST and PATCH bodies, and the session ID on GET and DELETE, with HMAC-SHA256 in X-HMAC-SIGNATURE. POST /v1/sessions needs no signature
  3. Stay under 30 session creations a minute on Self-Serve, 600 on Enterprise. A 429 carries code 1004
  4. Don't blindly retry POST /v1/sessions. Each call makes a new session, which is billed on a live integration
  5. Poll GET /v1/sessions/{id}/decision until verification is not null, or accept webhooks within 5 seconds and treat duplicates as normal
  6. Call the new hosts, such as api-saas.veriff.com, api-eu.veriff.com or api-us.veriff.com. The legacy hosts, among them stationapi.veriff.com, close on 9 December 2026

Questions

Which is better for AI agents, Middesk or Veriff?

Veriff scores 64.8 (B) on agent readiness against Middesk's 57.5 (C), and leads in 5 of 7 scored categories. Middesk leads on agent ergonomics.

Do Middesk and Veriff need an API key?

Middesk takes an API key or an OAuth sign-in. Veriff needs an API key.

Can an agent call Middesk and Veriff without installing anything?

Middesk has a hosted endpoint at https://api.middesk.com/v1. No hosted endpoint is listed for Veriff.

Other comparisons with Middesk or Veriff

Machine-readable

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.