{ "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": 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-14T09:42:08.226914142Z", "lastOk": true, "lastStatus": 403, "lastMs": 335, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 336, "p95ms24h": 370, "samples24h": 248, "samples30d": 1258, "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": 100, "ok": 100 } ] }, "vendorStatus": { "page": "https://status.socure.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:41.574295915Z" }, "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-14T09:42:08.226914142Z" } }, "answer": "Stripe Identity scores 77.7 (BB) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 6 of 7 scored categories. Socure RiskOS leads on reliability.", "b": { "slug": "stripe-identity", "name": "Stripe Identity", "vendor": "Stripe, LLC", "vendorUrl": "https://stripe.com/identity", "kind": "http-api", "category": "identity-verification", "summary": "Stripe Identity verifies government-issued photo IDs from more than 120 countries, matches them to selfies and validates US Social Security numbers. Sessions are created and read through the Stripe API, and the end user completes the check in Stripe's flow.", "url": "https://www.anchorterminal.com/tools/stripe-identity", "markdownUrl": "https://www.anchorterminal.com/tools/stripe-identity.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/stripe-identity.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/stripe-identity.json", "repo": "https://github.com/stripe/openapi", "license": "Proprietary service under the Stripe Services Agreement and Stripe Identity Terms. The OpenAPI spec and official SDKs are MIT", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "stripe" }, { "registry": "pypi", "name": "stripe" } ], "auth": "api-key", "authNotes": "Stripe secret key, restricted key or IP-restricted key, sent as HTTP basic auth or a Bearer token to https://api.stripe.com. Results such as status, name and address need only a secret key. Date of birth, ID number and document images need a restricted key with Identity permissions, which can read them for verifications in the last 48 hours, or for all verifications once the key is IP-restricted. Identity is activated through an application in the Dashboard (checked 2026-10-14).", "pricing": "usage", "pricingNotes": "£1.25 per completed document and selfie verification and 35p per ID number lookup (US SSNs only), charged when the user completes verification, on the United Kingdom page our network was served. The first 50 verifications are free. Custom pricing is offered above 2,000 verifications a month (https://stripe.com/identity, checked 2026-10-14).", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Identity endpoints, the Identity docs or the product page (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 24154234, "pypiWeekly": 11360574, "asOf": "2026-10-14" }, "docsUrl": "https://docs.stripe.com/identity", "llmsTxt": "https://docs.stripe.com/llms.txt", "openapi": "https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.json", "capabilities": [ "kyc.identity", "kyc.documents" ], "tags": [ "hosted", "api-key", "openapi", "llms-txt", "webhooks", "sandbox", "free-tier", "status-page", "python", "typescript", "go", "java", "ruby", "php", "bug-bounty", "soc2" ], "lastRelease": "2026-10-01", "graded": true, "anchor": { "graded": true, "score": 77.7, "grade": "BB", "agentReady": true, "rank": 21, "ranked": true, "rankOf": 1076, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 93, "maintenance": 85, "payments": 40, "reliability": 62, "schema": 94, "security": 86, "transparency": 85 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Stripe Identity runs on the Stripe API, with a public OpenAPI spec, idempotency keys, restricted keys for sensitive fields and a redact endpoint. The product page lists £1.25 per document and selfie check, and the first 50 are free. It has no watchlist or business screening, and outside GB, JP and the US it is in public beta.", "bestFor": "A business already on Stripe that needs document and selfie checks or US SSN validation with published prices.", "strengths": [ "Six typed Identity operations in Stripe's public OpenAPI spec, with Markdown docs and llms.txt", "Date of birth and ID number need a restricted key, and IP-restricted keys for reads after 48 hours", "Idempotency keys on every POST and cursor pagination with status and date filters", "Published prices of £1.25 per verification and 35p per US SSN lookup, with the first 50 verifications free", "`redact` removes personal data from the session, reports, events and request logs, confirmed by a webhook" ], "weaknesses": [ "Document, selfie and US SSN checks only. No sanctions or watchlist screening and no business verification", "Generally available only for businesses in GB, JP and the US, and a public beta in 30 other countries", "Use for credit, housing, employment or insurance decisions, and resale of results, are forbidden by the terms", "status.stripe.com renders only in JavaScript, so the incident history couldn't be read", "Stripe keeps a copy of verification data after redaction until the end user asks Stripe support to delete it" ], "agentNotes": [ "Send an Idempotency-Key based on your user reference when creating a VerificationSession, so a retry doesn't make a second session", "Send the end user the session URL or client secret. The person completes the check, the agent can't. Links expire after 48 hours", "Use a restricted key for `verified_outputs.dob` and `id_number`. Without an IP restriction it reads them only for 48 hours", "Wait for `identity.verification_session.verified` or `requires_input` webhooks instead of polling", "Treat `redact` as irreversible, and don't put personal data in metadata" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 77.7 } ], "editorialScores": { "ergonomics": 93, "maintenance": 85, "payments": 40, "reliability": 62, "schema": 94, "security": 86, "transparency": 72 }, "provenanceScore": 98 }, "connect": { "http": "curl https://api.stripe.com/v1/identity/verification_sessions \\\n -u \"\u003c\u003cYOUR_SECRET_KEY\u003e\u003e:\" \\\n -d type=document" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/stripe-identity" }, "sameCompany": [ "stripe-mcp" ], "area": "domain-data", "provenance": { "legalEntity": "Stripe, LLC", "domain": "stripe.com", "domainRegistered": "1995-09-12", "endpointOnVendorDomain": true, "terms": "https://stripe.com/identity/legal", "privacy": "https://stripe.com/privacy", "statusPage": "https://status.stripe.com", "changelog": "https://docs.stripe.com/changelog", "securityTxt": "valid", "checked": "2026-10-14", "notes": [ "stripe.com/identity/legal redirects to the Stripe Services Agreement service terms, last updated 2 October 2026, which hold the Stripe Identity Terms.", "Our network was redirected to the /gb/ copies of the terms, privacy policy and service provider list.", "stripe.com/.well-known/security.txt points to HackerOne and expires 2026-12-31.", "stripe.com was registered in 1995, before Stripe bought it." ], "score": 98 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/stripe-identity.json", "live": { "slug": "stripe-identity", "vendorStatus": { "page": "https://status.stripe.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:58.613651718Z" }, "updatedAt": "2026-10-14T08:53:58.613651718Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Socure Inc.", "b": "Stripe, LLC", "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 under the Stripe Services Agreement and Stripe Identity Terms. The OpenAPI spec and official SDKs 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-01", "name": "Last release" }, { "a": "no document linked", "b": "2026-09-28", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-04-28", "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": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "35k npm/wk", "b": "24.2M npm/wk, 11.4M PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Stripe Identity scores 77.7 (BB) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 6 of 7 scored categories. Socure RiskOS leads on reliability.", "question": "Which is better for AI agents, Socure RiskOS or Stripe Identity?" }, { "answer": "Both need an API key.", "question": "Do Socure RiskOS and Stripe Identity need an API key?" }, { "answer": "Socure RiskOS has a hosted endpoint at https://mcp.riskos.socure.com/sandbox. No hosted endpoint is listed for Stripe Identity.", "question": "Can an agent call Socure RiskOS and Stripe Identity 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": [ "Schema \u0026 documentation, 94 against 84", "Agent ergonomics, 93 against 46", "Security \u0026 auth, 86 against 60", "Payments \u0026 pricing, 40 against 35", "Maintenance \u0026 community, 85 against 75", "Transparency \u0026 trust, 85 against 68" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "A business already on Stripe that needs document and selfie checks or US SSN validation with published prices.", "slug": "stripe-identity", "watchFor": "Document, selfie and US SSN checks only. No sanctions or watchlist screening and no business verification" } ], "job": { "capability": "kyc.identity", "name": "Identity verification" }, "others": [ { "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/alloy-vs-stripe-identity.json", "title": "Alloy vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/alloy-vs-stripe-identity" }, { "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-stripe-identity.json", "title": "ComplyCube vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/complycube-vs-stripe-identity" }, { "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-stripe-identity.json", "title": "Didit vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/didit-vs-stripe-identity" }, { "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/entrust-identity-verification-vs-stripe-identity.json", "title": "Entrust Identity Verification (formerly Onfido) vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-stripe-identity" }, { "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-stripe-identity.json", "title": "Jumio vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/jumio-vs-stripe-identity" }, { "json": "https://www.anchorterminal.com/compare/middesk-vs-stripe-identity.json", "title": "Middesk vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/middesk-vs-stripe-identity" }, { "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-stripe-identity.json", "title": "Persona vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/persona-vs-stripe-identity" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos.json", "title": "Plaid Identity Verification vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos" }, { "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/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-stripe-identity.json", "title": "Shufti vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/shufti-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/stripe-identity-vs-sumsub.json", "title": "Stripe Identity vs Sumsub", "url": "https://www.anchorterminal.com/compare/stripe-identity-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/stripe-identity-vs-trulioo.json", "title": "Stripe Identity vs Trulioo", "url": "https://www.anchorterminal.com/compare/stripe-identity-vs-trulioo" }, { "json": "https://www.anchorterminal.com/compare/stripe-identity-vs-veriff.json", "title": "Stripe Identity vs Veriff", "url": "https://www.anchorterminal.com/compare/stripe-identity-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/stripe-identity-vs-vouched.json", "title": "Stripe Identity vs Vouched", "url": "https://www.anchorterminal.com/compare/stripe-identity-vs-vouched" }, { "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": 13, "edge": "socure-riskos", "key": "reliability", "name": "Reliability", "socure-riskos": 75, "stripe-identity": 62, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 10, "edge": "stripe-identity", "key": "schema", "name": "Schema \u0026 documentation", "socure-riskos": 84, "stripe-identity": 94, "weight": 13 }, { "by": 47, "edge": "stripe-identity", "key": "ergonomics", "name": "Agent ergonomics", "socure-riskos": 46, "stripe-identity": 93, "weight": 13 }, { "by": 26, "edge": "stripe-identity", "key": "security", "name": "Security \u0026 auth", "socure-riskos": 60, "stripe-identity": 86, "weight": 14 }, { "by": 5, "edge": "stripe-identity", "key": "payments", "name": "Payments \u0026 pricing", "socure-riskos": 35, "stripe-identity": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 10, "edge": "stripe-identity", "key": "maintenance", "name": "Maintenance \u0026 community", "socure-riskos": 75, "stripe-identity": 85, "weight": 7 }, { "by": 17, "edge": "stripe-identity", "key": "transparency", "name": "Transparency \u0026 trust", "socure-riskos": 68, "stripe-identity": 85, "weight": 7 } ], "summary": "Stripe Identity scores 77.7 (BB) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 6 of 7 scored categories. Socure RiskOS leads on reliability. Both do identity verification.", "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.", "stripe-identity": "Stripe Identity runs on the Stripe API, with a public OpenAPI spec, idempotency keys, restricted keys for sensitive fields and a redact endpoint. The product page lists £1.25 per document and selfie check, and the first 50 are free. It has no watchlist or business screening, and outside GB, JP and the US it is in public beta." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/socure-riskos-vs-stripe-identity", "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-stripe-identity.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/socure-riskos-vs-stripe-identity.md", "slim": "https://www.anchorterminal.com/compare/socure-riskos-vs-stripe-identity.min.md" }, "markdown": "Stripe Identity scores 77.7 (BB) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 6 of 7 scored categories. Socure RiskOS leads on reliability. Both do identity verification.\n\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- Stripe Identity: grade BB, 77.7/100, rank #21 of 1076. Markdown https://www.anchorterminal.com/tools/stripe-identity.md · JSON https://www.anchorterminal.com/api/v1/tools/stripe-identity.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### 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### Stripe Identity (BB)\n\nGood for: A business already on Stripe that needs document and selfie checks or US SSN validation with published prices.\n\nAhead on:\n- Schema \u0026 documentation, 94 against 84\n- Agent ergonomics, 93 against 46\n- Security \u0026 auth, 86 against 60\n- Payments \u0026 pricing, 40 against 35\n- Maintenance \u0026 community, 85 against 75\n- Transparency \u0026 trust, 85 against 68\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: Document, selfie and US SSN checks only. No sanctions or watchlist screening and no business verification\n\n\n## Score by category\n\n| Category | Weight | Socure RiskOS | Stripe Identity | 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 | 94 | Stripe Identity +10 |\n| Agent ergonomics | 13% (16.2 this run) | 46 | 93 | Stripe Identity +47 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 86 | Stripe Identity +26 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 40 | Stripe Identity +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 85 | Stripe Identity +10 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 68 | 85 | Stripe Identity +17 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.5 · B** | **77.7 · BB** | |\n\n## Facts side by side\n\n| Fact | Socure RiskOS | Stripe Identity |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Socure Inc. | Stripe, LLC |\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 under the Stripe Services Agreement and Stripe Identity Terms. The OpenAPI spec and official SDKs 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-01 |\n| Terms last updated | no document linked | 2026-09-28 |\n| Privacy policy last updated | no date given | 2026-04-28 |\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 | | not found in the text |\n| Arbitration or class-action waiver | | not found in the text |\n| Popularity | 35k npm/wk | 24.2M npm/wk, 11.4M PyPI/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**Stripe Identity.** Stripe Identity runs on the Stripe API, with a public OpenAPI spec, idempotency keys, restricted keys for sensitive fields and a redact endpoint. The product page lists £1.25 per document and selfie check, and the first 50 are free. It has no watchlist or business screening, and outside GB, JP and the US it is in public beta.\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### Stripe Identity\n\n1. Send an Idempotency-Key based on your user reference when creating a VerificationSession, so a retry doesn't make a second session\n2. Send the end user the session URL or client secret. The person completes the check, the agent can't. Links expire after 48 hours\n3. Use a restricted key for `verified_outputs.dob` and `id_number`. Without an IP restriction it reads them only for 48 hours\n4. Wait for `identity.verification_session.verified` or `requires_input` webhooks instead of polling\n5. Treat `redact` as irreversible, and don't put personal data in metadata\n\n## Questions\n\n### Which is better for AI agents, Socure RiskOS or Stripe Identity?\n\nStripe Identity scores 77.7 (BB) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 6 of 7 scored categories. Socure RiskOS leads on reliability.\n\n### Do Socure RiskOS and Stripe Identity need an API key?\n\nBoth need an API key.\n\n### Can an agent call Socure RiskOS and Stripe Identity without installing anything?\n\nSocure RiskOS has a hosted endpoint at https://mcp.riskos.socure.com/sandbox. No hosted endpoint is listed for Stripe Identity.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/socure-riskos-vs-stripe-identity.json, and with the fewest tokens: https://www.anchorterminal.com/compare/socure-riskos-vs-stripe-identity.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"socure-riskos\", \"b\": \"stripe-identity\"}`. From a terminal: `anchor compare socure-riskos stripe-identity`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/socure-riskos.json and https://www.anchorterminal.com/api/v1/tools/stripe-identity.json\n\n## Other comparisons with Socure RiskOS or Stripe Identity\n\n- [Alloy vs Socure RiskOS](https://www.anchorterminal.com/compare/alloy-vs-socure-riskos.md)\n- [Alloy vs Stripe Identity](https://www.anchorterminal.com/compare/alloy-vs-stripe-identity.md)\n- [ComplyCube vs Socure RiskOS](https://www.anchorterminal.com/compare/complycube-vs-socure-riskos.md)\n- [ComplyCube vs Stripe Identity](https://www.anchorterminal.com/compare/complycube-vs-stripe-identity.md)\n- [Didit vs Socure RiskOS](https://www.anchorterminal.com/compare/didit-vs-socure-riskos.md)\n- [Didit vs Stripe Identity](https://www.anchorterminal.com/compare/didit-vs-stripe-identity.md)\n- [Entrust Identity Verification (formerly Onfido) vs Socure RiskOS](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-socure-riskos.md)\n- [Entrust Identity Verification (formerly Onfido) vs Stripe Identity](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-stripe-identity.md)\n- [Jumio vs Socure RiskOS](https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.md)\n- [Jumio vs Stripe Identity](https://www.anchorterminal.com/compare/jumio-vs-stripe-identity.md)\n- [Middesk vs Stripe Identity](https://www.anchorterminal.com/compare/middesk-vs-stripe-identity.md)\n- [Persona vs Socure RiskOS](https://www.anchorterminal.com/compare/persona-vs-socure-riskos.md)\n- [Persona vs Stripe Identity](https://www.anchorterminal.com/compare/persona-vs-stripe-identity.md)\n- [Plaid Identity Verification vs Socure RiskOS](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos.md)\n- [Plaid Identity Verification vs Stripe Identity](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-stripe-identity.md)\n- [Shufti vs Socure RiskOS](https://www.anchorterminal.com/compare/shufti-vs-socure-riskos.md)\n- [Shufti vs Stripe Identity](https://www.anchorterminal.com/compare/shufti-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- [Stripe Identity vs Sumsub](https://www.anchorterminal.com/compare/stripe-identity-vs-sumsub.md)\n- [Stripe Identity vs Trulioo](https://www.anchorterminal.com/compare/stripe-identity-vs-trulioo.md)\n- [Stripe Identity vs Veriff](https://www.anchorterminal.com/compare/stripe-identity-vs-veriff.md)\n- [Stripe Identity vs Vouched](https://www.anchorterminal.com/compare/stripe-identity-vs-vouched.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": "Socure RiskOS vs Stripe Identity", "url": "" } ], "description": "Stripe Identity scores 77.7 (BB) to Socure RiskOS's 63.5 (B) for identity verification. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Socure RiskOS B 63.5", "Stripe Identity BB 77.7", "scores" ], "h1": "Socure RiskOS vs Stripe Identity", "image": "https://www.anchorterminal.com/assets/og/compare-socure-riskos-vs-stripe-identity.png", "path": "/compare/socure-riskos-vs-stripe-identity", "published": "2026-10-01", "section": "tools", "title": "Socure RiskOS vs Stripe Identity for AI agents (2026)", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/socure-riskos-vs-stripe-identity" }, "tokens": { "markdown": 2750, "slim": 730 }, "version": 1 }