{ "data": { "a": { "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": 357, "ranked": true, "rankOf": 842, "categoryRank": 5, "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-09T11:46:41.308485021Z", "lastOk": true, "lastStatus": 403, "lastMs": 340, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 337, "p95ms24h": 397, "samples24h": 44, "samples30d": 44, "days": [ { "date": "2026-10-09", "probes": 44, "ok": 44 } ] }, "vendorStatus": { "page": "https://status.socure.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T11:40:55.521859922Z" }, "updatedAt": "2026-10-09T11:46:41.308485021Z" } }, "answer": "Socure RiskOS scores 63.5 (B) on agent readiness against Veriff's 61.1 (C), and leads in 5 of 7 scored categories. Veriff leads on payments \u0026 pricing.", "b": { "slug": "veriff", "name": "Veriff", "vendor": "Veriff OÜ", "vendorUrl": "https://www.veriff.com", "kind": "http-api", "category": "identity-verification", "summary": "Identity verification service from Veriff in Tallinn. It checks an identity document and a selfie, with liveness, database checks and PEP and sanctions screening. Sessions are created and read through the Public API v1, with results sent by webhook.", "url": "https://www.anchorterminal.com/tools/veriff", "markdownUrl": "https://www.anchorterminal.com/tools/veriff.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/veriff.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/veriff.json", "repo": "https://github.com/Veriff/veriff-js-sdk", "license": "Proprietary service. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk)", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@veriff/incontext-sdk" }, { "registry": "npm", "name": "@veriff/js-sdk" }, { "registry": "npm", "name": "@veriff/react-native-sdk" } ], "auth": "api-key", "authNotes": "Self-serve. Signing up for a Self-Serve plan creates a Customer Portal account with a test integration, and Enterprise accounts start from a sales form. Each integration has an API key, sent as `X-AUTH-CLIENT`, and up to five shared secret keys used to compute an HMAC-SHA256 `X-HMAC-SIGNATURE` (over the body on POST and PATCH, over the session ID on GET and DELETE). POST /v1/sessions needs only the API key. Secrets are shown once and can be rotated or deleted by an admin. There are no scopes. A live integration unlocks once the account holder passes Veriff's own identity verification.", "pricing": "usage", "pricingNotes": "Self-Serve is priced per verification with a monthly minimum. Essential is $0.80 ($49 a month minimum), Plus $1.39 ($99) and Premium $1.89 ($209). PEP and sanctions screening adds $0.64, ongoing monitoring $0.09 and two-year retention $0.30. A 15-day trial covers up to 50 sessions with no card, after the account holder completes identity verification. Test integrations are free and unbilled. Enterprise, suggested for 5,000 or more verifications a month, is priced by sales (https://www.veriff.com/plans/self-serve, checked 2026-10-08).", "priceSummary": "$0.80 / tx", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs index, the API guides or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 32, "npmWeekly": 109625, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://devdocs.veriff.com", "llmsTxt": "https://devdocs.veriff.com/llms.txt", "openapi": "https://devdocs.veriff.com/apidocs/v1sessions.md", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening" ], "tags": [ "hosted", "api-key", "hmac", "webhooks", "openapi", "llms-txt", "free-trial", "sandbox", "status-page", "bug-bounty", "soc2", "iso27001" ], "lastRelease": "2026-10-02", "graded": true, "anchor": { "graded": true, "score": 61.1, "grade": "C", "agentReady": false, "rank": 436, "ranked": true, "rankOf": 842, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 43, "maintenance": 74, "payments": 40, "reliability": 62, "schema": 82, "security": 63, "transparency": 67 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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 the status page shows nine incidents between 20 July and 7 October 2026.", "bestFor": "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.", "strengths": [ "Public prices of $0.80, $1.39 and $1.89 a verification, with a 15-day trial of up to 50 sessions and no card", "llms.txt index and Markdown pages, each API endpoint with an OpenAPI 3.0.0 fragment, examples and error schemas", "Up to five shared secret keys per integration, shown once, with documented rotation and deletion", "Test integrations are created at signup, aren't billed, and let the developer force a decision", "ISO/IEC 27001:2022, SOC 2 Type II, Cyber Essentials and a bug bounty on Intigriti paying 50 to 6,000 euros" ], "weaknesses": [ "No server-side SDK and no MCP server. Official packages cover only browser and mobile capture", "No idempotency key on POST /v1/sessions, and no Retry-After or backoff guidance for the documented 429", "Nine status-page incidents between 20 July and 7 October 2026, mostly delayed decisions in the US region", "No endpoint lists sessions and no pagination was found. Every read needs a stored session ID", "Session deletion by API is off by default and capped at 10 sessions in 24 hours", "No security.txt, and the sub-processor list sits on a help centre page that needs JavaScript" ], "agentNotes": [ "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", "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", "Stay under 30 session creations a minute on Self-Serve, 600 on Enterprise. A 429 carries code 1004", "Don't blindly retry POST /v1/sessions. Each call makes a new session, which is billed on a live integration", "Poll GET /v1/sessions/{id}/decision until `verification` is not null, or accept webhooks within 5 seconds and treat duplicates as normal" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.1 } ], "editorialScores": { "ergonomics": 43, "maintenance": 74, "payments": 40, "reliability": 62, "schema": 82, "security": 63, "transparency": 48 }, "provenanceScore": 85 }, "connect": { "http": "curl -X POST \"https://\u003cBaseURL\u003e/v1/sessions\" \\\n -H 'Content-Type: application/json' \\\n -H 'X-AUTH-CLIENT: API-KEY' \\\n -d '{\"verification\": {}}'" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/veriff" }, "area": "domain-data", "unitPrices": [ { "item": "Verification, Essential plan (automated decision)", "unit": "tx", "usd": 0.8, "note": "$49 a month minimum" }, { "item": "Verification, Plus plan", "unit": "tx", "usd": 1.39, "note": "$99 a month minimum" }, { "item": "Verification, Premium plan", "unit": "tx", "usd": 1.89, "note": "$209 a month minimum" }, { "item": "PEP and sanctions screening add-on, per verification", "unit": "tx", "usd": 0.64, "note": "charged on top of the monthly minimum" }, { "item": "Ongoing monitoring add-on, per verification", "unit": "tx", "usd": 0.09, "note": "charged on top of the monthly minimum" } ], "provenance": { "legalEntity": "Veriff OÜ", "domain": "veriff.com", "domainRegistered": "2006-04-12", "endpointOnVendorDomain": true, "terms": "https://www.veriff.com/terms-of-service", "privacy": "https://www.veriff.com/privacy-notice", "statusPage": "https://status.veriff.com", "changelog": "https://devdocs.veriff.com/docs/release-notes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The privacy notice (valid from 30 July 2020, last updated 16 April 2026) names Veriff OÜ and Veriff Brazil Ltda. and gives the Estonian Data Protection Inspectorate as lead supervisory authority.", "www.veriff.com/terms-of-service answers 200 with the title Terms of Service but no terms text in the HTML we fetched, so the terms themselves weren't read.", "www.veriff.com/.well-known/security.txt and /security.txt return 404. Reports go to a bug bounty programme on Intigriti (https://www.veriff.com/bug-bounty).", "The API base URL is per integration and shown in the Customer Portal. Code samples in the docs use https://stationapi.veriff.com.", "RDAP for veriff.com gives a registration date of 2006-04-12, which predates the company.", "The sub-processor list is linked from the privacy notice to help.veriff.com, which returned only a JavaScript shell to our fetch." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/veriff.json", "live": { "slug": "veriff", "vendorStatus": { "page": "https://status.veriff.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T11:41:13.411444533Z" }, "versions": [ { "registry": "github", "name": "Veriff/veriff-js-sdk", "version": "v2.0.0", "released": "2025-09-09", "seenAt": "2026-10-08T16:34:12.058479178Z" }, { "registry": "npm", "name": "@veriff/incontext-sdk", "version": "2.5.0", "seenAt": "2026-10-08T16:34:07.822049846Z" }, { "registry": "npm", "name": "@veriff/js-sdk", "version": "2.0.0", "seenAt": "2026-10-08T16:34:08.944903091Z" }, { "registry": "npm", "name": "@veriff/react-native-sdk", "version": "13.2.0", "seenAt": "2026-10-08T16:34:10.073325113Z" } ], "githubStars": 32, "npmWeekly": 109625, "securityTxt": { "url": "https://veriff.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:34.847122653Z" }, "pages": [ { "url": "https://devdocs.veriff.com/docs/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:17:01.404186048Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "26520a9df2cc" }, { "url": "https://www.veriff.com/privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:31:21.093035848Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "024c0d3f9713" }, { "url": "https://www.veriff.com/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:31:23.123829782Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d9e650601ce7" } ], "updatedAt": "2026-10-09T11:41:13.411444533Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Socure Inc.", "b": "Veriff OÜ", "name": "Vendor" }, { "a": "https://mcp.riskos.socure.com/sandbox", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service. No service agreement is published, and the OpenAPI file states its licence as Proprietary", "b": "Proprietary service. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk)", "name": "Licence" }, { "a": "9", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-06", "b": "2026-10-02", "name": "Last release" }, { "a": "no document linked", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-04-16", "name": "Privacy policy last updated" }, { "a": "yes", "b": "yes", "name": "Customer content may train models" }, { "a": "", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "35k npm/wk", "b": "32 stars, 110k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Socure RiskOS scores 63.5 (B) on agent readiness against Veriff's 61.1 (C), and leads in 5 of 7 scored categories. Veriff leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Socure RiskOS or Veriff?" }, { "answer": "Both need an API key.", "question": "Do Socure RiskOS and Veriff need an API key?" }, { "answer": "Socure RiskOS has a hosted endpoint at https://mcp.riskos.socure.com/sandbox. No hosted endpoint is listed for Veriff.", "question": "Can an agent call Socure RiskOS and Veriff without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 62" ], "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" }, { "aheadOn": [ "Payments \u0026 pricing, 40 against 35" ], "also": null, "goodFor": "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.", "slug": "veriff", "watchFor": "No server-side SDK and no MCP server. Official packages cover only browser and mobile capture" } ], "job": { "capability": "kyc.identity", "name": "Kyc identity" }, "others": [ { "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/complycube-vs-veriff.json", "title": "ComplyCube vs Veriff", "url": "https://www.anchorterminal.com/compare/complycube-vs-veriff" }, { "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/didit-vs-veriff.json", "title": "Didit vs Veriff", "url": "https://www.anchorterminal.com/compare/didit-vs-veriff" }, { "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/jumio-vs-veriff.json", "title": "Jumio vs Veriff", "url": "https://www.anchorterminal.com/compare/jumio-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/middesk-vs-veriff.json", "title": "Middesk vs Veriff", "url": "https://www.anchorterminal.com/compare/middesk-vs-veriff" }, { "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/persona-vs-veriff.json", "title": "Persona vs Veriff", "url": "https://www.anchorterminal.com/compare/persona-vs-veriff" }, { "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/shufti-vs-veriff.json", "title": "Shufti vs Veriff", "url": "https://www.anchorterminal.com/compare/shufti-vs-veriff" }, { "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/sumsub-vs-veriff.json", "title": "Sumsub vs Veriff", "url": "https://www.anchorterminal.com/compare/sumsub-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/trulioo-vs-veriff.json", "title": "Trulioo vs Veriff", "url": "https://www.anchorterminal.com/compare/trulioo-vs-veriff" }, { "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/complyadvantage-vs-veriff.json", "title": "ComplyAdvantage vs Veriff", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-veriff" }, { "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": 13, "edge": "socure-riskos", "key": "reliability", "name": "Reliability", "socure-riskos": 75, "veriff": 62, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "edge": "socure-riskos", "key": "schema", "name": "Schema \u0026 documentation", "socure-riskos": 84, "veriff": 82, "weight": 13 }, { "by": 3, "edge": "socure-riskos", "key": "ergonomics", "name": "Agent ergonomics", "socure-riskos": 46, "veriff": 43, "weight": 13 }, { "by": 3, "edge": "veriff", "key": "security", "name": "Security \u0026 auth", "socure-riskos": 60, "veriff": 63, "weight": 14 }, { "by": 5, "edge": "veriff", "key": "payments", "name": "Payments \u0026 pricing", "socure-riskos": 35, "veriff": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 1, "edge": "socure-riskos", "key": "maintenance", "name": "Maintenance \u0026 community", "socure-riskos": 75, "veriff": 74, "weight": 7 }, { "by": 1, "edge": "socure-riskos", "key": "transparency", "name": "Transparency \u0026 trust", "socure-riskos": 68, "veriff": 67, "weight": 7 } ], "summary": "Socure RiskOS scores 63.5 (B) on agent readiness against Veriff's 61.1 (C), and leads in 5 of 7 scored categories. Veriff leads on payments \u0026 pricing. Both do kyc identity.", "verdicts": { "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.", "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 the status page shows nine incidents between 20 July and 7 October 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/socure-riskos-vs-veriff", "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-veriff.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/socure-riskos-vs-veriff.md", "slim": "https://www.anchorterminal.com/compare/socure-riskos-vs-veriff.min.md" }, "markdown": "Socure RiskOS scores 63.5 (B) on agent readiness against Veriff's 61.1 (C), and leads in 5 of 7 scored categories. Veriff leads on payments \u0026 pricing. Both do kyc identity.\n\n- Socure RiskOS: grade B, 63.5/100, rank #357 of 842. Markdown https://www.anchorterminal.com/tools/socure-riskos.md · JSON https://www.anchorterminal.com/api/v1/tools/socure-riskos.json\n- Veriff: grade C, 61.1/100, rank #436 of 842. Markdown https://www.anchorterminal.com/tools/veriff.md · JSON https://www.anchorterminal.com/api/v1/tools/veriff.json\n\n## Which one, for what\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 62\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### Veriff (C)\n\nGood 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.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 35\n\nWatch for: No server-side SDK and no MCP server. Official packages cover only browser and mobile capture\n\n\n## Score by category\n\n| Category | Weight | Socure RiskOS | Veriff | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 62 | Socure RiskOS +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 82 | Socure RiskOS +2 |\n| Agent ergonomics | 13% (16.2 this run) | 46 | 43 | Socure RiskOS +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 63 | Veriff +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 40 | Veriff +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 74 | Socure RiskOS +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 68 | 67 | Socure RiskOS +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.5 · B** | **61.1 · C** | |\n\n## Facts side by side\n\n| Fact | Socure RiskOS | Veriff |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Socure Inc. | Veriff OÜ |\n| Hosted endpoint | `https://mcp.riskos.socure.com/sandbox` | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service. No service agreement is published, and the OpenAPI file states its licence as Proprietary | Proprietary service. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk) |\n| Tools exposed | 9 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | 2026-10-02 |\n| Terms last updated | no document linked | couldn't be read |\n| Privacy policy last updated | no date given | 2026-04-16 |\n| Customer content may train models | yes | yes |\n| Terms restrict automated access | | couldn't be read |\n| Terms restrict benchmarking | | couldn't be read |\n| Terms or service can change without notice | | couldn't be read |\n| Arbitration or class-action waiver | | couldn't be read |\n| Popularity | 35k npm/wk | 32 stars, 110k npm/wk |\n\n## Verdicts\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**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 the status page shows nine incidents between 20 July and 7 October 2026.\n\n## Before you call either\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### Veriff\n\n1. 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\n2. 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\n3. Stay under 30 session creations a minute on Self-Serve, 600 on Enterprise. A 429 carries code 1004\n4. Don't blindly retry POST /v1/sessions. Each call makes a new session, which is billed on a live integration\n5. Poll GET /v1/sessions/{id}/decision until `verification` is not null, or accept webhooks within 5 seconds and treat duplicates as normal\n\n## Questions\n\n### Which is better for AI agents, Socure RiskOS or Veriff?\n\nSocure RiskOS scores 63.5 (B) on agent readiness against Veriff's 61.1 (C), and leads in 5 of 7 scored categories. Veriff leads on payments \u0026 pricing.\n\n### Do Socure RiskOS and Veriff need an API key?\n\nBoth need an API key.\n\n### Can an agent call Socure RiskOS and Veriff without installing anything?\n\nSocure RiskOS has a hosted endpoint at https://mcp.riskos.socure.com/sandbox. No hosted endpoint is listed for Veriff.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/socure-riskos-vs-veriff.json, and with the fewest tokens: https://www.anchorterminal.com/compare/socure-riskos-vs-veriff.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"socure-riskos\", \"b\": \"veriff\"}`. From a terminal: `anchor compare socure-riskos veriff`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/socure-riskos.json and https://www.anchorterminal.com/api/v1/tools/veriff.json\n\n## Other comparisons with Socure RiskOS or Veriff\n\n- [ComplyCube vs Socure RiskOS](https://www.anchorterminal.com/compare/complycube-vs-socure-riskos.md)\n- [ComplyCube vs Veriff](https://www.anchorterminal.com/compare/complycube-vs-veriff.md)\n- [Didit vs Socure RiskOS](https://www.anchorterminal.com/compare/didit-vs-socure-riskos.md)\n- [Didit vs Veriff](https://www.anchorterminal.com/compare/didit-vs-veriff.md)\n- [Jumio vs Socure RiskOS](https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.md)\n- [Jumio vs Veriff](https://www.anchorterminal.com/compare/jumio-vs-veriff.md)\n- [Middesk vs Veriff](https://www.anchorterminal.com/compare/middesk-vs-veriff.md)\n- [Persona vs Socure RiskOS](https://www.anchorterminal.com/compare/persona-vs-socure-riskos.md)\n- [Persona vs Veriff](https://www.anchorterminal.com/compare/persona-vs-veriff.md)\n- [Shufti vs Socure RiskOS](https://www.anchorterminal.com/compare/shufti-vs-socure-riskos.md)\n- [Shufti vs Veriff](https://www.anchorterminal.com/compare/shufti-vs-veriff.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- [Sumsub vs Veriff](https://www.anchorterminal.com/compare/sumsub-vs-veriff.md)\n- [Trulioo vs Veriff](https://www.anchorterminal.com/compare/trulioo-vs-veriff.md)\n- [ComplyAdvantage vs Socure RiskOS](https://www.anchorterminal.com/compare/complyadvantage-vs-socure-riskos.md)\n- [ComplyAdvantage vs Veriff](https://www.anchorterminal.com/compare/complyadvantage-vs-veriff.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-09", "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": "Socure RiskOS vs Veriff", "url": "" } ], "description": "Socure RiskOS scores 63.5 (B) on agent readiness against Veriff's 61.1 (C), and leads in 5 of 7 scored categories. Veriff leads on payments \u0026 pricing. Both do kyc identity. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Socure RiskOS B 63.5", "Veriff C 61.1", "scores" ], "h1": "Socure RiskOS vs Veriff", "image": "https://www.anchorterminal.com/assets/og/compare-socure-riskos-vs-veriff.png", "path": "/compare/socure-riskos-vs-veriff", "published": "2026-10-01", "section": "tools", "title": "Socure RiskOS vs Veriff for AI agents, B 63.5 vs C 61.1", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/socure-riskos-vs-veriff" }, "tokens": { "markdown": 2250, "slim": 630 }, "version": 1 }