{
  "data": {
    "a": {
      "slug": "persona",
      "name": "Persona",
      "vendor": "Persona Identities, Inc.",
      "vendorUrl": "https://withpersona.com",
      "kind": "http-api",
      "category": "identity-verification",
      "summary": "Persona is an identity verification platform from Persona Identities, Inc. Its REST API and hosted MCP server create inquiries, run government ID, selfie, document and database verifications, screen people and businesses against watchlists, and manage review cases.",
      "url": "https://www.anchorterminal.com/tools/persona",
      "markdownUrl": "https://www.anchorterminal.com/tools/persona.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/persona.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/persona.json",
      "license": "Proprietary service under Persona's terms of service. The `persona` JavaScript client on npm is MIT",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://mcp.withpersona.com",
      "packages": [
        {
          "registry": "npm",
          "name": "persona"
        }
      ],
      "auth": "api-key",
      "authNotes": "Self-serve API key, sent as `Authorization: Bearer \u003ckey\u003e` to https://api.withpersona.com/api/v1. A browser sign-up with a business email gives a sandbox key (`persona_sandbox_...`) at once. A production key (`persona_production_...`) needs a plan and Persona's approval of the organisation. Each key can be limited to about 50 read and write permissions per resource, given its own rate limit and an IP allowlist, and expired through the dashboard or the API. A new key has every standard permission until someone limits it. The MCP server at https://mcp.withpersona.com takes the same key. Its help article says OAuth is coming and isn't available yet (checked 2026-10-08).",
      "pricing": "paid",
      "pricingNotes": "The Essential plan starts at $250 a month on a 12-month contract with 500 verifications or reports a month included, then $1.50 for each further one, per the help centre. Growth and Enterprise are priced through sales. A 60-day trial with no card gives sandbox access and up to 50 services, so an agent can build and test without a contract, but the sandbox performs no real verifications. A Startup Programme gives eligible small companies 500 free verifications a month for a year. The pricing page itself refused our reader (checked 2026-10-08).",
      "priceSummary": "$250 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the API docs, the OpenAPI file, the MCP tool list or the help centre's plan articles (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": 190,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 570188,
        "pypiWeekly": null,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://docs.withpersona.com/getting-started",
      "llmsTxt": "https://docs.withpersona.com/llms.txt",
      "openapi": "https://docs.withpersona.com/openapi/api-reference.json",
      "capabilities": [
        "kyc.identity",
        "kyc.business",
        "kyc.documents",
        "kyc.screening",
        "kyc.cases"
      ],
      "tags": [
        "hosted",
        "paid",
        "sandbox",
        "api-key",
        "mcp",
        "openapi",
        "llms-txt",
        "webhooks",
        "json-api",
        "status-page",
        "soc2",
        "iso27001"
      ],
      "lastRelease": "2026-09-29",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 69.5,
        "grade": "B",
        "agentReady": false,
        "rank": 176,
        "ranked": true,
        "rankOf": 842,
        "categoryRank": 2,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 74,
          "maintenance": 75,
          "payments": 35,
          "reliability": 70,
          "schema": 85,
          "security": 73,
          "transparency": 68
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-08"
        },
        "negative": 0,
        "verdict": "The REST API has a public OpenAPI 3.1 file, llms.txt, API keys with per-resource permissions, idempotency keys on every POST and a 60-day sandbox trial with no card. Production needs a business review and a 12-month plan from $250 a month. The status page lists 11 incidents since 10 July 2026, including 70 minutes of timeouts across all products.",
        "bestFor": "A company that already runs Persona and wants an agent to create inquiries from templates, read verification and report results, screen against watchlists and work review cases with a permission-limited key.",
        "strengths": [
          "Public OpenAPI 3.1 file with 231 operations and 141 webhook definitions, plus llms.txt and a Markdown copy of every docs page",
          "API keys take about 50 read and write permissions per resource, an IP allowlist, their own rate limit and an expiry endpoint",
          "`Idempotency-Key` on every POST, cursor pagination, and `fields` and `include` parameters that trim responses",
          "API logs kept for two weeks and user audit logs for six months, both readable through the API",
          "Dated API versions selected per key or per request with `Persona-Version`, and a changelog with an RSS feed"
        ],
        "weaknesses": [
          "Production access needs Persona's approval and a 12-month plan from $250 a month, and API-only integration is limited to Enterprise plans",
          "Eleven incidents on the status page since 10 July 2026, five marked partial outage, most on document and government ID verifications",
          "The MCP server lists all 190 tools whatever the key allows, with no annotations, toolsets or read-only subset, and OAuth isn't available yet",
          "No official server-side SDK was found. The npm, iOS, Android and React Native packages are clients for the end-user flow",
          "The marketing site, terms, privacy policy and pricing page answered our reader with a bot check, and no SLA was found in the docs or help centre"
        ],
        "agentNotes": [
          "Ask for a dedicated key limited to the permissions the task needs. A new key has every standard permission until it's limited",
          "Send `Persona-Version` on every call and an `Idempotency-Key` on every POST. A replayed key returns the first result, including a 500",
          "Treat redact calls as irreversible. They permanently delete personal data and cascade to downstream objects",
          "Stay under 300 requests a minute in production, read `RateLimit-Remaining` and `Quota-Remaining`, and back off on 429 because rejected requests still count",
          "Use `fields` and `include` to cut response size. Through MCP these parameters aren't exposed, and only 14 tools take `filter`"
        ],
        "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": 69.5
          }
        ],
        "editorialScores": {
          "ergonomics": 74,
          "maintenance": 75,
          "payments": 35,
          "reliability": 70,
          "schema": 85,
          "security": 73,
          "transparency": 46
        },
        "provenanceScore": 90
      },
      "connect": {
        "http": "curl --request POST \\\n     --url https://api.withpersona.com/api/v1/inquiries \\\n     --header 'Persona-Version: 2023-01-05' \\\n     --header 'accept: application/json' \\\n     --header 'authorization: Bearer persona_sandbox_YOURAPIKEY' \\\n     --header 'content-type: application/json' \\\n     --data '{\"data\":{\"attributes\":{\"inquiry-template-id\":\"itmpl_YOURTEMPLATEID\",\"fields\":{\"name-first\":\"Jane\",\"name-last\":\"Doe\",\"birthdate\":\"1994-04-12\"}}}}'"
      },
      "letme": {
        "capability": "https://letme.dev/kyc.identity",
        "tool": "https://letme.dev/persona"
      },
      "area": "domain-data",
      "unitPrices": [
        {
          "item": "Essential plan",
          "unit": "month",
          "usd": 250,
          "note": "12-month contract, 500 verifications or reports a month included, unused ones don't roll over"
        },
        {
          "item": "Additional verification or report on the Essential plan",
          "unit": "tx",
          "usd": 1.5,
          "note": "Each service beyond the 500 included a month"
        }
      ],
      "provenance": {
        "legalEntity": "Persona Identities, Inc.",
        "domain": "withpersona.com",
        "domainRegistered": "2018-09-24",
        "endpointOnVendorDomain": true,
        "terms": "https://withpersona.com/legal/terms-of-service",
        "privacy": "https://withpersona.com/legal/privacy-policy",
        "statusPage": "https://status.withpersona.com",
        "changelog": "https://docs.withpersona.com/api-reference/versioning/changelog",
        "securityTxt": "valid",
        "checked": "2026-10-08",
        "notes": [
          "The help centre footer reads \"2026 Persona Identities, Inc.\", and the `persona` npm package names Persona Identities, Inc. as author.",
          "The API answers at api.withpersona.com and the MCP server at mcp.withpersona.com, both withpersona.com subdomains.",
          "withpersona.com/.well-known/security.txt gives security@withpersona.com, an expiry of 17 February 2027 and a note that disclosure runs through Bugcrowd.",
          "The terms and privacy URLs are the ones the status page links to. Both pages, and the rest of withpersona.com, answered our reader with a bot check (HTTP 403), so their text wasn't read.",
          "RDAP for withpersona.com gives a registration date of 2018-09-24 and MarkMonitor Inc. as registrar."
        ],
        "score": 90
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/persona.json",
      "live": {
        "slug": "persona",
        "probe": {
          "target": "https://mcp.withpersona.com",
          "method": "get",
          "lastAt": "2026-10-09T10:42:52.467979059Z",
          "lastOk": true,
          "lastStatus": 405,
          "lastMs": 176,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 149,
          "p95ms24h": 404,
          "samples24h": 207,
          "samples30d": 207,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 93,
              "ok": 93
            },
            {
              "date": "2026-10-09",
              "probes": 114,
              "ok": 114
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.withpersona.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-09T07:58:25.314745809Z"
        },
        "versions": [
          {
            "registry": "npm",
            "name": "persona",
            "version": "5.9.0",
            "seenAt": "2026-10-08T16:25:07.765894859Z"
          }
        ],
        "npmWeekly": 570188,
        "securityTxt": {
          "url": "https://withpersona.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-02-17T08:00:00.000Z",
          "checkedAt": "2026-10-08T15:39:00.840131962Z"
        },
        "pages": [
          {
            "url": "https://docs.withpersona.com/api-reference/versioning/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-08T18:19:46.701685957Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "6f0e8de3c16e"
          },
          {
            "url": "https://withpersona.com/legal/privacy-policy",
            "kind": "privacy",
            "status": 403,
            "checkedAt": "2026-10-08T18:25:46.538922013Z",
            "changedAt": "0001-01-01T00:00:00Z"
          },
          {
            "url": "https://withpersona.com/legal/terms-of-service",
            "kind": "terms",
            "status": 403,
            "checkedAt": "2026-10-08T18:25:48.548892401Z",
            "changedAt": "0001-01-01T00:00:00Z"
          }
        ],
        "updatedAt": "2026-10-09T10:42:52.467979059Z"
      }
    },
    "answer": "Persona scores 69.5 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 3 of 7 scored categories. Socure RiskOS leads on reliability.",
    "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": "Persona Identities, Inc.",
        "b": "Socure Inc.",
        "name": "Vendor"
      },
      {
        "a": "https://mcp.withpersona.com",
        "b": "https://mcp.riskos.socure.com/sandbox",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under Persona's terms of service. The `persona` JavaScript client on npm is MIT",
        "b": "Proprietary service. No service agreement is published, and the OpenAPI file states its licence as Proprietary",
        "name": "Licence"
      },
      {
        "a": "190",
        "b": "9",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-09-29",
        "b": "2026-10-06",
        "name": "Last release"
      },
      {
        "a": "couldn't be read",
        "b": "no document linked",
        "name": "Terms last updated"
      },
      {
        "a": "couldn't be read",
        "b": "no date given",
        "name": "Privacy policy last updated"
      },
      {
        "a": "couldn't be read",
        "b": "yes",
        "name": "Customer content may train models"
      },
      {
        "a": "couldn't be read",
        "b": "",
        "name": "Terms restrict automated access"
      },
      {
        "a": "couldn't be read",
        "b": "",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "couldn't be read",
        "b": "",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "couldn't be read",
        "b": "",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "570k npm/wk",
        "b": "35k npm/wk",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Persona scores 69.5 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 3 of 7 scored categories. Socure RiskOS leads on reliability.",
        "question": "Which is better for AI agents, Persona or Socure RiskOS?"
      },
      {
        "answer": "Both need an API key.",
        "question": "Do Persona and Socure RiskOS need an API key?"
      },
      {
        "answer": "Yes. Persona has a hosted endpoint at https://mcp.withpersona.com and Socure RiskOS at https://mcp.riskos.socure.com/sandbox.",
        "question": "Can an agent call Persona and Socure RiskOS without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Agent ergonomics, 74 against 46",
          "Security \u0026 auth, 73 against 60"
        ],
        "also": null,
        "goodFor": "A company that already runs Persona and wants an agent to create inquiries from templates, read verification and report results, screen against watchlists and work review cases with a permission-limited key.",
        "slug": "persona",
        "watchFor": "Production access needs Persona's approval and a 12-month plan from $250 a month, and API-only integration is limited to Enterprise plans"
      },
      {
        "aheadOn": [
          "Reliability, 75 against 70"
        ],
        "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-persona.json",
        "title": "ComplyCube vs Persona",
        "url": "https://www.anchorterminal.com/compare/complycube-vs-persona"
      },
      {
        "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-persona.json",
        "title": "Didit vs Persona",
        "url": "https://www.anchorterminal.com/compare/didit-vs-persona"
      },
      {
        "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/jumio-vs-persona.json",
        "title": "Jumio vs Persona",
        "url": "https://www.anchorterminal.com/compare/jumio-vs-persona"
      },
      {
        "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-shufti.json",
        "title": "Persona vs Shufti",
        "url": "https://www.anchorterminal.com/compare/persona-vs-shufti"
      },
      {
        "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/persona-vs-trulioo.json",
        "title": "Persona vs Trulioo",
        "url": "https://www.anchorterminal.com/compare/persona-vs-trulioo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/persona-vs-veriff.json",
        "title": "Persona vs Veriff",
        "url": "https://www.anchorterminal.com/compare/persona-vs-veriff"
      },
      {
        "json": "https://www.anchorterminal.com/compare/shufti-vs-socure-riskos.json",
        "title": "Shufti vs Socure RiskOS",
        "url": "https://www.anchorterminal.com/compare/shufti-vs-socure-riskos"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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-persona.json",
        "title": "ComplyAdvantage vs Persona",
        "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-persona"
      },
      {
        "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-persona.json",
        "title": "Middesk vs Persona",
        "url": "https://www.anchorterminal.com/compare/middesk-vs-persona"
      },
      {
        "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,
        "edge": "socure-riskos",
        "key": "reliability",
        "name": "Reliability",
        "persona": 70,
        "socure-riskos": 75,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 1,
        "edge": "persona",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "persona": 85,
        "socure-riskos": 84,
        "weight": 13
      },
      {
        "by": 28,
        "edge": "persona",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "persona": 74,
        "socure-riskos": 46,
        "weight": 13
      },
      {
        "by": 13,
        "edge": "persona",
        "key": "security",
        "name": "Security \u0026 auth",
        "persona": 73,
        "socure-riskos": 60,
        "weight": 14
      },
      {
        "by": 0,
        "edge": "",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "persona": 35,
        "socure-riskos": 35,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 0,
        "edge": "",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "persona": 75,
        "socure-riskos": 75,
        "weight": 7
      },
      {
        "by": 0,
        "edge": "",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "persona": 68,
        "socure-riskos": 68,
        "weight": 7
      }
    ],
    "summary": "Persona scores 69.5 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 3 of 7 scored categories. Socure RiskOS leads on reliability. Both do kyc identity.",
    "verdicts": {
      "persona": "The REST API has a public OpenAPI 3.1 file, llms.txt, API keys with per-resource permissions, idempotency keys on every POST and a 60-day sandbox trial with no card. Production needs a business review and a 12-month plan from $250 a month. The status page lists 11 incidents since 10 July 2026, including 70 minutes of timeouts across all products.",
      "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/persona-vs-socure-riskos",
    "json": "https://www.anchorterminal.com/compare/persona-vs-socure-riskos.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/persona-vs-socure-riskos.md",
    "slim": "https://www.anchorterminal.com/compare/persona-vs-socure-riskos.min.md"
  },
  "markdown": "Persona scores 69.5 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 3 of 7 scored categories. Socure RiskOS leads on reliability. Both do kyc identity.\n\n- Persona: grade B, 69.5/100, rank #176 of 842. Markdown https://www.anchorterminal.com/tools/persona.md · JSON https://www.anchorterminal.com/api/v1/tools/persona.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### Persona (B)\n\nGood for: A company that already runs Persona and wants an agent to create inquiries from templates, read verification and report results, screen against watchlists and work review cases with a permission-limited key.\n\nAhead on:\n- Agent ergonomics, 74 against 46\n- Security \u0026 auth, 73 against 60\n\nWatch for: Production access needs Persona's approval and a 12-month plan from $250 a month, and API-only integration is limited to Enterprise plans\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 70\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 | Persona | Socure RiskOS | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 75 | Socure RiskOS +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 85 | 84 | Persona +1 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 46 | Persona +28 |\n| Security \u0026 auth | 14% (17.5 this run) | 73 | 60 | Persona +13 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 35 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 75 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 68 | 68 | even |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **69.5 · B** | **63.5 · B** | |\n\n## Facts side by side\n\n| Fact | Persona | Socure RiskOS |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Persona Identities, Inc. | Socure Inc. |\n| Hosted endpoint | `https://mcp.withpersona.com` | `https://mcp.riskos.socure.com/sandbox` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Paid | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under Persona's terms of service. The `persona` JavaScript client on npm is MIT | Proprietary service. No service agreement is published, and the OpenAPI file states its licence as Proprietary |\n| Tools exposed | 190 | 9 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-29 | 2026-10-06 |\n| Terms last updated | couldn't be read | no document linked |\n| Privacy policy last updated | couldn't be read | no date given |\n| Customer content may train models | couldn't be read | yes |\n| Terms restrict automated access | couldn't be read |  |\n| Terms restrict benchmarking | couldn't be read |  |\n| Terms or service can change without notice | couldn't be read |  |\n| Arbitration or class-action waiver | couldn't be read |  |\n| Popularity | 570k npm/wk | 35k npm/wk |\n\n## Verdicts\n\n**Persona.** The REST API has a public OpenAPI 3.1 file, llms.txt, API keys with per-resource permissions, idempotency keys on every POST and a 60-day sandbox trial with no card. Production needs a business review and a 12-month plan from $250 a month. The status page lists 11 incidents since 10 July 2026, including 70 minutes of timeouts across all products.\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### Persona\n\n1. Ask for a dedicated key limited to the permissions the task needs. A new key has every standard permission until it's limited\n2. Send `Persona-Version` on every call and an `Idempotency-Key` on every POST. A replayed key returns the first result, including a 500\n3. Treat redact calls as irreversible. They permanently delete personal data and cascade to downstream objects\n4. Stay under 300 requests a minute in production, read `RateLimit-Remaining` and `Quota-Remaining`, and back off on 429 because rejected requests still count\n5. Use `fields` and `include` to cut response size. Through MCP these parameters aren't exposed, and only 14 tools take `filter`\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, Persona or Socure RiskOS?\n\nPersona scores 69.5 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 3 of 7 scored categories. Socure RiskOS leads on reliability.\n\n### Do Persona and Socure RiskOS need an API key?\n\nBoth need an API key.\n\n### Can an agent call Persona and Socure RiskOS without installing anything?\n\nYes. Persona has a hosted endpoint at https://mcp.withpersona.com 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/persona-vs-socure-riskos.json, and with the fewest tokens: https://www.anchorterminal.com/compare/persona-vs-socure-riskos.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"persona\", \"b\": \"socure-riskos\"}`. From a terminal: `anchor compare persona socure-riskos`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/persona.json and https://www.anchorterminal.com/api/v1/tools/socure-riskos.json\n\n## Other comparisons with Persona or Socure RiskOS\n\n- [ComplyCube vs Persona](https://www.anchorterminal.com/compare/complycube-vs-persona.md)\n- [ComplyCube vs Socure RiskOS](https://www.anchorterminal.com/compare/complycube-vs-socure-riskos.md)\n- [Didit vs Persona](https://www.anchorterminal.com/compare/didit-vs-persona.md)\n- [Didit vs Socure RiskOS](https://www.anchorterminal.com/compare/didit-vs-socure-riskos.md)\n- [Jumio vs Persona](https://www.anchorterminal.com/compare/jumio-vs-persona.md)\n- [Jumio vs Socure RiskOS](https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.md)\n- [Persona vs Shufti](https://www.anchorterminal.com/compare/persona-vs-shufti.md)\n- [Persona vs Sumsub](https://www.anchorterminal.com/compare/persona-vs-sumsub.md)\n- [Persona vs Trulioo](https://www.anchorterminal.com/compare/persona-vs-trulioo.md)\n- [Persona vs Veriff](https://www.anchorterminal.com/compare/persona-vs-veriff.md)\n- [Shufti vs Socure RiskOS](https://www.anchorterminal.com/compare/shufti-vs-socure-riskos.md)\n- [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 Persona](https://www.anchorterminal.com/compare/complyadvantage-vs-persona.md)\n- [ComplyAdvantage vs Socure RiskOS](https://www.anchorterminal.com/compare/complyadvantage-vs-socure-riskos.md)\n- [Middesk vs Persona](https://www.anchorterminal.com/compare/middesk-vs-persona.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": "Persona vs Socure RiskOS",
        "url": ""
      }
    ],
    "description": "Persona scores 69.5 (B) on agent readiness against Socure RiskOS's 63.5 (B), and leads in 3 of 7 scored categories. Socure RiskOS leads on reliability. Both do kyc identity. Category scores, facts, verdicts and agent notes side by side.",
    "facts": [
      "Persona B 69.5",
      "Socure RiskOS B 63.5",
      "scores"
    ],
    "h1": "Persona vs Socure RiskOS",
    "image": "https://www.anchorterminal.com/assets/og/compare-persona-vs-socure-riskos.png",
    "path": "/compare/persona-vs-socure-riskos",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Persona vs Socure RiskOS for AI agents, B 69.5 vs B 63.5",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/persona-vs-socure-riskos"
  },
  "tokens": {
    "markdown": 2300,
    "slim": 680
  },
  "version": 1
}
