{ "data": { "a": { "slug": "didit", "name": "Didit", "vendor": "Didit Identity Spain, S.L.", "vendorUrl": "https://didit.me", "kind": "http-api", "category": "identity-verification", "summary": "Didit is a hosted identity verification service for document, liveness, face match, sanctions screening and business registry checks. Developers reach it through a REST API with an OpenAPI spec, a hosted MCP server and client SDKs.", "url": "https://www.anchorterminal.com/tools/didit", "markdownUrl": "https://www.anchorterminal.com/tools/didit.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/didit.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/didit.json", "repo": "https://github.com/didit-protocol/mcp", "license": "Proprietary service under Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://verification.didit.me", "packages": [ { "registry": "npm", "name": "@didit-protocol/mcp-server" }, { "registry": "npm", "name": "@didit-protocol/sdk-web" }, { "registry": "npm", "name": "@didit-protocol/sdk-react-native" } ], "auth": "mixed", "authNotes": "Self-serve. The REST API takes an application API key in the `x-api-key` header. A key comes from the Business Console or from the registration API on `apx.didit.me`, which emails a 6-character code and returns the key with no browser step. Each application has a primary key with full access and any number of named keys with read or write access per resource, workflow and status limits, an IP allowlist and an expiry date. Named keys are created, rotated and revoked only in the console. The hosted MCP server uses OAuth 2.1 with PKCE and dynamic client registration, with the scopes `didit:management` and `didit:verification`, and accepts no API key.", "pricing": "usage", "pricingNotes": "Pay per completed check from prepaid USD credits, with no contract or minimum and no card needed to sign up. In a workflow, ID verification is $0.15, passive liveness $0.10, face match $0.05, device and IP analysis $0.03 and AML screening $0.20. Until 1 November 2026 each organisation gets 500 free checks a month for each of the first four. From 1 November that becomes $10 of credit a month, with optional Growth ($99 a month) and Scale ($299 a month) plans. Sandbox applications are not billed (https://docs.didit.me/getting-started/pricing, checked 2026-10-08).", "priceSummary": "$0.15 / tx", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI spec, the docs index or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 156, "popularity": { "githubStars": 0, "npmWeekly": 27338, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.didit.me", "llmsTxt": "https://docs.didit.me/llms.txt", "openapi": "https://docs.didit.me/openapi-25.json", "registryName": "me.didit/mcp", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening", "kyc.business", "kyc.cases" ], "tags": [ "hosted", "api-key", "oauth", "mcp", "webhooks", "openapi", "llms-txt", "free-tier", "no-card", "sandbox", "status-page", "sla", "soc2", "iso27001" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 75, "grade": "BB", "agentReady": true, "rank": 60, "ranked": true, "rankOf": 842, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 82, "payments": 60, "reliability": 80, "schema": 88, "security": 76, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A self-serve verification API with public per-check prices, key registration by API, scoped keys and a 365-day audit log. The status page shows three incidents marked major between 22 July and 4 September 2026, each a partial outage of the core APIs, and the sub-processor list isn't public.", "bestFor": "A team that wants document, liveness, screening and business registry checks from one API with public prices and no sales step, and an agent that has to set itself up.", "strengths": [ "An account and API key can be created by API at `apx.didit.me/auth/v2/programmatic/register/`, with an emailed code and no browser step", "Public OpenAPI 3.0.0 spec with 256 operations, plus llms.txt and a Markdown copy of every docs page", "Named API keys take read or write access per resource, workflow limits, an IP allowlist and an expiry date, and rotation keeps the old secret for 24 hours", "429 responses carry `Retry-After`, limits are published per scope, and 31 operations document an `Idempotency-Key` header or a reuse rule", "Per-check prices are public, charged only when a check finishes, with 500 free checks a month per core feature until 1 November 2026" ], "weaknesses": [ "Three incidents marked major on status.didit.me from 22 July to 4 September 2026, each a partial outage of the core APIs traced to the primary database", "No server-side SDK in any language. The published SDKs are capture clients for web, iOS, Android, React Native and Flutter", "The data processing addendum says the sub-processor list is published at `/terms/sub-processors`, but that address shows the legal index, which says the list is sent after a signed NDA", "Verification data is used for model training by default until an organisation owner turns it off in the console", "The hosted MCP server lists 156 tools to a signed-in user, 23 of them destructive, and role checks run in a mode that logs without hiding tools by default" ], "agentNotes": [ "Register with `POST https://apx.didit.me/auth/v2/programmatic/register/`, then `verify-email` with the emailed 6-character code. Use a real inbox, because reserved test domains return 500.", "Send the key as `x-api-key` to `https://verification.didit.me/v3/`. The JWT from registration works only on `apx.didit.me`.", "Create a workflow before `POST /v3/session/`. `workflow_id` is the only required field, and an unfinished session with the same `vendor_data` is returned again.", "Read results from webhooks and use `GET /v3/session/{sessionId}/decision/` for back-fill. Every per-feature result is a plural array.", "The MCP server at `https://mcp.didit.me/mcp` takes OAuth sign-in only, never an API key. Approve `didit:verification` alone when the task doesn't change workflows or keys." ], "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": 75 } ], "editorialScores": { "ergonomics": 69, "maintenance": 82, "payments": 60, "reliability": 80, "schema": 88, "security": 76, "transparency": 53 }, "provenanceScore": 73 }, "connect": { "http": "curl -X POST https://verification.didit.me/v3/session/ \\\n -H \"x-api-key: $DIDIT_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"workflow_id\":\"\u003cWORKFLOW_ID\u003e\",\"vendor_data\":\"user-42\",\"callback\":\"https://myapp.com/return\"}'", "claudeCode": "claude mcp add --transport http didit https://mcp.didit.me/mcp", "config": { "mcpServers": { "didit": { "url": "https://mcp.didit.me/mcp" } } } }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/didit" }, "area": "domain-data", "unitPrices": [ { "item": "ID verification in a workflow (document capture)", "unit": "tx", "usd": 0.15, "note": "500 free a month until 1 November 2026" }, { "item": "Passive liveness in a workflow", "unit": "tx", "usd": 0.1, "note": "500 free a month until 1 November 2026" }, { "item": "Face match 1:1 in a workflow", "unit": "tx", "usd": 0.05, "note": "500 free a month until 1 November 2026" }, { "item": "Device and IP analysis in a workflow", "unit": "tx", "usd": 0.03, "note": "500 free a month until 1 November 2026" }, { "item": "AML screening", "unit": "tx", "usd": 0.2, "note": "no free allowance" }, { "item": "Proof of address", "unit": "tx", "usd": 0.2, "note": "no free allowance" }, { "item": "KYB registry, per selected company (Lite profile)", "unit": "tx", "usd": 2, "note": "search is charged separately at up to $0.50" } ], "provenance": { "legalEntity": "Didit Identity Spain, S.L.", "domain": "didit.me", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://didit.me/terms/business/", "privacy": "https://didit.me/terms/privacy-policy/", "statusPage": "https://status.didit.me", "changelog": "https://docs.didit.me/changelog/september-2026", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Business Terms and Conditions (updated 23 September 2026) name two contracting entities. Didit Identity Spain, S.L., CIF B22929327, Barcelona, contracts with clients in the EU, EEA, UK and Switzerland, and Didit Identity, Inc., Dover, Delaware, with clients elsewhere.", "The Business Terms are the self-serve contract and include the SLA as Annex 1 and the Data Processing Addendum as Annex 2. A separate Master Services Agreement covers enterprise order forms.", "The Privacy Policy was updated on 7 October 2026 and names the Spanish Data Protection Agency as lead supervisory authority. A Verification Privacy Notice supplements it for end users.", "didit.me/.well-known/security.txt and docs.didit.me/.well-known/security.txt return 404. The Information Security Policy sends reports to security@didit.me.", "The API answers at verification.didit.me, account routes at apx.didit.me and the MCP server at mcp.didit.me, all on the vendor's domain.", "The registration date of didit.me wasn't established. whois returned nothing and rdap.org has no RDAP service for .me." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/didit.json", "live": { "slug": "didit", "probe": { "target": "https://verification.didit.me", "method": "get", "lastAt": "2026-10-09T10:42:41.61590497Z", "lastOk": true, "lastStatus": 404, "lastMs": 75, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 57, "p95ms24h": 88, "samples24h": 164, "samples30d": 164, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 114, "ok": 114 } ] }, "vendorStatus": { "page": "https://status.didit.me", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T10:41:33.765097069Z" }, "versions": [ { "registry": "mcp-registry", "name": "me.didit/mcp", "version": "5.0.1", "seenAt": "2026-10-09T02:57:46.004536428Z" } ], "updatedAt": "2026-10-09T10:42:41.61590497Z" } }, "answer": "Didit scores 75 (BB) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 6 of 7 scored categories. Socure RiskOS leads on transparency \u0026 trust.", "b": { "slug": "socure-riskos", "name": "Socure RiskOS", "vendor": "Socure Inc.", "vendorUrl": "https://www.socure.com", "kind": "http-api", "category": "identity-verification", "summary": "Socure RiskOS is an identity verification and risk decisioning platform from Socure Inc. Its Evaluation API runs configured workflows for KYC, document and selfie checks, fraud scoring and watchlist screening, and returns a decision with reason codes.", "url": "https://www.anchorterminal.com/tools/socure-riskos", "markdownUrl": "https://www.anchorterminal.com/tools/socure-riskos.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/socure-riskos.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/socure-riskos.json", "repo": "https://github.com/socure-inc/.github", "license": "Proprietary service. No service agreement is published, and the OpenAPI file states its licence as Proprietary", "transports": [ "http" ], "remoteUrl": "https://mcp.riskos.socure.com/sandbox", "packages": [ { "registry": "npm", "name": "@socure-inc/device-risk-sdk" } ], "auth": "api-key", "authNotes": "Self-serve API key for the sandbox, sent as `Authorization: Bearer \u003ckey\u003e`. A person signs up in a browser for a Socure Launch sandbox account and copies the key from the Developer Workbench. Sandbox and production use separate keys and hosts. Production starts at 0 requests a second and needs Socure Support to activate it, and Enterprise accounts go through sandbox certification with Socure staff. Each key reaches every workflow, with no scopes. Regenerating a key keeps the old one working until it is deleted, and an additional key is requested from Support. The MCP server takes its own MCP Server Key. IP allowlisting, mutual TLS and payload encryption are optional (checked 2026-10-08).", "pricing": "usage", "pricingNotes": "Socure Launch charges per evaluation started in production, at $0.80 for document verification, $0.90 with watchlist screening, $1.00 for KYC, fraud and watchlist with a document step-up, and $1.30 with prefill. Launch accounts receive $1,000 in production credits each month. The sandbox is free, so an agent can build and test without a contract, but it returns predefined results. Evaluations an end user abandons are still charged. Socure Enterprise is priced through sales. Whether sign-up or the move to production asks for a card was not established (checked 2026-10-08).", "priceSummary": "$0.80 / tx", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, the OpenAPI file, the MCP server page or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": null, "npmWeekly": 35395, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://help.socure.com/riskos/docs", "llmsTxt": "https://help.socure.com/riskos/llms.txt", "openapi": "https://raw.githubusercontent.com/socure-inc/.github/main/openapi-spec/riskos-api-spec.json", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening", "kyc.business", "kyc.cases" ], "tags": [ "hosted", "usage", "sandbox", "api-key", "mcp", "openapi", "llms-txt", "webhooks", "status-page", "soc2", "iso27001", "fedramp" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 63.5, "grade": "B", "agentReady": false, "rank": 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-09T10:42:57.226946622Z", "lastOk": true, "lastStatus": 403, "lastMs": 344, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 334, "p95ms24h": 397, "samples24h": 33, "samples30d": 33, "days": [ { "date": "2026-10-09", "probes": 33, "ok": 33 } ] }, "vendorStatus": { "page": "https://status.socure.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T10:42:04.23425622Z" }, "updatedAt": "2026-10-09T10:42:57.226946622Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Didit Identity Spain, S.L.", "b": "Socure Inc.", "name": "Vendor" }, { "a": "https://verification.didit.me", "b": "https://mcp.riskos.socure.com/sandbox", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, stdio", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or 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 under Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT", "b": "Proprietary service. No service agreement is published, and the OpenAPI file states its licence as Proprietary", "name": "Licence" }, { "a": "156", "b": "9", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "me.didit/mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-08", "b": "2026-10-06", "name": "Last release" }, { "a": "2026-09-23", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-10-07", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "yes", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "0 stars, 27k npm/wk", "b": "35k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Didit scores 75 (BB) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 6 of 7 scored categories. Socure RiskOS leads on transparency \u0026 trust.", "question": "Which is better for AI agents, Didit or Socure RiskOS?" }, { "answer": "Didit takes an API key or an OAuth sign-in. Socure RiskOS needs an API key.", "question": "Do Didit and Socure RiskOS need an API key?" }, { "answer": "Yes. Didit has a hosted endpoint at https://verification.didit.me and Socure RiskOS at https://mcp.riskos.socure.com/sandbox.", "question": "Can an agent call Didit and Socure RiskOS without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 80 against 75", "Agent ergonomics, 69 against 46", "Security \u0026 auth, 76 against 60", "Payments \u0026 pricing, 60 against 35", "Maintenance \u0026 community, 82 against 75" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine", "Free to start without a card" ], "goodFor": "A team that wants document, liveness, screening and business registry checks from one API with public prices and no sales step, and an agent that has to set itself up.", "slug": "didit", "watchFor": "Three incidents marked major on status.didit.me from 22 July to 4 September 2026, each a partial outage of the core APIs traced to the primary database" }, { "aheadOn": [ "Transparency \u0026 trust, 68 against 63" ], "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" } ], "job": { "capability": "kyc.identity", "name": "Kyc identity" }, "others": [ { "json": "https://www.anchorterminal.com/compare/complycube-vs-didit.json", "title": "ComplyCube vs Didit", "url": "https://www.anchorterminal.com/compare/complycube-vs-didit" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-socure-riskos.json", "title": "ComplyCube vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/complycube-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-jumio.json", "title": "Didit vs Jumio", "url": "https://www.anchorterminal.com/compare/didit-vs-jumio" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-middesk.json", "title": "Didit vs Middesk", "url": "https://www.anchorterminal.com/compare/didit-vs-middesk" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-persona.json", "title": "Didit vs Persona", "url": "https://www.anchorterminal.com/compare/didit-vs-persona" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-shufti.json", "title": "Didit vs Shufti", "url": "https://www.anchorterminal.com/compare/didit-vs-shufti" }, { "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/didit-vs-trulioo.json", "title": "Didit vs Trulioo", "url": "https://www.anchorterminal.com/compare/didit-vs-trulioo" }, { "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/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/shufti-vs-socure-riskos.json", "title": "Shufti vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/shufti-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-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/complyadvantage-vs-didit.json", "title": "ComplyAdvantage vs Didit", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-didit" }, { "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": 5, "didit": 80, "edge": "didit", "key": "reliability", "name": "Reliability", "socure-riskos": 75, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 4, "didit": 88, "edge": "didit", "key": "schema", "name": "Schema \u0026 documentation", "socure-riskos": 84, "weight": 13 }, { "by": 23, "didit": 69, "edge": "didit", "key": "ergonomics", "name": "Agent ergonomics", "socure-riskos": 46, "weight": 13 }, { "by": 16, "didit": 76, "edge": "didit", "key": "security", "name": "Security \u0026 auth", "socure-riskos": 60, "weight": 14 }, { "by": 25, "didit": 60, "edge": "didit", "key": "payments", "name": "Payments \u0026 pricing", "socure-riskos": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 7, "didit": 82, "edge": "didit", "key": "maintenance", "name": "Maintenance \u0026 community", "socure-riskos": 75, "weight": 7 }, { "by": 5, "didit": 63, "edge": "socure-riskos", "key": "transparency", "name": "Transparency \u0026 trust", "socure-riskos": 68, "weight": 7 } ], "summary": "Didit scores 75 (BB) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 6 of 7 scored categories. Socure RiskOS leads on transparency \u0026 trust. Both do kyc identity.", "verdicts": { "didit": "A self-serve verification API with public per-check prices, key registration by API, scoped keys and a 365-day audit log. The status page shows three incidents marked major between 22 July and 4 September 2026, each a partial outage of the core APIs, and the sub-processor list isn't public.", "socure-riskos": "A public OpenAPI file, llms.txt, 15 documented error codes and dated release notes cover a ten-operation REST API, and Socure Launch publishes prices from $0.80 an evaluation with a free sandbox. API keys carry no scopes, no idempotency header is defined, no service terms are published, and production stays at zero requests until Socure activates it." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/didit-vs-socure-riskos", "json": "https://www.anchorterminal.com/compare/didit-vs-socure-riskos.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/didit-vs-socure-riskos.md", "slim": "https://www.anchorterminal.com/compare/didit-vs-socure-riskos.min.md" }, "markdown": "Didit scores 75 (BB) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 6 of 7 scored categories. Socure RiskOS leads on transparency \u0026 trust. Both do kyc identity.\n\n- Didit: grade BB, 75/100, rank #60 of 842. Markdown https://www.anchorterminal.com/tools/didit.md · JSON https://www.anchorterminal.com/api/v1/tools/didit.json\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\n## Which one, for what\n\n### Didit (BB)\n\nGood for: A team that wants document, liveness, screening and business registry checks from one API with public prices and no sales step, and an agent that has to set itself up.\n\nAhead on:\n- Reliability, 80 against 75\n- Agent ergonomics, 69 against 46\n- Security \u0026 auth, 76 against 60\n- Payments \u0026 pricing, 60 against 35\n- Maintenance \u0026 community, 82 against 75\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Three incidents marked major on status.didit.me from 22 July to 4 September 2026, each a partial outage of the core APIs traced to the primary database\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- Transparency \u0026 trust, 68 against 63\n\nWatch for: No service agreement or API terms are published. The only terms pages are website terms of use and end-user terms for document capture\n\n\n## Score by category\n\n| Category | Weight | Didit | Socure RiskOS | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 75 | Didit +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 84 | Didit +4 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 46 | Didit +23 |\n| Security \u0026 auth | 14% (17.5 this run) | 76 | 60 | Didit +16 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 35 | Didit +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 82 | 75 | Didit +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 68 | Socure RiskOS +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **75 · BB** | **63.5 · B** | |\n\n## Facts side by side\n\n| Fact | Didit | Socure RiskOS |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Didit Identity Spain, S.L. | Socure Inc. |\n| Hosted endpoint | `https://verification.didit.me` | `https://mcp.riskos.socure.com/sandbox` |\n| Transports | HTTP, Streamable HTTP, stdio | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT | Proprietary service. No service agreement is published, and the OpenAPI file states its licence as Proprietary |\n| Tools exposed | 156 | 9 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `me.didit/mcp` | not listed |\n| Last release | 2026-10-08 | 2026-10-06 |\n| Terms last updated | 2026-09-23 | no document linked |\n| Privacy policy last updated | 2026-10-07 | no date given |\n| Customer content may train models | yes, with an opt-out | yes |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | 0 stars, 27k npm/wk | 35k npm/wk |\n\n## Verdicts\n\n**Didit.** A self-serve verification API with public per-check prices, key registration by API, scoped keys and a 365-day audit log. The status page shows three incidents marked major between 22 July and 4 September 2026, each a partial outage of the core APIs, and the sub-processor list isn't public.\n\n**Socure RiskOS.** A public OpenAPI file, llms.txt, 15 documented error codes and dated release notes cover a ten-operation REST API, and Socure Launch publishes prices from $0.80 an evaluation with a free sandbox. API keys carry no scopes, no idempotency header is defined, no service terms are published, and production stays at zero requests until Socure activates it.\n\n## Before you call either\n\n### Didit\n\n1. Register with `POST https://apx.didit.me/auth/v2/programmatic/register/`, then `verify-email` with the emailed 6-character code. Use a real inbox, because reserved test domains return 500.\n2. Send the key as `x-api-key` to `https://verification.didit.me/v3/`. The JWT from registration works only on `apx.didit.me`.\n3. Create a workflow before `POST /v3/session/`. `workflow_id` is the only required field, and an unfinished session with the same `vendor_data` is returned again.\n4. Read results from webhooks and use `GET /v3/session/{sessionId}/decision/` for back-fill. Every per-feature result is a plural array.\n5. The MCP server at `https://mcp.didit.me/mcp` takes OAuth sign-in only, never an API key. Approve `didit:verification` alone when the task doesn't change workflows or keys.\n\n### Socure RiskOS\n\n1. Send `Authorization: Bearer \u003ckey\u003e` to `https://riskos.sandbox.socure.com/api/evaluation` for tests and `https://riskos.socure.com/api/evaluation` for live checks. The two environments use separate keys.\n2. Use dummy data only in the sandbox. It returns predefined results, connects to no live data source and expects the documented test values.\n3. Store the `eval_id` from every `POST /api/evaluation` response. No list or search endpoint exists to find it later.\n4. On 429 wait the seconds given in `X-Retry-After`. Do not blindly resend a failed `POST /api/evaluation`, because no idempotency header is documented and Launch bills each initiated evaluation.\n5. The MCP server at `https://mcp.riskos.socure.com/sandbox` reads docs, workflows and webhooks with its own MCP Server Key. It cannot run evaluations or read results.\n\n## Questions\n\n### Which is better for AI agents, Didit or Socure RiskOS?\n\nDidit scores 75 (BB) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 6 of 7 scored categories. Socure RiskOS leads on transparency \u0026 trust.\n\n### Do Didit and Socure RiskOS need an API key?\n\nDidit takes an API key or an OAuth sign-in. Socure RiskOS needs an API key.\n\n### Can an agent call Didit and Socure RiskOS without installing anything?\n\nYes. Didit has a hosted endpoint at https://verification.didit.me and Socure RiskOS at https://mcp.riskos.socure.com/sandbox.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/didit-vs-socure-riskos.json, and with the fewest tokens: https://www.anchorterminal.com/compare/didit-vs-socure-riskos.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"didit\", \"b\": \"socure-riskos\"}`. From a terminal: `anchor compare didit socure-riskos`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/didit.json and https://www.anchorterminal.com/api/v1/tools/socure-riskos.json\n\n## Other comparisons with Didit or Socure RiskOS\n\n- [ComplyCube vs Didit](https://www.anchorterminal.com/compare/complycube-vs-didit.md)\n- [ComplyCube vs Socure RiskOS](https://www.anchorterminal.com/compare/complycube-vs-socure-riskos.md)\n- [Didit vs Jumio](https://www.anchorterminal.com/compare/didit-vs-jumio.md)\n- [Didit vs Middesk](https://www.anchorterminal.com/compare/didit-vs-middesk.md)\n- [Didit vs Persona](https://www.anchorterminal.com/compare/didit-vs-persona.md)\n- [Didit vs Shufti](https://www.anchorterminal.com/compare/didit-vs-shufti.md)\n- [Didit vs Sumsub](https://www.anchorterminal.com/compare/didit-vs-sumsub.md)\n- [Didit vs Trulioo](https://www.anchorterminal.com/compare/didit-vs-trulioo.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- [Persona vs Socure RiskOS](https://www.anchorterminal.com/compare/persona-vs-socure-riskos.md)\n- [Shufti vs Socure RiskOS](https://www.anchorterminal.com/compare/shufti-vs-socure-riskos.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- [ComplyAdvantage vs Didit](https://www.anchorterminal.com/compare/complyadvantage-vs-didit.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-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": "Didit vs Socure RiskOS", "url": "" } ], "description": "Didit scores 75 (BB) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 6 of 7 scored categories. Socure RiskOS leads on transparency \u0026 trust. Both do kyc identity. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Didit BB 75", "Socure RiskOS B 63.5", "scores" ], "h1": "Didit vs Socure RiskOS", "image": "https://www.anchorterminal.com/assets/og/compare-didit-vs-socure-riskos.png", "path": "/compare/didit-vs-socure-riskos", "published": "2026-10-01", "section": "tools", "title": "Didit vs Socure RiskOS for AI agents, BB 75 vs B 63.5", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/didit-vs-socure-riskos" }, "tokens": { "markdown": 2400, "slim": 780 }, "version": 1 }