Jumio

# Fix list: Jumio

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/jumio, the October 2026 research run, assessed 8 October 2026. Grade C, 55 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Jumio: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Payments & pricing, 0 out of 100, up to 12.5 more on the total

Why it scored 0: No x402, MPP or L402 (0). No price is published. The pricing URL returns 404 and the site sends buyers to a sales form (0). No free tier or trial was found, and the mock service needs a tenant set up by Jumio (0). OAuth2 is activated by an account manager, so no agent can onboard alone (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 2. Agent ergonomics, 45 out of 100, up to 8.9 more on the total

Why it scored 45: No field selection. The workflow details response is large, though separate status, steps and rules endpoints return smaller ones (12). GET /api/v1/workflow-executions returns the last processed transactions and its spec has no paging or filter parameters (5). The 429 body has title, status and detail, and capability decisions carry documented labels. HTTP errors in the specs stop at 401, 403 and 404 (12). No idempotency key, and POST or PUT on accounts starts a new transaction each time. Reads are safe to repeat (5). An account request needs only `customerInternalReference` and a workflow key, plus a required User-Agent header. Official server libraries exist for Java Spring Boot and .NET, the first from Jumio's own Maven repository and the second as a download (11).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 3. Reliability, 65 out of 100, up to 7 more on the total

Why it scored 65: Graded on the Platform REST APIs with the hosted lines. Statuspage at monitor.jumio.com with 48 components by data centre, plus an unauthenticated health endpoint per region (20). In the 90 days to 8 October 2026 there were four degradations of processing, on 14 to 15 August (about 20 hours, mainly the EU), 30 September and twice on 1 October (the second ran 13.5 hours), each causing delays and unexpected MISSING_MANDATORY_DATAPOINTS rejections, and a 35-minute outage of the Singapore data centre on 2 September that Jumio marked critical. No core API was down for an hour, so we scored between the minor and major lines (12). Limits are published per tenant, 10 token requests, 1 new transaction and 15 retrievals a second (15). A 429 with a JSON body is documented, with a retrieval retry schedule from 40 to 940 seconds and general backoff advice. No Retry-After header or idempotency key was found (8). No SLA found in public pages (0). GA (10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 4. Security & auth, 63 out of 100, up to 6.5 more on the total

Why it scored 63: OAuth2 client credentials with 60-minute bearer tokens. Each client is limited to initiate, to retrieve and delete, or both, and can be deactivated. The Retrieval spec names a `transactions/retrieval` scope. No secret expiry or rotation procedure was found beyond generating a new pair (26). An initiate-only client can't read results, but reading and deleting share one permission and no confirmation step exists for DELETE (10). Responses carry text extracted from documents and watchlist results, with no injection guidance found (3). The Portal Audit Log records user actions with email, IP address and result since 1 September 2023. It isn't stated to cover API calls (9). SOC 2, ISO 27001 and PCI DSS 4.0.1 on the Trust Centre and an unpaid vulnerability disclosure programme. No bug bounty, and security.txt returns 404 (15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 5. Schema & documentation, 73 out of 100, up to 4.4 more on the total

Why it scored 73: Five OpenAPI 3.0 files download from the reference pages, covering 25 operations across Accounts, Credentials, Retrieval, Aggregate and Public Status (25). llms.txt and a 2.2 MB llms-full.txt in Markdown, and robots.txt lists both (10). Operations carry a summary and a link to a guide, and the guides explain order of use. Few say when not to use an endpoint (12). String lengths, patterns, UUID formats and 57 enums in the Retrieval spec, but `overrideSettings` is a free-form object and the mock service packs JSON into `customerInternalReference` (11). Request and response examples throughout, and decision labels in tables. The specs list only 401, 403 and 404, with 400 and 429 described in prose (9). Paths carry /api/v1 and the specs are versioned 1.0.0, 1.0.2 or v0. No changelog for the REST APIs was found, only undated SDK changelogs (6).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 6. Transparency & trust, 60 out of 100, up to 3.5 more on the total

Made of editorial 41, provenance 78.

Why it scored 60: Closed service with no public service agreement or API terms. The terms of use page covers end users in the United States (8). The Online Services Privacy Notice, updated 4 August 2026, says Jumio is the controller in general and the processor for certain customers, uses data to improve its services through machine learning, and destroys biometric data within three years. Other retention periods are available on request, and no public DPA was found. The docs say tenant retention is set through support (15). The SDK maintenance policy gives 9 months of support, 24 months to end of life and 3 months' notice of an earlier end. Basic authentication is marked deprecated with no date, and no policy for the REST APIs was found (12). Three data centre regions are named, and the list of third parties is available on request only (6).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Terms of service: not found (0 of 10)
- Privacy policy: read, states 8 of the 8 things a reader expects, and has 1 clause that costs points (8 of 10)
- security.txt: not found (0 of 10)

## 7. Maintenance & community, 75 out of 100, up to 2.2 more on the total

Why it scored 75: Android SDK 4.19.1 was tagged on 28 September 2026 (30). Releases in the last 90 days include Android 4.18.0 on 10 July, 4.19.0 on 17 September and 4.19.1, iOS 4.19.0 on 18 September, and @jumio/websdk 0.6.1 and 0.6.2 on 21 July and 19 August (20). Closed service with public SDK changelogs and a support portal at support.jumio.com. No API changelog or public developer forum was found, and GitHub issue handling wasn't read (8). Capture SDKs are current. The Java client is 1.1.0 from a private Maven repository with no date, and the .NET library is a download (12). The public repositories hold docs and samples, with no CI visible, and @jumio/websdk is still 0.x (5).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- No service agreement, API terms or DPA is published, so `provenance.terms` is left out. Whether customers receive an SLA under contract wasn't established
- No price, trial or free tier was found on public pages. We didn't contact sales
- unchecked: support.jumio.com, which the docs give as the support channel, and whether it needs a login
- unchecked: GitHub issue counts and reply times for the Jumio repositories (the GitHub API refused us for its rate limit)
- unchecked: the documents behind trust.jumio.com, which lists SOC 2, ISO 27001 and PCI DSS 4.0.1 as compliant without dates in the page we read
- Whether a 429 carries Retry-After, and whether GET /api/v1/workflow-executions accepts paging or filters that the spec omits
- Whether callbacks are signed. Only source IP addresses and hostnames per region were found
- Whether the Portal Audit Log records API calls made with OAuth2 clients
- Prepared data accepts business fields and `kybCapabilities`, but no business verification workflow is documented, so kyc.business isn't listed
- The Java client's release date wasn't found. It installs from repo.api.jumio.ai, not Maven Central
- githubStars is Jumio/mobile-sdk-android and npmWeekly is @jumio/websdk (28 September to 4 October 2026), both capture SDKs, since no public server-side package exists

## 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

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Use the host for the tenant's region (amer-1, emea-1 or apac-1). Tokens come from auth.<region>.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

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.