{ "data": { "a": { "slug": "plaid-identity-verification", "name": "Plaid Identity Verification", "vendor": "Plaid Inc.", "vendorUrl": "https://plaid.com/products/identity-verification/", "kind": "http-api", "category": "identity-verification", "summary": "Plaid Identity Verification checks a person against data sources, identity documents, selfies with liveness and SMS, with risk scoring and optional Monitor watchlist screening. Sessions run in Plaid Link or through a backend-only API flow.", "url": "https://www.anchorterminal.com/tools/plaid-identity-verification", "markdownUrl": "https://www.anchorterminal.com/tools/plaid-identity-verification.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/plaid-identity-verification.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/plaid-identity-verification.json", "repo": "https://github.com/plaid/plaid-openapi", "license": "Proprietary service under Plaid's developer policy and end-user terms. The OpenAPI file and client libraries are MIT", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "plaid" }, { "registry": "pypi", "name": "plaid-python" } ], "auth": "api-key", "authNotes": "`client_id` and `secret` in the JSON body of each POST to https://sandbox.plaid.com or https://production.plaid.com, with a separate secret per environment. No scopes. Sandbox for Identity Verification is enabled self-serve from the Dashboard Products page (since 12 August 2026). Production needs a product access request, and the integrating company must be based in the US, Canada or the UK (checked 2026-10-14).", "pricing": "paid", "pricingNotes": "No public prices. Each session is billed an Anti-Fraud Engine fee plus fees for data source verification (by country), document checks and selfie checks, and retries are billed as new sessions. Exact rates appear after applying for Production. Sandbox is free (https://plaid.com/docs/account/billing/, checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Identity Verification docs, the API reference or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 1238045, "pypiWeekly": 656200, "asOf": "2026-10-14" }, "docsUrl": "https://plaid.com/docs/identity-verification/", "llmsTxt": "https://plaid.com/llms.txt", "openapi": "https://raw.githubusercontent.com/plaid/plaid-openapi/master/2020-09-14.yml", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening" ], "tags": [ "hosted", "api-key", "openapi", "llms-txt", "webhooks", "sandbox", "status-page", "python", "typescript", "go", "java", "ruby", "bug-bounty" ], "lastRelease": "2026-10-13", "graded": true, "anchor": { "graded": true, "score": 67.1, "grade": "B", "agentReady": false, "rank": 278, "ranked": true, "rankOf": 1076, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 83, "payments": 15, "reliability": 68, "schema": 91, "security": 61, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Plaid Identity Verification has four typed endpoints in Plaid's public OpenAPI file, an idempotent create, a backend-only flow for data source checks and frequent changelog entries. Prices appear only after applying for Production, the secret has no scopes, and the rate-limit and error pages are disallowed to crawlers.", "bestFor": "US, Canadian and UK companies that want KYC with data source checks, documents and selfies, especially those already on Plaid or wanting Monitor screening in the same flow.", "strengths": [ "Four typed endpoints in the public OpenAPI file, with llms.txt and Markdown docs", "Backend-only flow runs data source checks from user data with no Link session", "`is_idempotent` on create returns the existing session instead of making a second", "Six dated Identity Verification changelog entries between 9 July and 13 October 2026", "Self-serve Sandbox since 12 August 2026, with sample identities for test outcomes" ], "weaknesses": [ "No public prices. Rates appear only after a Production application", "One team secret reaches every Plaid product, with no scopes or read-only key", "Integrating companies must be based in the US, Canada or the UK", "Data stays only while the contract is active, and access to past sessions ends with it", "Rate-limit and error pages sit under a path robots.txt disallows, so we didn't read them" ], "agentNotes": [ "Pass `is_idempotent: true` to /identity_verification/create so a retry returns the existing session", "Use the backend-only flow (data source template, `gave_consent: true`) when you already hold the user's details. Documents and selfies need the person in Link", "Wait for the STATUS_UPDATED webhook or poll /identity_verification/get. Link's onSuccess doesn't mean the user passed", "Don't issue retries casually. Each retry is a new session billed again", "Enable Sandbox for Identity Verification on the Dashboard Products page before the first call" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.1 } ], "editorialScores": { "ergonomics": 75, "maintenance": 83, "payments": 15, "reliability": 68, "schema": 91, "security": 61, "transparency": 57 }, "provenanceScore": 97 }, "connect": { "http": "curl -X POST https://sandbox.plaid.com/identity_verification/create \\\n-H 'Content-Type: application/json' \\\n-d '{\n \"client_user_id\": \"user-sandbox-b0e2c4ee-a763-4df5-bfe9-46a46bce993d\",\n \"client_id\": \"${PLAID_CLIENT_ID}\",\n \"secret\": \"${PLAID_SECRET}\",\n \"is_shareable\": true,\n \"template_id\": \"idvtmp_52xR9LKo77r1Np\",\n \"gave_consent\": true\n}'" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/plaid-identity-verification" }, "sameCompany": [ "plaid" ], "area": "domain-data", "provenance": { "legalEntity": "Plaid Inc.", "domain": "plaid.com", "domainRegistered": "1995-08-16", "endpointOnVendorDomain": true, "terms": "https://plaid.com/legal/#developer-policy", "privacy": "https://plaid.com/legal/#privacy-statement", "statusPage": "https://status.plaid.com", "changelog": "https://plaid.com/docs/changelog/", "securityTxt": "valid", "checked": "2026-10-14", "notes": [ "Same entity, legal pages and status page as the plaid listing. Plaid Financial Ltd and Plaid, B.V. cover the UK and the EEA.", "plaid.com/.well-known/security.txt lists HackerOne and security@plaid.com and expires 2026-12-31.", "plaid.com was registered in 1995, before Plaid was founded." ], "score": 97 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/plaid-identity-verification.json", "live": { "slug": "plaid-identity-verification", "vendorStatus": { "page": "https://status.plaid.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:53:20.159743826Z" }, "updatedAt": "2026-10-14T09:53:20.159743826Z" } }, "answer": "Plaid Identity Verification scores 67.1 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 5 of 7 scored categories. Socure RiskOS leads on reliability and payments \u0026 pricing.", "b": { "slug": "socure-riskos", "name": "Socure RiskOS", "vendor": "Socure Inc.", "vendorUrl": "https://www.socure.com", "kind": "http-api", "category": "identity-verification", "summary": "Socure RiskOS is an identity verification and risk decisioning platform from Socure Inc. Its Evaluation API runs configured workflows for KYC, document and selfie checks, fraud scoring and watchlist screening, and returns a decision with reason codes.", "url": "https://www.anchorterminal.com/tools/socure-riskos", "markdownUrl": "https://www.anchorterminal.com/tools/socure-riskos.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/socure-riskos.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/socure-riskos.json", "repo": "https://github.com/socure-inc/.github", "license": "Proprietary service. No service agreement is published, and the OpenAPI file states its licence as Proprietary", "transports": [ "http" ], "remoteUrl": "https://mcp.riskos.socure.com/sandbox", "packages": [ { "registry": "npm", "name": "@socure-inc/device-risk-sdk" } ], "auth": "api-key", "authNotes": "Self-serve API key for the sandbox, sent as `Authorization: Bearer \u003ckey\u003e`. A person signs up in a browser for a Socure Launch sandbox account and copies the key from the Developer Workbench. Sandbox and production use separate keys and hosts. Production starts at 0 requests a second and needs Socure Support to activate it, and Enterprise accounts go through sandbox certification with Socure staff. Each key reaches every workflow, with no scopes. Regenerating a key keeps the old one working until it is deleted, and an additional key is requested from Support. The MCP server takes its own MCP Server Key. IP allowlisting, mutual TLS and payload encryption are optional (checked 2026-10-08).", "pricing": "usage", "pricingNotes": "Socure Launch charges per evaluation started in production, at $0.80 for document verification, $0.90 with watchlist screening, $1.00 for KYC, fraud and watchlist with a document step-up, and $1.30 with prefill. Launch accounts receive $1,000 in production credits each month. The sandbox is free, so an agent can build and test without a contract, but it returns predefined results. Evaluations an end user abandons are still charged. Socure Enterprise is priced through sales. Whether sign-up or the move to production asks for a card was not established (checked 2026-10-08).", "priceSummary": "$0.80 / tx", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, the OpenAPI file, the MCP server page or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": null, "npmWeekly": 35395, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://help.socure.com/riskos/docs", "llmsTxt": "https://help.socure.com/riskos/llms.txt", "openapi": "https://raw.githubusercontent.com/socure-inc/.github/main/openapi-spec/riskos-api-spec.json", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening", "kyc.business", "kyc.cases" ], "tags": [ "hosted", "usage", "sandbox", "api-key", "mcp", "openapi", "llms-txt", "webhooks", "status-page", "soc2", "iso27001", "fedramp" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 63.5, "grade": "B", "agentReady": false, "rank": 417, "ranked": true, "rankOf": 1076, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 46, "maintenance": 75, "payments": 35, "reliability": 75, "schema": 84, "security": 60, "transparency": 68 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A public OpenAPI file, llms.txt, 15 documented error codes and dated release notes cover a ten-operation REST API, and Socure Launch publishes prices from $0.80 an evaluation with a free sandbox. API keys carry no scopes, no idempotency header is defined, no service terms are published, and production stays at zero requests until Socure activates it.", "bestFor": "A company in the United States that wants one decision from combined KYC, document, fraud and watchlist checks through a single evaluation call.", "strengths": [ "OpenAPI 3.0.3 file for ten operations and a 3.1 webhook file in a public GitHub repository, last synced 5 October 2026", "llms.txt indexes for every docs section and a Markdown copy of each page, with a robots.txt signal that allows AI input", "Socure Launch publishes four solutions at $0.80 to $1.30 per evaluation, with a free sandbox and $1,000 of monthly production credits", "Errors return one of 15 machine-readable codes with field-level `invalid_args`, and 429 responses carry `X-Retry-After`", "Release notes show entries on 5 and 6 October 2026 and more than 20 dated entries since 10 July" ], "weaknesses": [ "No service agreement or API terms are published. The only terms pages are website terms of use and end-user terms for document capture", "Each API key reaches every workflow, with no scopes or read-only keys, and an additional key has to be requested from Support", "The rate limit page advises idempotency keys, but neither the docs nor the OpenAPI file define an idempotency header", "No endpoint lists or searches evaluations. A caller needs the `eval_id` from the original response or a webhook", "Enrichment request and response schemas, reason codes and signal definitions sit in the dashboard, not in the public docs", "Production starts at 0 requests a second until Socure approves it, and Launch accounts are capped at 1 evaluation a second and 500 a day" ], "agentNotes": [ "Send `Authorization: Bearer \u003ckey\u003e` to `https://riskos.sandbox.socure.com/api/evaluation` for tests and `https://riskos.socure.com/api/evaluation` for live checks. The two environments use separate keys.", "Use dummy data only in the sandbox. It returns predefined results, connects to no live data source and expects the documented test values.", "Store the `eval_id` from every `POST /api/evaluation` response. No list or search endpoint exists to find it later.", "On 429 wait the seconds given in `X-Retry-After`. Do not blindly resend a failed `POST /api/evaluation`, because no idempotency header is documented and Launch bills each initiated evaluation.", "The MCP server at `https://mcp.riskos.socure.com/sandbox` reads docs, workflows and webhooks with its own MCP Server Key. It cannot run evaluations or read results." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.5 } ], "editorialScores": { "ergonomics": 46, "maintenance": 75, "payments": 35, "reliability": 75, "schema": 84, "security": 60, "transparency": 53 }, "provenanceScore": 82 }, "connect": { "http": "curl --request POST \\\n --url \"https://riskos.sandbox.socure.com/api/evaluation\" \\\n --header \"Authorization: Bearer YOUR_API_KEY\" \\\n --header \"Content-Type: application/json\" \\\n --header \"Accept: application/json\" \\\n --data '{\"id\":\"customer-onb-12345\",\"timestamp\":\"2024-12-01T08:15:30.456Z\",\"workflow\":\"consumer_onboarding\",\"data\":{\"individual\":{\"given_name\":\"Jane\",\"family_name\":\"Doe\",\"email\":\"jane.doe@example.com\",\"phone_number\":\"+1-555-123-4567\",\"address\":{\"line_1\":\"123 Main St\",\"locality\":\"San Francisco\",\"major_admin_division\":\"CA\",\"postal_code\":\"94105\",\"country\":\"US\"}}}}'", "claudeCode": "claude mcp add --transport http socure-dev-assist https://mcp.riskos.socure.com/sandbox --header \"Authorization: Bearer $RISKOS_MCP_KEY\"", "config": { "mcpServers": { "socure-dev-assist": { "args": [ "-y", "mcp-remote", "https://mcp.riskos.socure.com/sandbox", "--header", "Authorization: Bearer YOUR_MCP_SERVER_KEY" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/socure-riskos" }, "area": "domain-data", "unitPrices": [ { "item": "Socure Launch, Document Verification (DocV)", "unit": "tx", "usd": 0.8, "note": "Per evaluation started in production, after $1,000 of monthly credits" }, { "item": "Socure Launch, DocV + Watchlist", "unit": "tx", "usd": 0.9, "note": "Per evaluation started in production" }, { "item": "Socure Launch, KYC + Fraud + Watchlist with DocV step-up", "unit": "tx", "usd": 1, "note": "Per evaluation started in production" }, { "item": "Socure Launch, Prefill, KYC + Fraud + Watchlist with DocV step-up", "unit": "tx", "usd": 1.3, "note": "Per evaluation started in production" } ], "provenance": { "legalEntity": "Socure Inc.", "domain": "socure.com", "domainRegistered": "2003-06-20", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://www.socure.com/privacy-en", "statusPage": "https://status.socure.com", "changelog": "https://help.socure.com/riskos/page/release-notes", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The Global Services Privacy Notice (effective 1 October 2026) names Socure Inc. and covers the verification services. A separate Website Privacy Notice covers the marketing site.", "No service agreement or API terms are published. www.socure.com/terms-of-service is the Website Terms of Use, and the policies page lists only privacy notices, the DocV Terms of Use for end users and a text messaging notice, so the terms field is left out.", "The API answers at riskos.socure.com and riskos.sandbox.socure.com, and the MCP server at mcp.riskos.socure.com, all socure.com subdomains.", "www.socure.com/.well-known/security.txt gives security@socure.com and an `Expires` value of 15 July 2026, which has passed.", "RDAP for socure.com gives a registration date of 2003-06-20." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/socure-riskos.json", "live": { "slug": "socure-riskos", "probe": { "target": "https://mcp.riskos.socure.com/sandbox", "method": "get", "lastAt": "2026-10-14T10:00:05.794388559Z", "lastOk": true, "lastStatus": 403, "lastMs": 336, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 336, "p95ms24h": 369, "samples24h": 248, "samples30d": 1261, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 103, "ok": 103 } ] }, "vendorStatus": { "page": "https://status.socure.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:53:34.201384538Z" }, "versions": [ { "registry": "npm", "name": "@socure-inc/device-risk-sdk", "version": "2.11.0", "seenAt": "2026-10-13T23:25:20.672205661Z" } ], "githubStars": 0, "npmWeekly": 31350, "securityTxt": { "url": "https://socure.com/.well-known/security.txt", "state": "expired", "expires": "2026-07-15T00:00:00.000Z", "checkedAt": "2026-10-13T15:46:04.015689318Z" }, "llmsTxt": { "url": "https://help.socure.com/riskos/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-13T14:12:35.762942045Z" }, "domain": { "domain": "socure.com", "registered": "2003-06-20", "source": "https://rdap.verisign.com/com/v1/domain/socure.com", "checkedAt": "2026-10-11T13:26:58.40959229Z" }, "pages": [ { "url": "https://help.socure.com/riskos/page/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-10-13T20:17:38.534141883Z", "changedAt": "2026-10-13T20:17:38.534141883Z", "fingerprint": "42cb3f70014b" }, { "url": "https://www.socure.com/privacy-en", "kind": "privacy", "status": 304, "checkedAt": "2026-10-13T20:32:21.849748463Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "5567f47f0ada" } ], "updatedAt": "2026-10-14T10:00:05.794388559Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Plaid Inc.", "b": "Socure Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://mcp.riskos.socure.com/sandbox", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Plaid's developer policy and end-user terms. The OpenAPI file and client libraries are MIT", "b": "Proprietary service. No service agreement is published, and the OpenAPI file states its licence as Proprietary", "name": "Licence" }, { "a": "none", "b": "9", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-13", "b": "2026-10-06", "name": "Last release" }, { "a": "2025-12-01", "b": "no document linked", "name": "Terms last updated" }, { "a": "2025-12-01", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "1.2M npm/wk, 656k PyPI/wk", "b": "35k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Plaid Identity Verification scores 67.1 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 5 of 7 scored categories. Socure RiskOS leads on reliability and payments \u0026 pricing.", "question": "Which is better for AI agents, Plaid Identity Verification or Socure RiskOS?" }, { "answer": "Both need an API key.", "question": "Do Plaid Identity Verification and Socure RiskOS need an API key?" }, { "answer": "No hosted endpoint is listed for Plaid Identity Verification. Socure RiskOS has a hosted endpoint at https://mcp.riskos.socure.com/sandbox.", "question": "Can an agent call Plaid Identity Verification and Socure RiskOS without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 91 against 84", "Agent ergonomics, 75 against 46", "Maintenance \u0026 community, 83 against 75", "Transparency \u0026 trust, 77 against 68" ], "also": null, "goodFor": "US, Canadian and UK companies that want KYC with data source checks, documents and selfies, especially those already on Plaid or wanting Monitor screening in the same flow.", "slug": "plaid-identity-verification", "watchFor": "No public prices. Rates appear only after a Production application" }, { "aheadOn": [ "Reliability, 75 against 68", "Payments \u0026 pricing, 35 against 15" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "A company in the United States that wants one decision from combined KYC, document, fraud and watchlist checks through a single evaluation call.", "slug": "socure-riskos", "watchFor": "No service agreement or API terms are published. The only terms pages are website terms of use and end-user terms for document capture" } ], "job": { "capability": "kyc.identity", "name": "Identity verification" }, "others": [ { "json": "https://www.anchorterminal.com/compare/alloy-vs-plaid-identity-verification.json", "title": "Alloy vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/alloy-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-socure-riskos.json", "title": "Alloy vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/alloy-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification.json", "title": "ComplyCube vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-socure-riskos.json", "title": "ComplyCube vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/complycube-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-plaid-identity-verification.json", "title": "Didit vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/didit-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-socure-riskos.json", "title": "Didit vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/didit-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification.json", "title": "Entrust Identity Verification (formerly Onfido) vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-socure-riskos.json", "title": "Entrust Identity Verification (formerly Onfido) vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-plaid-identity-verification.json", "title": "Jumio vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/jumio-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.json", "title": "Jumio vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/jumio-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/middesk-vs-plaid-identity-verification.json", "title": "Middesk vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/middesk-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/persona-vs-plaid-identity-verification.json", "title": "Persona vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/persona-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/persona-vs-socure-riskos.json", "title": "Persona vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/persona-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-shufti.json", "title": "Plaid Identity Verification vs Shufti", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-shufti" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-stripe-identity.json", "title": "Plaid Identity Verification vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-stripe-identity" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-sumsub.json", "title": "Plaid Identity Verification vs Sumsub", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-trulioo.json", "title": "Plaid Identity Verification vs Trulioo", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-trulioo" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-veriff.json", "title": "Plaid Identity Verification vs Veriff", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-vouched.json", "title": "Plaid Identity Verification vs Vouched", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-vouched" }, { "json": "https://www.anchorterminal.com/compare/shufti-vs-socure-riskos.json", "title": "Shufti vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/shufti-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-stripe-identity.json", "title": "Socure RiskOS vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/socure-riskos-vs-stripe-identity" }, { "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub.json", "title": "Socure RiskOS vs Sumsub", "url": "https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-trulioo.json", "title": "Socure RiskOS vs Trulioo", "url": "https://www.anchorterminal.com/compare/socure-riskos-vs-trulioo" }, { "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-veriff.json", "title": "Socure RiskOS vs Veriff", "url": "https://www.anchorterminal.com/compare/socure-riskos-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-vouched.json", "title": "Socure RiskOS vs Vouched", "url": "https://www.anchorterminal.com/compare/socure-riskos-vs-vouched" }, { "json": "https://www.anchorterminal.com/compare/complyadvantage-vs-plaid-identity-verification.json", "title": "ComplyAdvantage vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/complyadvantage-vs-socure-riskos.json", "title": "ComplyAdvantage vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/middesk-vs-socure-riskos.json", "title": "Middesk vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/middesk-vs-socure-riskos" } ], "scores": [ { "by": 7, "edge": "socure-riskos", "key": "reliability", "name": "Reliability", "plaid-identity-verification": 68, "socure-riskos": 75, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 7, "edge": "plaid-identity-verification", "key": "schema", "name": "Schema \u0026 documentation", "plaid-identity-verification": 91, "socure-riskos": 84, "weight": 13 }, { "by": 29, "edge": "plaid-identity-verification", "key": "ergonomics", "name": "Agent ergonomics", "plaid-identity-verification": 75, "socure-riskos": 46, "weight": 13 }, { "by": 1, "edge": "plaid-identity-verification", "key": "security", "name": "Security \u0026 auth", "plaid-identity-verification": 61, "socure-riskos": 60, "weight": 14 }, { "by": 20, "edge": "socure-riskos", "key": "payments", "name": "Payments \u0026 pricing", "plaid-identity-verification": 15, "socure-riskos": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 8, "edge": "plaid-identity-verification", "key": "maintenance", "name": "Maintenance \u0026 community", "plaid-identity-verification": 83, "socure-riskos": 75, "weight": 7 }, { "by": 9, "edge": "plaid-identity-verification", "key": "transparency", "name": "Transparency \u0026 trust", "plaid-identity-verification": 77, "socure-riskos": 68, "weight": 7 } ], "summary": "Plaid Identity Verification scores 67.1 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 5 of 7 scored categories. Socure RiskOS leads on reliability and payments \u0026 pricing. Both do identity verification.", "verdicts": { "plaid-identity-verification": "Plaid Identity Verification has four typed endpoints in Plaid's public OpenAPI file, an idempotent create, a backend-only flow for data source checks and frequent changelog entries. Prices appear only after applying for Production, the secret has no scopes, and the rate-limit and error pages are disallowed to crawlers.", "socure-riskos": "A public OpenAPI file, llms.txt, 15 documented error codes and dated release notes cover a ten-operation REST API, and Socure Launch publishes prices from $0.80 an evaluation with a free sandbox. API keys carry no scopes, no idempotency header is defined, no service terms are published, and production stays at zero requests until Socure activates it." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos", "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos.md", "slim": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos.min.md" }, "markdown": "Plaid Identity Verification scores 67.1 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 5 of 7 scored categories. Socure RiskOS leads on reliability and payments \u0026 pricing. Both do identity verification.\n\n- Plaid Identity Verification: grade B, 67.1/100, rank #278 of 1076. Markdown https://www.anchorterminal.com/tools/plaid-identity-verification.md · JSON https://www.anchorterminal.com/api/v1/tools/plaid-identity-verification.json\n- Socure RiskOS: grade B, 63.5/100, rank #417 of 1076. Markdown https://www.anchorterminal.com/tools/socure-riskos.md · JSON https://www.anchorterminal.com/api/v1/tools/socure-riskos.json\n- Best identity and business verification APIs for AI agents: https://www.anchorterminal.com/best/identity-verification/index.md\n- All 119 verification comparisons: https://www.anchorterminal.com/compare/identity-verification/index.md\n\n## Which one, for what\n\n### Plaid Identity Verification (B)\n\nGood for: US, Canadian and UK companies that want KYC with data source checks, documents and selfies, especially those already on Plaid or wanting Monitor screening in the same flow.\n\nAhead on:\n- Schema \u0026 documentation, 91 against 84\n- Agent ergonomics, 75 against 46\n- Maintenance \u0026 community, 83 against 75\n- Transparency \u0026 trust, 77 against 68\n\nWatch for: No public prices. Rates appear only after a Production application\n\n### Socure RiskOS (B)\n\nGood for: A company in the United States that wants one decision from combined KYC, document, fraud and watchlist checks through a single evaluation call.\n\nAhead on:\n- Reliability, 75 against 68\n- Payments \u0026 pricing, 35 against 15\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No service agreement or API terms are published. The only terms pages are website terms of use and end-user terms for document capture\n\n\n## Score by category\n\n| Category | Weight | Plaid Identity Verification | Socure RiskOS | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 68 | 75 | Socure RiskOS +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 91 | 84 | Plaid Identity Verification +7 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 46 | Plaid Identity Verification +29 |\n| Security \u0026 auth | 14% (17.5 this run) | 61 | 60 | Plaid Identity Verification +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 35 | Socure RiskOS +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 75 | Plaid Identity Verification +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 68 | Plaid Identity Verification +9 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **67.1 · B** | **63.5 · B** | |\n\n## Facts side by side\n\n| Fact | Plaid Identity Verification | Socure RiskOS |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Plaid Inc. | Socure Inc. |\n| Hosted endpoint | no (local only) | `https://mcp.riskos.socure.com/sandbox` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Paid | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under Plaid's developer policy and end-user terms. The OpenAPI file and client libraries are MIT | Proprietary service. No service agreement is published, and the OpenAPI file states its licence as Proprietary |\n| Tools exposed | none | 9 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-13 | 2026-10-06 |\n| Terms last updated | 2025-12-01 | no document linked |\n| Privacy policy last updated | 2025-12-01 | no date given |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | 1.2M npm/wk, 656k PyPI/wk | 35k npm/wk |\n\n## Verdicts\n\n**Plaid Identity Verification.** Plaid Identity Verification has four typed endpoints in Plaid's public OpenAPI file, an idempotent create, a backend-only flow for data source checks and frequent changelog entries. Prices appear only after applying for Production, the secret has no scopes, and the rate-limit and error pages are disallowed to crawlers.\n\n**Socure RiskOS.** A public OpenAPI file, llms.txt, 15 documented error codes and dated release notes cover a ten-operation REST API, and Socure Launch publishes prices from $0.80 an evaluation with a free sandbox. API keys carry no scopes, no idempotency header is defined, no service terms are published, and production stays at zero requests until Socure activates it.\n\n## Before you call either\n\n### Plaid Identity Verification\n\n1. Pass `is_idempotent: true` to /identity_verification/create so a retry returns the existing session\n2. Use the backend-only flow (data source template, `gave_consent: true`) when you already hold the user's details. Documents and selfies need the person in Link\n3. Wait for the STATUS_UPDATED webhook or poll /identity_verification/get. Link's onSuccess doesn't mean the user passed\n4. Don't issue retries casually. Each retry is a new session billed again\n5. Enable Sandbox for Identity Verification on the Dashboard Products page before the first call\n\n### Socure RiskOS\n\n1. Send `Authorization: Bearer \u003ckey\u003e` to `https://riskos.sandbox.socure.com/api/evaluation` for tests and `https://riskos.socure.com/api/evaluation` for live checks. The two environments use separate keys.\n2. Use dummy data only in the sandbox. It returns predefined results, connects to no live data source and expects the documented test values.\n3. Store the `eval_id` from every `POST /api/evaluation` response. No list or search endpoint exists to find it later.\n4. On 429 wait the seconds given in `X-Retry-After`. Do not blindly resend a failed `POST /api/evaluation`, because no idempotency header is documented and Launch bills each initiated evaluation.\n5. The MCP server at `https://mcp.riskos.socure.com/sandbox` reads docs, workflows and webhooks with its own MCP Server Key. It cannot run evaluations or read results.\n\n## Questions\n\n### Which is better for AI agents, Plaid Identity Verification or Socure RiskOS?\n\nPlaid Identity Verification scores 67.1 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 5 of 7 scored categories. Socure RiskOS leads on reliability and payments \u0026 pricing.\n\n### Do Plaid Identity Verification and Socure RiskOS need an API key?\n\nBoth need an API key.\n\n### Can an agent call Plaid Identity Verification and Socure RiskOS without installing anything?\n\nNo hosted endpoint is listed for Plaid Identity Verification. Socure RiskOS has a hosted endpoint at https://mcp.riskos.socure.com/sandbox.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos.json, and with the fewest tokens: https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"plaid-identity-verification\", \"b\": \"socure-riskos\"}`. From a terminal: `anchor compare plaid-identity-verification socure-riskos`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/plaid-identity-verification.json and https://www.anchorterminal.com/api/v1/tools/socure-riskos.json\n\n## Other comparisons with Plaid Identity Verification or Socure RiskOS\n\n- [Alloy vs Plaid Identity Verification](https://www.anchorterminal.com/compare/alloy-vs-plaid-identity-verification.md)\n- [Alloy vs Socure RiskOS](https://www.anchorterminal.com/compare/alloy-vs-socure-riskos.md)\n- [ComplyCube vs Plaid Identity Verification](https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification.md)\n- [ComplyCube vs Socure RiskOS](https://www.anchorterminal.com/compare/complycube-vs-socure-riskos.md)\n- [Didit vs Plaid Identity Verification](https://www.anchorterminal.com/compare/didit-vs-plaid-identity-verification.md)\n- [Didit vs Socure RiskOS](https://www.anchorterminal.com/compare/didit-vs-socure-riskos.md)\n- [Entrust Identity Verification (formerly Onfido) vs Plaid Identity Verification](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification.md)\n- [Entrust Identity Verification (formerly Onfido) vs Socure RiskOS](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-socure-riskos.md)\n- [Jumio vs Plaid Identity Verification](https://www.anchorterminal.com/compare/jumio-vs-plaid-identity-verification.md)\n- [Jumio vs Socure RiskOS](https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.md)\n- [Middesk vs Plaid Identity Verification](https://www.anchorterminal.com/compare/middesk-vs-plaid-identity-verification.md)\n- [Persona vs Plaid Identity Verification](https://www.anchorterminal.com/compare/persona-vs-plaid-identity-verification.md)\n- [Persona vs Socure RiskOS](https://www.anchorterminal.com/compare/persona-vs-socure-riskos.md)\n- [Plaid Identity Verification vs Shufti](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-shufti.md)\n- [Plaid Identity Verification vs Stripe Identity](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-stripe-identity.md)\n- [Plaid Identity Verification vs Sumsub](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-sumsub.md)\n- [Plaid Identity Verification vs Trulioo](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-trulioo.md)\n- [Plaid Identity Verification vs Veriff](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-veriff.md)\n- [Plaid Identity Verification vs Vouched](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-vouched.md)\n- [Shufti vs Socure RiskOS](https://www.anchorterminal.com/compare/shufti-vs-socure-riskos.md)\n- [Socure RiskOS vs Stripe Identity](https://www.anchorterminal.com/compare/socure-riskos-vs-stripe-identity.md)\n- [Socure RiskOS vs Sumsub](https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub.md)\n- [Socure RiskOS vs Trulioo](https://www.anchorterminal.com/compare/socure-riskos-vs-trulioo.md)\n- [Socure RiskOS vs Veriff](https://www.anchorterminal.com/compare/socure-riskos-vs-veriff.md)\n- [Socure RiskOS vs Vouched](https://www.anchorterminal.com/compare/socure-riskos-vs-vouched.md)\n- [ComplyAdvantage vs Plaid Identity Verification](https://www.anchorterminal.com/compare/complyadvantage-vs-plaid-identity-verification.md)\n- [ComplyAdvantage vs Socure RiskOS](https://www.anchorterminal.com/compare/complyadvantage-vs-socure-riskos.md)\n- [Middesk vs Socure RiskOS](https://www.anchorterminal.com/compare/middesk-vs-socure-riskos.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-14", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Plaid Identity Verification vs Socure RiskOS", "url": "" } ], "description": "Plaid Identity Verification scores 67.1 (B) to Socure RiskOS's 63.5 (B) for identity verification. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Plaid Identity Verification B 67.1", "Socure RiskOS B 63.5", "scores" ], "h1": "Plaid Identity Verification vs Socure RiskOS", "image": "https://www.anchorterminal.com/assets/og/compare-plaid-identity-verification-vs-socure-riskos.png", "path": "/compare/plaid-identity-verification-vs-socure-riskos", "published": "2026-10-01", "section": "tools", "title": "Plaid Identity Verification vs Socure RiskOS for AI agents (2026)", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos" }, "tokens": { "markdown": 2900, "slim": 780 }, "version": 1 }