{ "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": "Sumsub scores 68.5 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 4 of 7 scored categories. Socure RiskOS leads on schema \u0026 documentation and payments \u0026 pricing.", "b": { "slug": "sumsub", "name": "Sumsub", "vendor": "Sum and Substance Ltd", "vendorUrl": "https://sumsub.com", "kind": "http-api", "category": "identity-verification", "summary": "Sumsub verifies people from identity documents and a liveness check, verifies businesses against registries, and screens both against sanctions and watchlists. Agents reach it through a signed REST API and a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/sumsub", "markdownUrl": "https://www.anchorterminal.com/tools/sumsub.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sumsub.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sumsub.json", "repo": "https://github.com/sumsub/agent-skills", "license": "Proprietary service under Sumsub's terms and conditions. The agent skills repository and the @sumsub/websdk npm package are MIT", "transports": [ "http" ], "remoteUrl": "https://api.sumsub.com", "packages": [ { "registry": "npm", "name": "@sumsub/websdk" } ], "auth": "mixed", "authNotes": "The REST API takes an app token generated in the Dashboard by a signed-in team member. Each request carries `X-App-Token`, `X-App-Access-Ts` and `X-App-Access-Sig`, an HMAC-SHA256 signature made with the token's secret key over the timestamp, method, path and body. A token has its own permissions, an optional IP allowlist, an optional expiry date and optional source keys that limit it to a group of applicants, and it can be disabled or deleted but not edited. Sandbox and production tokens are separate. The MCP server at https://api.sumsub.com/mcp/ uses OAuth with PKCE and dynamic client registration, signs the user in with Sumsub, and needs the Use MCP server role permission. Production mode opens after Sumsub verifies the integration (https://docs.sumsub.com/reference/about-sumsub-api).", "pricing": "usage", "pricingNotes": "Basic is $1.35 per verification with a $149 monthly minimum, and Compliance is $1.85 with a $299 minimum and adds AML screening and address checks. Business verification, transaction monitoring and fraud prevention are on a custom plan through sales. Only completed checks are charged. Sandbox mode is free in any account, limited to 500 new applicants and 1,000 transactions per 24 hours. The 14-day trial of 50 real checks asks for bank card details (https://sumsub.com/pricing/, https://docs.sumsub.com/docs/self-service, checked 2026-10-08).", "priceSummary": "$1.35 / tx", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, the OpenAPI spec or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 172226, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.sumsub.com", "llmsTxt": "https://docs.sumsub.com/llms.txt", "openapi": "https://api.sumsub.com/openapi.json", "capabilities": [ "kyc.identity", "kyc.business", "kyc.documents", "kyc.screening", "kyc.cases" ], "tags": [ "hosted", "usage-based", "sandbox", "api-key", "oauth", "mcp", "openapi", "llms-txt", "webhooks", "status-page", "sla", "bug-bounty", "soc2", "iso27001" ], "lastRelease": "2026-10-03", "graded": true, "anchor": { "graded": true, "score": 68.5, "grade": "B", "agentReady": false, "rank": 200, "ranked": true, "rankOf": 842, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 74, "payments": 25, "reliability": 80, "schema": 78, "security": 80, "transparency": 74 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Per-token permissions, an IP allowlist, HMAC-signed requests and a public OpenAPI spec with Markdown docs suit an agent working on verification cases. No idempotency keys or Retry-After guidance were found, there is no server SDK, and production access needs a browser signup, a bank card and Sumsub's review of the integration.", "bestFor": "An agent that starts verifications, sends links, reads results and AML cases, and works case queues for a regulated business, with one token limited to those permissions.", "strengths": [ "App tokens carry per-token permissions, an optional IP allowlist and expiry date, and can be disabled with a recorded reason", "Requests are signed with HMAC-SHA256 over timestamp, method, path and body, so the secret key never travels", "Public OpenAPI 3.0.1 spec with 157 operations, llms.txt, and every docs page served as Markdown", "Hosted MCP server with OAuth, PKCE and dynamic client registration, gated by a Use MCP server role permission", "Terms publish a 99.5 per cent monthly uptime commitment, and the status page lists API, WebSDK and MobileSDK for three regions" ], "weaknesses": [ "No idempotency keys and no Retry-After or backoff guidance found in the reviewed documentation", "Only 24 of 157 operations in the OpenAPI spec carry a summary or description, and 154 declare only a default response", "No official server-side SDK. Sumsub publishes request-signing examples in seven languages instead", "The 14-day trial of 50 real checks needs a bank card, and production opens after Sumsub checks the integration", "Terms clause 6.9 permits Sumsub to use customers' personal data to develop fraud detection, including machine learning models", "The subprocessor list is published in the Dashboard, not on a public page" ], "agentNotes": [ "Sign every request. X-App-Access-Sig is the lowercase hex HMAC-SHA256 of timestamp, uppercase method, path with query and raw body, and the timestamp must be within one minute of server time", "Use a sandbox token (prefix sbx) for agent work. Sandbox and production tokens are separate, and Sumsub's own skills refuse any other prefix", "Stay under 300 GET and 50 POST requests per 5 seconds, and under 500 new applicants per 24 hours in Sandbox", "Token permissions can't be edited after creation. Generate a new token with the narrower set and delete the old one", "Subscribe to the applicantReviewed webhook for results and verify x-payload-digest against the raw body before trusting it" ], "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": 68.5 } ], "editorialScores": { "ergonomics": 60, "maintenance": 74, "payments": 25, "reliability": 80, "schema": 78, "security": 80, "transparency": 52 }, "provenanceScore": 96 }, "connect": { "install": "npx skills add sumsub/agent-skills --all -g", "http": "curl -X GET \\\n 'https://api.sumsub.com/resources/auditTrailEvents/list?from=2024-06-01+00:00:00\u0026to=2024-06-30+23:59:59\u0026limit=100' \\\n -H 'X-App-Token: \u003cyour-app-token\u003e' \\\n -H 'X-App-Access-Sig: \u003cyour-signature\u003e' \\\n -H 'X-App-Access-Ts: \u003cunix-timestamp\u003e'", "claudeCode": "claude mcp add --transport http sumsub https://api.sumsub.com/mcp/", "config": { "mcpServers": { "sumsub": { "args": [ "mcp-remote", "https://api.sumsub.com/mcp/" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/sumsub" }, "area": "domain-data", "unitPrices": [ { "item": "Basic plan, user verification", "unit": "tx", "usd": 1.35, "note": "per completed verification; $149 monthly minimum" }, { "item": "Compliance plan, user verification with AML screening and address check", "unit": "tx", "usd": 1.85, "note": "per completed verification; $299 monthly minimum" } ], "provenance": { "legalEntity": "Sum and Substance Ltd", "domain": "sumsub.com", "domainRegistered": "2015-05-01", "endpointOnVendorDomain": true, "terms": "https://sumsub.com/terms-and-conditions/", "privacy": "https://sumsub.com/privacy-notice-service/", "statusPage": "https://status.sumsub.com", "changelog": "https://docs.sumsub.com/changelog", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The terms (version of 21 May 2026) name Sum and Substance Ltd, England, company number 09688671, 30 St. Mary Axe, London EC3A 8BF, with contracting entities in the UAE, Delaware, Singapore and Cyprus depending on where the customer is registered.", "The API and the MCP server answer at api.sumsub.com, and the Dashboard and OAuth issuer at cockpit.sumsub.com.", "sumsub.com/.well-known/security.txt gives security@sumsub.com and a Bugcrowd engagement as contacts and expires on 2027-12-31.", "The service privacy notice was last updated on 19 March 2026. The data processing agreement is Annex 3 of the terms.", "RDAP for sumsub.com gives a registration date of 2015-05-01." ], "score": 96 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sumsub.json", "live": { "slug": "sumsub", "probe": { "target": "https://api.sumsub.com", "method": "get", "lastAt": "2026-10-09T11:46:41.99457637Z", "lastOk": true, "lastStatus": 200, "lastMs": 148, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 163, "p95ms24h": 260, "samples24h": 218, "samples30d": 218, "days": [ { "date": "2026-10-08", "probes": 93, "ok": 93 }, { "date": "2026-10-09", "probes": 125, "ok": 125 } ] }, "vendorStatus": { "page": "https://status.sumsub.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T11:40:59.008733831Z" }, "versions": [ { "registry": "npm", "name": "@sumsub/websdk", "version": "2.9.0", "seenAt": "2026-10-08T16:31:00.353997894Z" } ], "githubStars": 7, "npmWeekly": 172226, "securityTxt": { "url": "https://sumsub.com/.well-known/security.txt", "state": "valid", "expires": "2027-12-31T11:59:00Z", "checkedAt": "2026-10-08T15:38:36.412722848Z" }, "pages": [ { "url": "https://docs.sumsub.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:19:32.69717252Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "24fd7917e5f9" }, { "url": "https://sumsub.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:24:56.017931789Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8df9176ba407" }, { "url": "https://sumsub.com/privacy-notice-service/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:24:58.191382748Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "676c31f026df" }, { "url": "https://sumsub.com/terms-and-conditions/", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:25:00.198690776Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "63e133a2d160" } ], "updatedAt": "2026-10-09T11:46:41.99457637Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Socure Inc.", "b": "Sum and Substance Ltd", "name": "Vendor" }, { "a": "https://mcp.riskos.socure.com/sandbox", "b": "https://api.sumsub.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or 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 under Sumsub's terms and conditions. The agent skills repository and the @sumsub/websdk npm package are MIT", "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-03", "name": "Last release" }, { "a": "no document linked", "b": "2026-05-21", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-03-19", "name": "Privacy policy last updated" }, { "a": "yes", "b": "yes", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "35k npm/wk", "b": "172k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Sumsub scores 68.5 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 4 of 7 scored categories. Socure RiskOS leads on schema \u0026 documentation and payments \u0026 pricing.", "question": "Which is better for AI agents, Socure RiskOS or Sumsub?" }, { "answer": "Socure RiskOS needs an API key. Sumsub takes an API key or an OAuth sign-in.", "question": "Do Socure RiskOS and Sumsub need an API key?" }, { "answer": "Yes. Socure RiskOS has a hosted endpoint at https://mcp.riskos.socure.com/sandbox and Sumsub at https://api.sumsub.com.", "question": "Can an agent call Socure RiskOS and Sumsub without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 84 against 78", "Payments \u0026 pricing, 35 against 25" ], "also": null, "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": [ "Reliability, 80 against 75", "Agent ergonomics, 60 against 46", "Security \u0026 auth, 80 against 60", "Transparency \u0026 trust, 74 against 68" ], "also": null, "goodFor": "An agent that starts verifications, sends links, reads results and AML cases, and works case queues for a regulated business, with one token limited to those permissions.", "slug": "sumsub", "watchFor": "No idempotency keys and no Retry-After or backoff guidance found in the reviewed documentation" } ], "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-sumsub.json", "title": "ComplyCube vs Sumsub", "url": "https://www.anchorterminal.com/compare/complycube-vs-sumsub" }, { "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-sumsub.json", "title": "Didit vs Sumsub", "url": "https://www.anchorterminal.com/compare/didit-vs-sumsub" }, { "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-sumsub.json", "title": "Jumio vs Sumsub", "url": "https://www.anchorterminal.com/compare/jumio-vs-sumsub" }, { "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-sumsub.json", "title": "Persona vs Sumsub", "url": "https://www.anchorterminal.com/compare/persona-vs-sumsub" }, { "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-sumsub.json", "title": "Shufti vs Sumsub", "url": "https://www.anchorterminal.com/compare/shufti-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/sumsub-vs-trulioo.json", "title": "Sumsub vs Trulioo", "url": "https://www.anchorterminal.com/compare/sumsub-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/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-sumsub.json", "title": "ComplyAdvantage vs Sumsub", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-sumsub" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/middesk-vs-sumsub.json", "title": "Middesk vs Sumsub", "url": "https://www.anchorterminal.com/compare/middesk-vs-sumsub" } ], "scores": [ { "by": 5, "edge": "sumsub", "key": "reliability", "name": "Reliability", "socure-riskos": 75, "sumsub": 80, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 6, "edge": "socure-riskos", "key": "schema", "name": "Schema \u0026 documentation", "socure-riskos": 84, "sumsub": 78, "weight": 13 }, { "by": 14, "edge": "sumsub", "key": "ergonomics", "name": "Agent ergonomics", "socure-riskos": 46, "sumsub": 60, "weight": 13 }, { "by": 20, "edge": "sumsub", "key": "security", "name": "Security \u0026 auth", "socure-riskos": 60, "sumsub": 80, "weight": 14 }, { "by": 10, "edge": "socure-riskos", "key": "payments", "name": "Payments \u0026 pricing", "socure-riskos": 35, "sumsub": 25, "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, "sumsub": 74, "weight": 7 }, { "by": 6, "edge": "sumsub", "key": "transparency", "name": "Transparency \u0026 trust", "socure-riskos": 68, "sumsub": 74, "weight": 7 } ], "summary": "Sumsub scores 68.5 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 4 of 7 scored categories. Socure RiskOS leads on schema \u0026 documentation and 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.", "sumsub": "Per-token permissions, an IP allowlist, HMAC-signed requests and a public OpenAPI spec with Markdown docs suit an agent working on verification cases. No idempotency keys or Retry-After guidance were found, there is no server SDK, and production access needs a browser signup, a bank card and Sumsub's review of the integration." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub", "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub.md", "slim": "https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub.min.md" }, "markdown": "Sumsub scores 68.5 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 4 of 7 scored categories. Socure RiskOS leads on schema \u0026 documentation and 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- Sumsub: grade B, 68.5/100, rank #200 of 842. Markdown https://www.anchorterminal.com/tools/sumsub.md · JSON https://www.anchorterminal.com/api/v1/tools/sumsub.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- Schema \u0026 documentation, 84 against 78\n- Payments \u0026 pricing, 35 against 25\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### Sumsub (B)\n\nGood for: An agent that starts verifications, sends links, reads results and AML cases, and works case queues for a regulated business, with one token limited to those permissions.\n\nAhead on:\n- Reliability, 80 against 75\n- Agent ergonomics, 60 against 46\n- Security \u0026 auth, 80 against 60\n- Transparency \u0026 trust, 74 against 68\n\nWatch for: No idempotency keys and no Retry-After or backoff guidance found in the reviewed documentation\n\n\n## Score by category\n\n| Category | Weight | Socure RiskOS | Sumsub | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 80 | Sumsub +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 78 | Socure RiskOS +6 |\n| Agent ergonomics | 13% (16.2 this run) | 46 | 60 | Sumsub +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 80 | Sumsub +20 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 25 | Socure RiskOS +10 |\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 | 74 | Sumsub +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.5 · B** | **68.5 · B** | |\n\n## Facts side by side\n\n| Fact | Socure RiskOS | Sumsub |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Socure Inc. | Sum and Substance Ltd |\n| Hosted endpoint | `https://mcp.riskos.socure.com/sandbox` | `https://api.sumsub.com` |\n| Transports | HTTP | HTTP |\n| Auth | API key | OAuth or 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 under Sumsub's terms and conditions. The agent skills repository and the @sumsub/websdk npm package are MIT |\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-03 |\n| Terms last updated | no document linked | 2026-05-21 |\n| Privacy policy last updated | no date given | 2026-03-19 |\n| Customer content may train models | yes | yes |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | not found in the text |\n| Terms or service can change without notice | | yes |\n| Arbitration or class-action waiver | | yes |\n| Popularity | 35k npm/wk | 172k 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**Sumsub.** Per-token permissions, an IP allowlist, HMAC-signed requests and a public OpenAPI spec with Markdown docs suit an agent working on verification cases. No idempotency keys or Retry-After guidance were found, there is no server SDK, and production access needs a browser signup, a bank card and Sumsub's review of the integration.\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### Sumsub\n\n1. Sign every request. X-App-Access-Sig is the lowercase hex HMAC-SHA256 of timestamp, uppercase method, path with query and raw body, and the timestamp must be within one minute of server time\n2. Use a sandbox token (prefix sbx) for agent work. Sandbox and production tokens are separate, and Sumsub's own skills refuse any other prefix\n3. Stay under 300 GET and 50 POST requests per 5 seconds, and under 500 new applicants per 24 hours in Sandbox\n4. Token permissions can't be edited after creation. Generate a new token with the narrower set and delete the old one\n5. Subscribe to the applicantReviewed webhook for results and verify x-payload-digest against the raw body before trusting it\n\n## Questions\n\n### Which is better for AI agents, Socure RiskOS or Sumsub?\n\nSumsub scores 68.5 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 4 of 7 scored categories. Socure RiskOS leads on schema \u0026 documentation and payments \u0026 pricing.\n\n### Do Socure RiskOS and Sumsub need an API key?\n\nSocure RiskOS needs an API key. Sumsub takes an API key or an OAuth sign-in.\n\n### Can an agent call Socure RiskOS and Sumsub without installing anything?\n\nYes. Socure RiskOS has a hosted endpoint at https://mcp.riskos.socure.com/sandbox and Sumsub at https://api.sumsub.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub.json, and with the fewest tokens: https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"socure-riskos\", \"b\": \"sumsub\"}`. From a terminal: `anchor compare socure-riskos sumsub`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/socure-riskos.json and https://www.anchorterminal.com/api/v1/tools/sumsub.json\n\n## Other comparisons with Socure RiskOS or Sumsub\n\n- [ComplyCube vs Socure RiskOS](https://www.anchorterminal.com/compare/complycube-vs-socure-riskos.md)\n- [ComplyCube vs Sumsub](https://www.anchorterminal.com/compare/complycube-vs-sumsub.md)\n- [Didit vs Socure RiskOS](https://www.anchorterminal.com/compare/didit-vs-socure-riskos.md)\n- [Didit vs Sumsub](https://www.anchorterminal.com/compare/didit-vs-sumsub.md)\n- [Jumio vs Socure RiskOS](https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.md)\n- [Jumio vs Sumsub](https://www.anchorterminal.com/compare/jumio-vs-sumsub.md)\n- [Persona vs Socure RiskOS](https://www.anchorterminal.com/compare/persona-vs-socure-riskos.md)\n- [Persona vs Sumsub](https://www.anchorterminal.com/compare/persona-vs-sumsub.md)\n- [Shufti vs Socure RiskOS](https://www.anchorterminal.com/compare/shufti-vs-socure-riskos.md)\n- [Shufti vs Sumsub](https://www.anchorterminal.com/compare/shufti-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- [Sumsub vs Trulioo](https://www.anchorterminal.com/compare/sumsub-vs-trulioo.md)\n- [Sumsub vs Veriff](https://www.anchorterminal.com/compare/sumsub-vs-veriff.md)\n- [ComplyAdvantage vs Socure RiskOS](https://www.anchorterminal.com/compare/complyadvantage-vs-socure-riskos.md)\n- [ComplyAdvantage vs Sumsub](https://www.anchorterminal.com/compare/complyadvantage-vs-sumsub.md)\n- [Middesk vs Socure RiskOS](https://www.anchorterminal.com/compare/middesk-vs-socure-riskos.md)\n- [Middesk vs Sumsub](https://www.anchorterminal.com/compare/middesk-vs-sumsub.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 Sumsub", "url": "" } ], "description": "Sumsub scores 68.5 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 4 of 7 scored categories. Socure RiskOS leads on schema \u0026 documentation and payments \u0026 pricing. Both do kyc identity. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Socure RiskOS B 63.5", "Sumsub B 68.5", "scores" ], "h1": "Socure RiskOS vs Sumsub", "image": "https://www.anchorterminal.com/assets/og/compare-socure-riskos-vs-sumsub.png", "path": "/compare/socure-riskos-vs-sumsub", "published": "2026-10-01", "section": "tools", "title": "Socure RiskOS vs Sumsub for AI agents, B 63.5 vs B 68.5", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub" }, "tokens": { "markdown": 2350, "slim": 680 }, "version": 1 }