{ "data": { "a": { "slug": "alloy", "name": "Alloy", "vendor": "First Mile Group, Inc. (Alloy)", "vendorUrl": "https://www.alloy.com", "kind": "http-api", "category": "identity-verification", "summary": "Alloy is an identity and fraud decisioning platform for banks and fintechs. Its API runs onboarding journeys and evaluations that orchestrate identity, business, document and watchlist checks across third-party data vendors, with case management and ongoing monitoring.", "url": "https://www.anchorterminal.com/tools/alloy", "markdownUrl": "https://www.anchorterminal.com/tools/alloy.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/alloy.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/alloy.json", "license": "Proprietary service under Alloy's terms of service. The @alloyidentity/web-sdk capture package is MIT", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@alloyidentity/web-sdk" } ], "auth": "mixed", "authNotes": "Account-level token and secret (older accounts use a workflow token and secret), sent as HTTP basic auth or exchanged at /v1/oauth/bearer for a one-hour Bearer token with client credentials. Up to five active secrets per key, rotated and revoked in the dashboard by users with key permissions. No scopes. The same keys serve sandbox and production, chosen by base URL or the `alloy-sandbox: true` header. Keys come with a customer contract (checked 2026-10-14).", "pricing": "paid", "pricingNotes": "No public prices. www.alloy.com/pricing returns 404 and the site routes buyers to a demo. Production calls invoke third-party data vendors and can incur charges, while sandbox calls don't (https://developer.alloy.com/public/docs/sandbox-vs-production, checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs index, the API reference or the website (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 20569, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://developer.alloy.com/public/docs/introduction", "llmsTxt": "https://developer.alloy.com/public/llms.txt", "capabilities": [ "kyc.identity", "kyc.business", "kyc.screening", "kyc.documents", "kyc.cases" ], "tags": [ "hosted", "enterprise", "sales-led", "api-key", "oauth", "llms-txt", "webhooks", "sandbox", "status-page", "soc2" ], "lastRelease": "2026-10-05", "graded": true, "anchor": { "graded": true, "score": 52.4, "grade": "D", "agentReady": false, "rank": 782, "ranked": true, "rankOf": 1076, "categoryRank": 16, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 52, "maintenance": 72, "payments": 0, "reliability": 59, "schema": 73, "security": 49, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Alloy's public docs cover journeys, evaluations, entities, documents, cases and investigations, with llms.txt, Markdown pages, OpenAPI fragments and rate-limit headers with retry-after. Access is sales-led with no public price or trial, credentials have no scopes, there is no idempotency key or server SDK, and inputs vary by each customer's workflow.", "bestFor": "Banks and fintechs that already run onboarding through Alloy and want an agent to submit journey applications, read decisions and work investigations.", "strengths": [ "Public developer docs with llms.txt (247 entries), Markdown pages and an OpenAPI fragment on each reference page", "Rate-limit headers and `retry-after` on 429, with a written guide to which codes to retry", "One API orchestrates identity, business, document and watchlist checks across many data vendors", "Up to five active secrets per key, OAuth client credentials and an IP allowlist", "Status page with separate Production API, Sandbox API, Webhooks and third-party components" ], "weaknesses": [ "No public prices, trial or self-serve sign-up. Access starts with a demo request", "Rate limits vary by account and endpoint with no published numbers", "No idempotency key and no server-side SDK", "Evaluation inputs and outputs depend on each customer's workflow, so the contract is loosely typed", "Sandbox and Production are request modes over one data store, so test and live records can collide" ], "agentNotes": [ "Get the account's base URL from the customer. Defaults are api.alloy.co and sandbox.alloy.co, and some accounts have their own hosts", "Use unique, prefixed external IDs in sandbox. Sandbox and Production share one data store", "Read `alloy-ratelimit-remaining`, and on 429 or 5xx wait for `retry-after` with exponential backoff and jitter", "Expect `running` after about 25 seconds on journey applications and wait for the webhook instead of resubmitting", "Send the workflow header with account-level keys, since inputs depend on the workflow configured" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 52.4 } ], "editorialScores": { "ergonomics": 52, "maintenance": 72, "payments": 0, "reliability": 59, "schema": 73, "security": 49, "transparency": 38 }, "provenanceScore": 86 }, "connect": { "http": "curl -X POST https://sandbox.alloy.co/v1/oauth/bearer \\\n -H \"Content-Type: application/json\" \\\n -H \"Authorization: Basic \u003cbasic_token\u003e\" \\\n -d '{\n \"grant_type\": \"client_credentials\"\n }'" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/alloy" }, "area": "domain-data", "provenance": { "legalEntity": "First Mile Group, Inc.", "domain": "alloy.com", "domainRegistered": "1999-02-25", "endpointOnVendorDomain": true, "terms": "https://www.alloy.com/tos", "privacy": "https://www.alloy.com/privacy-policy", "statusPage": "https://status.alloy.com", "changelog": "https://www.alloy.com/product-updates", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The privacy policy (29 August 2025) names First Mile Group, Inc. d/b/a/ Alloy.", "The default API hosts are on alloy.co (api.alloy.co, sandbox.alloy.co), and account-specific hosts on alloy.com. status.alloy.co redirects to status.alloy.com.", "www.alloy.com/.well-known/security.txt and alloy.co/.well-known/security.txt return 404.", "RDAP for alloy.com gives a registration date of 1999-02-25, before Alloy was founded in 2015." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/alloy.json", "live": { "slug": "alloy", "vendorStatus": { "page": "https://status.alloy.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:38:51.209484803Z" }, "mcpTools": { "url": "https://api.alloy.cx/mcp", "checkedAt": "2026-10-02T22:09:59.902886223Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-02T22:09:59.902886223Z" }, "updatedAt": "2026-10-14T09:38:51.209484803Z" } }, "answer": "Jumio scores 55 (C) on agent readiness against Alloy's 52.4 (D), and leads in 3 of 7 scored categories. Alloy leads on agent ergonomics.", "b": { "slug": "jumio", "name": "Jumio", "vendor": "Jumio Corporation", "vendorUrl": "https://www.jumio.com", "kind": "http-api", "category": "identity-verification", "summary": "Identity verification service from Jumio Corporation in Sunnyvale. It checks identity documents and selfies with liveness, screens against sanctions and PEP lists, and runs government database checks. Transactions are started and read through regional REST APIs with OAuth2.", "url": "https://www.anchorterminal.com/tools/jumio", "markdownUrl": "https://www.anchorterminal.com/tools/jumio.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/jumio.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/jumio.json", "repo": "https://github.com/Jumio/mobile-sdk-android", "license": "Proprietary service. No public service agreement was found. The @jumio/websdk npm package is marked UNLICENSED", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@jumio/websdk" }, { "registry": "npm", "name": "react-native-jumio-mobilesdk" } ], "auth": "oauth", "authNotes": "Sales approval. A Jumio account manager activates OAuth2 for the tenant and supplies the workflow keys. An admin then generates client ID and secret pairs in the Jumio Portal, each limited to initiating transactions, to retrieving and deleting them, or both, and each can be deactivated. The pair is sent as Basic credentials to the regional token URL with `grant_type=client_credentials`, and the bearer token lasts 60 minutes. Basic authentication on the REST APIs themselves is marked deprecated. Account creation also returns per-transaction tokens for uploads and the capture SDKs.", "pricing": "paid", "pricingNotes": "No public prices. www.jumio.com/pricing/ returns 404 and the site's Get Started button opens a sales enquiry form. No free tier, trial or self-serve signup was found. The mock service for synthetic test transactions needs a dedicated tenant that Jumio Support or the account manager sets up (checked 2026-10-08).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms-full.txt, the five OpenAPI files or the Jumio website (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 72, "npmWeekly": 2122, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://documentation.jumio.ai", "llmsTxt": "https://documentation.jumio.ai/llms.txt", "openapi": "https://documentation.jumio.ai/redocusaurus/account.yaml", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening" ], "tags": [ "hosted", "enterprise", "oauth", "openapi", "llms-txt", "callbacks", "sales-led", "status-page", "soc2", "iso27001", "java", "dotnet" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 55, "grade": "C", "agentReady": false, "rank": 713, "ranked": true, "rankOf": 1076, "categoryRank": 14, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 45, "maintenance": 75, "payments": 0, "reliability": 65, "schema": 73, "security": 63, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Five OpenAPI 3.0 files, an llms.txt index and OAuth2 clients limited to initiating or to retrieving and deleting make the API readable and containable. Access starts with an account manager, with no public price, trial or service agreement, and the status page shows four processing degradations and a 35-minute Singapore outage between 14 August and 2 October 2026.", "bestFor": "An enterprise with a Jumio contract that wants document, selfie and liveness checks, watchlist screening and Latin American, Thai and Australian database checks behind OpenAPI-described endpoints.", "strengths": [ "Five downloadable OpenAPI 3.0 files covering 25 operations, plus llms.txt and a 2.2 MB llms-full.txt of the docs in Markdown", "OAuth2 client credentials with 60-minute bearer tokens. Each client is limited to initiate, to retrieve and delete, or both, and can be deactivated", "Rate limits are published per tenant. Token requests 10 a second, new transactions 1 a second, retrievals 15 a second", "Statuspage at monitor.jumio.com by data centre, and an unauthenticated health endpoint per region that answers UP, DEGRADED or DOWN", "SOC 2, ISO 27001 and PCI DSS 4.0.1 listed on the Trust Centre, and a vulnerability disclosure programme at vdp.jumio.com" ], "weaknesses": [ "No public price, free tier or trial. OAuth2 and workflow keys are activated by a Jumio account manager", "No service agreement or DPA is published. The public terms of use cover end users in the United States", "Four processing degradations and a 35-minute Singapore outage on the status page between 14 August and 2 October 2026", "No idempotency key. A repeated POST or PUT on accounts starts another transaction", "GET /api/v1/workflow-executions takes no paging or filter parameters, and the specs document only 401, 403 and 404 errors", "Retention periods and the sub-processor list are available on request only, and security.txt returns 404" ], "agentNotes": [ "Use the host for the tenant's region (amer-1, emea-1 or apac-1). Tokens come from auth.\u003cregion\u003e.jumio.ai/oauth2/token with the client ID and secret as Basic credentials", "Reuse the bearer token for its 60 minutes. Token requests are limited to 10 a second and new transactions to 1 a second per tenant", "Send a User-Agent header on every call. The Account API marks it required", "Don't blindly retry POST /api/v1/accounts. Each call creates an account and a transaction, and no idempotency key exists", "Wait for the callback or poll the status endpoint until PROCESSED before retrieving. Jumio's retry schedule starts at 40 seconds and stops after 940" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55 } ], "editorialScores": { "ergonomics": 45, "maintenance": 75, "payments": 0, "reliability": 65, "schema": 73, "security": 63, "transparency": 41 }, "provenanceScore": 78 }, "connect": { "http": "curl --location 'https://auth.amer-1.jumio.ai/oauth2/token' \\\n -u CLIENT_ID:CLIENT_SECRET \\\n --header 'Accept: application/json' \\\n --data-urlencode 'grant_type=client_credentials'" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/jumio" }, "area": "domain-data", "provenance": { "legalEntity": "Jumio Corporation", "domain": "jumio.com", "domainRegistered": "2004-03-30", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://www.jumio.com/privacy-center/privacy-notices/online-services-notice/", "statusPage": "https://monitor.jumio.com", "changelog": "https://documentation.jumio.ai/docs/developer-resources/SDKs/mobile-sdk/mobile-sdk-android-master/docs/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Online Services Privacy Notice (last updated 4 August 2026) names Jumio Corporation, 100 Mathilda Place, Suite 100, Sunnyvale, CA 94086, with Jumio Software Development GmbH in Linz as EU representative.", "No terms field. Jumio publishes no service agreement or API terms for customers. www.jumio.com/terms-of-use/ (last updated 18 June 2026) is addressed to end users in the United States, so it isn't recorded as the governing document.", "The APIs answer on jumio.ai hosts (auth, account, api, retrieval, kyx and status under amer-1, emea-1 and apac-1), a second domain used throughout Jumio's own documentation at documentation.jumio.ai.", "www.jumio.com/.well-known/security.txt and /security.txt return 404. Reports go to the vulnerability disclosure programme at https://vdp.jumio.com, which pays nothing.", "The changelog linked is the Android SDK's. No changelog for the REST APIs was found.", "RDAP for jumio.com gives a registration date of 2004-03-30." ], "score": 78 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/jumio.json", "live": { "slug": "jumio", "vendorStatus": { "page": "https://monitor.jumio.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:17.680456737Z" }, "versions": [ { "registry": "github", "name": "Jumio/mobile-sdk-android", "version": "v4.19.1", "released": "2026-09-28", "seenAt": "2026-10-13T23:03:31.8438655Z" }, { "registry": "npm", "name": "@jumio/websdk", "version": "0.6.2", "seenAt": "2026-10-13T23:03:29.658957915Z" }, { "registry": "npm", "name": "react-native-jumio-mobilesdk", "version": "4.11.0", "seenAt": "2026-10-13T23:03:30.077827417Z" } ], "githubStars": 72, "npmWeekly": 2384, "securityTxt": { "url": "https://jumio.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-13T15:45:23.408019204Z" }, "llmsTxt": { "url": "https://documentation.jumio.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-13T14:11:48.597122921Z" }, "domain": { "domain": "jumio.com", "registered": "2004-03-30", "source": "https://rdap.verisign.com/com/v1/domain/jumio.com", "checkedAt": "2026-10-11T13:20:49.723829226Z" }, "pages": [ { "url": "https://documentation.jumio.ai/docs/developer-resources/SDKs/mobile-sdk/mobile-sdk-android-master/docs/changelog", "kind": "changelog", "status": 304, "checkedAt": "2026-10-13T20:16:24.688432791Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4e0b13492ecb" }, { "url": "https://www.jumio.com/privacy-center/privacy-notices/online-services-notice/", "kind": "privacy", "status": 304, "checkedAt": "2026-10-13T20:29:11.663584583Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "47ddc34e8761" } ], "updatedAt": "2026-10-14T09:39:17.680456737Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "First Mile Group, Inc. (Alloy)", "b": "Jumio Corporation", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Alloy's terms of service. The @alloyidentity/web-sdk capture package is MIT", "b": "Proprietary service. No public service agreement was found. The @jumio/websdk npm package is marked UNLICENSED", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-05", "b": "2026-09-28", "name": "Last release" }, { "a": "2026-03-12", "b": "no document linked", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-08-04", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "name": "Customer content may train models" }, { "a": "yes", "b": "", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "21k npm/wk", "b": "72 stars, 2.1k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Jumio scores 55 (C) on agent readiness against Alloy's 52.4 (D), and leads in 3 of 7 scored categories. Alloy leads on agent ergonomics.", "question": "Which is better for AI agents, Alloy or Jumio?" }, { "answer": "Alloy takes an API key or an OAuth sign-in. Jumio uses an OAuth sign-in.", "question": "Do Alloy and Jumio need an API key?" }, { "answer": "No hosted endpoint is listed for Alloy. No hosted endpoint is listed for Jumio.", "question": "Can an agent call Alloy and Jumio without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 52 against 45" ], "also": null, "goodFor": "Banks and fintechs that already run onboarding through Alloy and want an agent to submit journey applications, read decisions and work investigations.", "slug": "alloy", "watchFor": "No public prices, trial or self-serve sign-up. Access starts with a demo request" }, { "aheadOn": [ "Reliability, 65 against 59", "Security \u0026 auth, 63 against 49" ], "also": null, "goodFor": "An enterprise with a Jumio contract that wants document, selfie and liveness checks, watchlist screening and Latin American, Thai and Australian database checks behind OpenAPI-described endpoints.", "slug": "jumio", "watchFor": "No public price, free tier or trial. OAuth2 and workflow keys are activated by a Jumio account manager" } ], "job": { "capability": "kyc.identity", "name": "Identity verification" }, "others": [ { "json": "https://www.anchorterminal.com/compare/alloy-vs-complycube.json", "title": "Alloy vs ComplyCube", "url": "https://www.anchorterminal.com/compare/alloy-vs-complycube" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-didit.json", "title": "Alloy vs Didit", "url": "https://www.anchorterminal.com/compare/alloy-vs-didit" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification.json", "title": "Alloy vs Entrust Identity Verification (formerly Onfido)", "url": "https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-middesk.json", "title": "Alloy vs Middesk", "url": "https://www.anchorterminal.com/compare/alloy-vs-middesk" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-persona.json", "title": "Alloy vs Persona", "url": "https://www.anchorterminal.com/compare/alloy-vs-persona" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-plaid-identity-verification.json", "title": "Alloy vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/alloy-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-shufti.json", "title": "Alloy vs Shufti", "url": "https://www.anchorterminal.com/compare/alloy-vs-shufti" }, { "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/alloy-vs-sumsub.json", "title": "Alloy vs Sumsub", "url": "https://www.anchorterminal.com/compare/alloy-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-trulioo.json", "title": "Alloy vs Trulioo", "url": "https://www.anchorterminal.com/compare/alloy-vs-trulioo" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-veriff.json", "title": "Alloy vs Veriff", "url": "https://www.anchorterminal.com/compare/alloy-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-vouched.json", "title": "Alloy vs Vouched", "url": "https://www.anchorterminal.com/compare/alloy-vs-vouched" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-jumio.json", "title": "ComplyCube vs Jumio", "url": "https://www.anchorterminal.com/compare/complycube-vs-jumio" }, { "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/entrust-identity-verification-vs-jumio.json", "title": "Entrust Identity Verification (formerly Onfido) vs Jumio", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-middesk.json", "title": "Jumio vs Middesk", "url": "https://www.anchorterminal.com/compare/jumio-vs-middesk" }, { "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-plaid-identity-verification.json", "title": "Jumio vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/jumio-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-shufti.json", "title": "Jumio vs Shufti", "url": "https://www.anchorterminal.com/compare/jumio-vs-shufti" }, { "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/jumio-vs-sumsub.json", "title": "Jumio vs Sumsub", "url": "https://www.anchorterminal.com/compare/jumio-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-trulioo.json", "title": "Jumio vs Trulioo", "url": "https://www.anchorterminal.com/compare/jumio-vs-trulioo" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-veriff.json", "title": "Jumio vs Veriff", "url": "https://www.anchorterminal.com/compare/jumio-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-vouched.json", "title": "Jumio vs Vouched", "url": "https://www.anchorterminal.com/compare/jumio-vs-vouched" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-complyadvantage.json", "title": "Alloy vs ComplyAdvantage", "url": "https://www.anchorterminal.com/compare/alloy-vs-complyadvantage" }, { "json": "https://www.anchorterminal.com/compare/complyadvantage-vs-jumio.json", "title": "ComplyAdvantage vs Jumio", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-jumio" } ], "scores": [ { "alloy": 59, "by": 6, "edge": "jumio", "jumio": 65, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "alloy": 73, "by": 0, "edge": "", "jumio": 73, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "alloy": 52, "by": 7, "edge": "alloy", "jumio": 45, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "alloy": 49, "by": 14, "edge": "jumio", "jumio": 63, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "alloy": 0, "by": 0, "edge": "", "jumio": 0, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "alloy": 72, "by": 3, "edge": "jumio", "jumio": 75, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "alloy": 62, "by": 2, "edge": "alloy", "jumio": 60, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Jumio scores 55 (C) on agent readiness against Alloy's 52.4 (D), and leads in 3 of 7 scored categories. Alloy leads on agent ergonomics. Both do identity verification.", "verdicts": { "alloy": "Alloy's public docs cover journeys, evaluations, entities, documents, cases and investigations, with llms.txt, Markdown pages, OpenAPI fragments and rate-limit headers with retry-after. Access is sales-led with no public price or trial, credentials have no scopes, there is no idempotency key or server SDK, and inputs vary by each customer's workflow.", "jumio": "Five OpenAPI 3.0 files, an llms.txt index and OAuth2 clients limited to initiating or to retrieving and deleting make the API readable and containable. Access starts with an account manager, with no public price, trial or service agreement, and the status page shows four processing degradations and a 35-minute Singapore outage between 14 August and 2 October 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/alloy-vs-jumio", "json": "https://www.anchorterminal.com/compare/alloy-vs-jumio.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/alloy-vs-jumio.md", "slim": "https://www.anchorterminal.com/compare/alloy-vs-jumio.min.md" }, "markdown": "Jumio scores 55 (C) on agent readiness against Alloy's 52.4 (D), and leads in 3 of 7 scored categories. Alloy leads on agent ergonomics. Both do identity verification.\n\n- Alloy: grade D, 52.4/100, rank #782 of 1076. Markdown https://www.anchorterminal.com/tools/alloy.md · JSON https://www.anchorterminal.com/api/v1/tools/alloy.json\n- Jumio: grade C, 55/100, rank #713 of 1076. Markdown https://www.anchorterminal.com/tools/jumio.md · JSON https://www.anchorterminal.com/api/v1/tools/jumio.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### Alloy (D)\n\nGood for: Banks and fintechs that already run onboarding through Alloy and want an agent to submit journey applications, read decisions and work investigations.\n\nAhead on:\n- Agent ergonomics, 52 against 45\n\nWatch for: No public prices, trial or self-serve sign-up. Access starts with a demo request\n\n### Jumio (C)\n\nGood for: An enterprise with a Jumio contract that wants document, selfie and liveness checks, watchlist screening and Latin American, Thai and Australian database checks behind OpenAPI-described endpoints.\n\nAhead on:\n- Reliability, 65 against 59\n- Security \u0026 auth, 63 against 49\n\nWatch for: No public price, free tier or trial. OAuth2 and workflow keys are activated by a Jumio account manager\n\n\n## Score by category\n\n| Category | Weight | Alloy | Jumio | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 59 | 65 | Jumio +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 73 | 73 | even |\n| Agent ergonomics | 13% (16.2 this run) | 52 | 45 | Alloy +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 49 | 63 | Jumio +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 0 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 72 | 75 | Jumio +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 62 | 60 | Alloy +2 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **52.4 · D** | **55 · C** | |\n\n## Facts side by side\n\n| Fact | Alloy | Jumio |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | First Mile Group, Inc. (Alloy) | Jumio Corporation |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Alloy's terms of service. The @alloyidentity/web-sdk capture package is MIT | Proprietary service. No public service agreement was found. The @jumio/websdk npm package is marked UNLICENSED |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-05 | 2026-09-28 |\n| Terms last updated | 2026-03-12 | no document linked |\n| Privacy policy last updated | no date given | 2026-08-04 |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | yes | |\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 | yes | |\n| Popularity | 21k npm/wk | 72 stars, 2.1k npm/wk |\n\n## Verdicts\n\n**Alloy.** Alloy's public docs cover journeys, evaluations, entities, documents, cases and investigations, with llms.txt, Markdown pages, OpenAPI fragments and rate-limit headers with retry-after. Access is sales-led with no public price or trial, credentials have no scopes, there is no idempotency key or server SDK, and inputs vary by each customer's workflow.\n\n**Jumio.** Five OpenAPI 3.0 files, an llms.txt index and OAuth2 clients limited to initiating or to retrieving and deleting make the API readable and containable. Access starts with an account manager, with no public price, trial or service agreement, and the status page shows four processing degradations and a 35-minute Singapore outage between 14 August and 2 October 2026.\n\n## Before you call either\n\n### Alloy\n\n1. Get the account's base URL from the customer. Defaults are api.alloy.co and sandbox.alloy.co, and some accounts have their own hosts\n2. Use unique, prefixed external IDs in sandbox. Sandbox and Production share one data store\n3. Read `alloy-ratelimit-remaining`, and on 429 or 5xx wait for `retry-after` with exponential backoff and jitter\n4. Expect `running` after about 25 seconds on journey applications and wait for the webhook instead of resubmitting\n5. Send the workflow header with account-level keys, since inputs depend on the workflow configured\n\n### Jumio\n\n1. Use the host for the tenant's region (amer-1, emea-1 or apac-1). Tokens come from auth.\u003cregion\u003e.jumio.ai/oauth2/token with the client ID and secret as Basic credentials\n2. Reuse the bearer token for its 60 minutes. Token requests are limited to 10 a second and new transactions to 1 a second per tenant\n3. Send a User-Agent header on every call. The Account API marks it required\n4. Don't blindly retry POST /api/v1/accounts. Each call creates an account and a transaction, and no idempotency key exists\n5. Wait for the callback or poll the status endpoint until PROCESSED before retrieving. Jumio's retry schedule starts at 40 seconds and stops after 940\n\n## Questions\n\n### Which is better for AI agents, Alloy or Jumio?\n\nJumio scores 55 (C) on agent readiness against Alloy's 52.4 (D), and leads in 3 of 7 scored categories. Alloy leads on agent ergonomics.\n\n### Do Alloy and Jumio need an API key?\n\nAlloy takes an API key or an OAuth sign-in. Jumio uses an OAuth sign-in.\n\n### Can an agent call Alloy and Jumio without installing anything?\n\nNo hosted endpoint is listed for Alloy. No hosted endpoint is listed for Jumio.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/alloy-vs-jumio.json, and with the fewest tokens: https://www.anchorterminal.com/compare/alloy-vs-jumio.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"alloy\", \"b\": \"jumio\"}`. From a terminal: `anchor compare alloy jumio`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/alloy.json and https://www.anchorterminal.com/api/v1/tools/jumio.json\n\n## Other comparisons with Alloy or Jumio\n\n- [Alloy vs ComplyCube](https://www.anchorterminal.com/compare/alloy-vs-complycube.md)\n- [Alloy vs Didit](https://www.anchorterminal.com/compare/alloy-vs-didit.md)\n- [Alloy vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification.md)\n- [Alloy vs Middesk](https://www.anchorterminal.com/compare/alloy-vs-middesk.md)\n- [Alloy vs Persona](https://www.anchorterminal.com/compare/alloy-vs-persona.md)\n- [Alloy vs Plaid Identity Verification](https://www.anchorterminal.com/compare/alloy-vs-plaid-identity-verification.md)\n- [Alloy vs Shufti](https://www.anchorterminal.com/compare/alloy-vs-shufti.md)\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- [Alloy vs Sumsub](https://www.anchorterminal.com/compare/alloy-vs-sumsub.md)\n- [Alloy vs Trulioo](https://www.anchorterminal.com/compare/alloy-vs-trulioo.md)\n- [Alloy vs Veriff](https://www.anchorterminal.com/compare/alloy-vs-veriff.md)\n- [Alloy vs Vouched](https://www.anchorterminal.com/compare/alloy-vs-vouched.md)\n- [ComplyCube vs Jumio](https://www.anchorterminal.com/compare/complycube-vs-jumio.md)\n- [Didit vs Jumio](https://www.anchorterminal.com/compare/didit-vs-jumio.md)\n- [Entrust Identity Verification (formerly Onfido) vs Jumio](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio.md)\n- [Jumio vs Middesk](https://www.anchorterminal.com/compare/jumio-vs-middesk.md)\n- [Jumio vs Persona](https://www.anchorterminal.com/compare/jumio-vs-persona.md)\n- [Jumio vs Plaid Identity Verification](https://www.anchorterminal.com/compare/jumio-vs-plaid-identity-verification.md)\n- [Jumio vs Shufti](https://www.anchorterminal.com/compare/jumio-vs-shufti.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- [Jumio vs Sumsub](https://www.anchorterminal.com/compare/jumio-vs-sumsub.md)\n- [Jumio vs Trulioo](https://www.anchorterminal.com/compare/jumio-vs-trulioo.md)\n- [Jumio vs Veriff](https://www.anchorterminal.com/compare/jumio-vs-veriff.md)\n- [Jumio vs Vouched](https://www.anchorterminal.com/compare/jumio-vs-vouched.md)\n- [Alloy vs ComplyAdvantage](https://www.anchorterminal.com/compare/alloy-vs-complyadvantage.md)\n- [ComplyAdvantage vs Jumio](https://www.anchorterminal.com/compare/complyadvantage-vs-jumio.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": "Alloy vs Jumio", "url": "" } ], "description": "Jumio scores 55 (C) to Alloy's 52.4 (D) for identity verification. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Alloy D 52.4", "Jumio C 55", "scores" ], "h1": "Alloy vs Jumio", "image": "https://www.anchorterminal.com/assets/og/compare-alloy-vs-jumio.png", "path": "/compare/alloy-vs-jumio", "published": "2026-10-01", "section": "tools", "title": "Alloy vs Jumio for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/alloy-vs-jumio" }, "tokens": { "markdown": 2400, "slim": 630 }, "version": 1 }