Unit vs Synctera

Account opening

1. developerOpen a real, insured deposit account through the API — application to active account fully programmatic, with sandbox parity so the flow is tested before launch

   weight 3 · round to Synctera
   Unit~partialprobed4/10

   Unit's docs confirm programmatic creation of deposit accounts (including FBO structures) via API, which is the core capability, but the evidence pack contains no mention of a sandbox/test environment for parity testing, no explicit FDIC-insurance language, and probes show API reference/OpenAPI endpoints returning 404s, undermining confidence in full self-serve API documentation. missing for 10: sandbox environment documentation, explicit insured-deposit (FDIC) claims, working API reference/OpenAPI spec.

   • [claimed-docs] “Create deposit accounts and wallet accounts held in FBO structures. Support use cases including operating accounts, customer wallets, sub-ac…”
   • [claimed-docs] “Companies can work with one or multiple Unit bank partners through the same infrastructure.”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.unit.co/docs/api/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.unit.co/openapi.json, https://www.unit.co/swagger.json, https://www.unit.co/api/openapi.…”

   proof ↗⚑ flag

   Synctera~partialprobed7/10

   Docs show a full programmatic path — customer creation (personal/business), KYC/watchlist verification, account creation, cards, transfers/wires, webhooks — and confirm sandbox API keys work immediately with the same API surface as production (synctera-docs-1/2/3/9/10/14, synctera-probe-1/2). However, the pack never explicitly states the accounts are FDIC-insured deposit accounts or confirms sandbox truly mirrors bank-approval/production parity beyond key issuance, so the specific 'insured deposit account' and full sandbox-to-prod fidelity claims are not directly evidenced. Missing for 10: explicit FDIC/insurance confirmation, and independent/hands-on confirmation of sandbox-to-production parity for the full account-opening flow.

   • [claimed-docs] “Creates and manages records for personal customers”
   • [claimed-docs] “Creates and manages records for business customers”
   • [claimed-docs] “Creates and manages customer accounts”
   • [claimed-docs] “Synctera's verification solution runs identity and watchlist checks for personal and business customers and records the results as `verifica…”
   • [claimed-docs] “Once an API key is issued in Sandbox, you can immediately start calling the APIs below.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.synctera.com/llms.txt # Synctera - [v2 (658 pages)](https://docs.synctera.com/_llms/v2.md): Docume…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.synctera.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Synctera connects you with the banks in our network that best align with your product vision and timeline.”

   proof ↗⚑ flag

Fbo structures

1. finance leadThe account structure is transparent — whether funds sit in FBO pools or individual accounts, where FDIC insurance actually attaches, and who can see the ledger, all documented plainly

   weight 3 · round to Unit
   Unit~partialclaimed4/10

   Unit's docs mention FBO deposit account structures and dashboard/API visibility into accounts and compliance data, but there's no plain documentation of where FDIC insurance actually attaches (pass-through vs individual), no explicit ledger access-control model, and no clear breakdown of pooled vs individual account structures for finance leads. missing for 10: explicit FDIC insurance attachment documentation, ledger visibility/permission model, clear FBO-vs-individual account structural disclosure.

   • [claimed-docs] “Create deposit accounts and wallet accounts held in FBO structures. Support use cases including operating accounts, customer wallets, sub-ac…”
   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”
   • [claimed-docs] “Companies can work with one or multiple Unit bank partners through the same infrastructure.”

   proof ↗⚑ flag

   Synctera—none0/10

   While Synctera's docs cover customer account creation, cards, transfers, and bank-partner collaboration tools, none of the evidence addresses FBO pooled vs individual account structuring, where FDIC insurance actually attaches, or ledger visibility/access-control documentation — the specific transparency concerns a finance lead would need. This is a fair axis for a BaaS/bank-partner platform, but no supporting evidence exists.

   • [claimed-docs] “Creates and manages customer accounts”
   • [claimed-docs] “Manage all operational workflows in a centralized platform with a set of tools that provide complete data visibility and seamless collaborat…”
   • [claimed-docs] “Synctera connects you with the banks in our network that best align with your product vision and timeline.”

   proof ↗⚑ flag

Virtual accounts

1. developerIssue unique account and routing numbers at scale — virtual accounts for reconciliation, per-customer collection accounts, and sub-accounts under a master structure

   weight 2 · round to Unit
   Unit~partialprobed5/10

   Unit's docs confirm deposit/wallet accounts, sub-accounts, and multi-party fund flows suitable for per-customer collection and reconciliation use cases, but there is no explicit mention of programmatic bulk issuance of unique account/routing numbers at scale or dedicated virtual-account reconciliation features. Missing for 10: explicit API documentation on bulk/at-scale account+routing number issuance, virtual account numbering scheme details, and independent/hands-on confirmation of scale performance.

   • [claimed-docs] “Create deposit accounts and wallet accounts held in FBO structures. Support use cases including operating accounts, customer wallets, sub-ac…”
   • [claimed-docs] “Companies can work with one or multiple Unit bank partners through the same infrastructure.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.unit.co/llms.txt # Unit > **Unit is a financial infrastructure platform for technology companies th…”

   proof ↗⚑ flag

   Synctera~partialclaimed3/10

   Synctera's docs confirm it creates and manages customer accounts and supports internal transfers, which is consistent with account-provisioning capability for a BaaS platform, but there is no explicit evidence of issuing unique routing numbers, virtual accounts for reconciliation, per-customer collection accounts, or sub-account/master-account hierarchies. missing for 10: explicit routing-number issuance, virtual account/reconciliation feature docs, per-customer collection account docs, master/sub-account hierarchy docs.

   • [claimed-docs] “Creates and manages customer accounts”
   • [claimed-docs] “The Internal Transfer API allows you to transfer funds between two Synctera accounts, in real-time.”
   • [claimed-docs] “Issue cards, accept payments, and transfer money between accounts”

   proof ↗⚑ flag

Yield

1. finance leadIdle balances can earn — interest-bearing accounts or documented sweep options, with the rate mechanics and who keeps the spread spelled out

   weight 2 · round drawn
   Unit—none0/10

   Evidence covers deposit accounts, payments, cards, and credit products but contains no mention of interest-bearing accounts, sweep programs, rate mechanics, or spread-sharing arrangements for idle balances.

   ⚑ flag

   Synctera—none0/10

   Evidence covers customer accounts, cards, transfers, wires, KYC, webhooks, but nothing on interest-bearing accounts, sweep programs, or rate/spread mechanics between Synctera and bank partners. No documentation addresses idle balance yield or spread ownership.

   ⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Synctera
   Unit✓fullprobed8/10

   Unit hosts a live llms.txt (confirmed HTTP 200 via probe) with structured agent-oriented documentation covering accounts, payments, cards, credit products, and infrastructure details, which an AI agent can be pointed at directly. Missing for 10: independent/third-party confirmation of agent usage in practice and absence of a discoverable OpenAPI/machine-readable API spec (openapi.json/swagger.json returned 404s) to complement the llms.txt.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.unit.co/llms.txt # Unit > **Unit is a financial infrastructure platform for technology companies th…”
   • [claimed-docs] “Create deposit accounts and wallet accounts held in FBO structures. Support use cases including operating accounts, customer wallets, sub-ac…”
   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.unit.co/openapi.json, https://www.unit.co/swagger.json, https://www.unit.co/api/openapi.…”

   proof ↗⚑ flag

   Synctera✓fullprobed9/10

   A direct probe confirms Synctera serves a valid llms.txt at docs.synctera.com/llms.txt listing structured doc bundles (v2, v0) for agent consumption, plus a machine-readable OpenAPI spec, matching the agent-oriented docs story. Missing for 10: no independent/community confirmation of agents actually using it successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.synctera.com/llms.txt # Synctera - [v2 (658 pages)](https://docs.synctera.com/_llms/v2.md): Docume…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.synctera.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Synctera
   Unit—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Synctera~partialprobed4/10

   Synctera is API-first (OpenAPI spec, sandbox API keys) which inherently supports programmatic/headless calls, and docs show you can call APIs immediately after obtaining a sandbox key. However there is no explicit CI/CD guidance, CLI tool, or automation example (e.g., GitHub Actions, test harness) showing headless operation in a pipeline. Missing for 10: explicit CI/automation documentation, CLI or SDK examples for pipeline integration, and confirmation of non-interactive auth flows suited for CI.

   • [claimed-docs] “Once an API key is issued in Sandbox, you can immediately start calling the APIs below.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.synctera.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.synctera.com/llms.txt # Synctera - [v2 (658 pages)](https://docs.synctera.com/_llms/v2.md): Docume…”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Unit—none0/10

   Unit is a banking-as-a-service platform (not itself an agent), so an official MCP server for connecting agents is a fair axis to expect, but the evidence pack contains no mention of MCP, agent connectivity, or any such server—only standard API/docs content and failed probes for API specs. Missing for 10: any documentation of an MCP server, agent integration tooling, or even an OpenAPI spec that could underpin one.

   • [probe] “PROBE docs-md: HTTP 404 at https://www.unit.co/docs/api/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.unit.co/openapi.json, https://www.unit.co/swagger.json, https://www.unit.co/api/openapi.…”

   proof ↗⚑ flag

   Synctera—none0/10

   Synctera is a banking-as-a-service platform, so an official MCP server is a plausible axis, but the evidence pack shows only API docs, OpenAPI spec, and llms.txt — no mention of an MCP server or agent-connection capability.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.synctera.com/llms.txt # Synctera - [v2 (658 pages)](https://docs.synctera.com/_llms/v2.md): Docume…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.synctera.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Unit—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Synctera—none0/10

   Synctera is a banking-as-a-service API platform; evidence shows API docs, OpenAPI spec, and llms.txt but no mention of an official CLI tool for interacting with the platform. missing for 10: any CLI product, CLI documentation, or install instructions.

   ⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Synctera
   Unit~partialprobed5/10

   Unit's marketing/llms.txt content repeatedly references building via 'APIs' for accounts, payments, cards, and credit products (unit-docs-1 through unit-docs-5, unit-docs-9), implying a documented public API exists, but the evidence pack's own probes failed to locate any actual API documentation or OpenAPI/Swagger spec (unit-probe-2, unit-probe-3), leaving the claim unverified. Missing for 10: a working link to actual API reference docs, an OpenAPI/Swagger spec, or independent developer corroboration that the API is usable/documented in practice.

   • [claimed-docs] “Create deposit accounts and wallet accounts held in FBO structures. Support use cases including operating accounts, customer wallets, sub-ac…”
   • [claimed-docs] “Send and receive money using payment capabilities including ACH, wires, real-time payments, checks, and international payments, with settlem…”
   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”
   • [claimed-docs] “Direct, bare-metal access to the Federal Reserve, the card networks, and bank partners.”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.unit.co/docs/api/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.unit.co/openapi.json, https://www.unit.co/swagger.json, https://www.unit.co/api/openapi.…”

   proof ↗⚑ flag

   Synctera✓fullprobed8/10

   Synctera exposes a comprehensive, well-documented public REST API (customers, accounts, cards, transfers, KYC, webhooks) confirmed by a live OpenAPI spec and llms.txt discovery, with a sandbox API key flow for immediate programmatic access — clear evidence of driving the product entirely via documented API. Missing for 10: independent third-party developer confirmation/hands-on usage reports beyond vendor docs and automated probes.

   • [claimed-docs] “Once an API key is issued in Sandbox, you can immediately start calling the APIs below.”
   • [claimed-docs] “Issue cards, accept payments, and transfer money between accounts”
   • [claimed-docs] “The Webhook API enables integrators to subscribe to specific events on the Synctera platform.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.synctera.com/llms.txt # Synctera - [v2 (658 pages)](https://docs.synctera.com/_llms/v2.md): Docume…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.synctera.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Unit—none0/10

   Unit's evidence pack describes banking/payments infrastructure capabilities (accounts, payments, cards, credit) but contains no mention of API key scoping, credential permissions, or any mechanism for issuing least-privilege credentials for AI agents. This is a fair axis for an API platform, but no evidence supports it.

   ⚑ flag

   Synctera—none0/10

   Synctera is an API platform where scoped credentials would be a fair axis to ask about, but the evidence only shows generic API key issuance for Sandbox with no mention of scopes, permission levels, or least-privilege credential issuance for agents.

   • [claimed-docs] “Once an API key is issued in Sandbox, you can immediately start calling the APIs below.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Unit—none0/10

   The evidence pack describes Unit's banking/payments/card capabilities and API access via a Dashboard, but never mentions official SDKs (e.g., language-specific client libraries) for developers to build against. Probes even show 404s for OpenAPI/Swagger specs and a docs .md endpoint, further undermining any claim of accessible, well-documented programmatic tooling.

   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.unit.co/docs/api/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.unit.co/openapi.json, https://www.unit.co/swagger.json, https://www.unit.co/api/openapi.…”

   proof ↗⚑ flag

   Synctera—none0/10

   Evidence shows extensive API documentation, an OpenAPI spec, and an llms.txt for AI consumption, but there is no mention of official client SDKs (e.g., Python, JS, Java libraries) that developers could build against directly. Missing for 10: any evidence of official language-specific SDKs, SDK versioning, or SDK code samples.

   ⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Synctera
   Unit—none0/10

   The evidence pack contains no mention of webhooks or event subscription capabilities anywhere in Unit's documentation excerpts; only general product/banking-infrastructure descriptions and failed probes for API specs are present.

   ⚑ flag

   Synctera✓fullclaimed8/10

   Synctera provides a dedicated Webhook API letting integrators subscribe to specific platform events, documented in a first-party guide. Missing for 10: independent/hands-on corroboration of webhook reliability and richer detail on event types/payload structure beyond the single guide reference.

   • [claimed-docs] “The Webhook API enables integrators to subscribe to specific events on the Synctera platform.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Unit—none0/10

   Unit is a banking-as-a-service infrastructure platform; evidence covers accounts, payments, cards, and credit products with dashboard/API data access, but nothing describes AI-generated insights or suggestions surfaced from customer data. Missing for 10: any mention of AI/ML-driven analytics, anomaly detection, or suggestion features within the dashboard or API.

   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”
   • [claimed-docs] “Store, move, spend, and lend money inside your product.”

   proof ↗⚑ flag

   Synctera—none0/10

   Synctera is a banking-as-a-service API platform for core banking operations; evidence pack shows no AI-generated insights, analytics, or suggestion features derived from customer data. This is an applicable axis for a fintech data platform, but no evidence of any AI-driven insight capability exists.

   ⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Unit—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Synctera—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Unit—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Synctera—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Unit—none0/10

   No evidence of an interactive API reference or runnable examples; probes for docs/openapi endpoints returned 404s, and no docs mention a sandbox/console for testing API calls.

   • [probe] “PROBE docs-md: HTTP 404 at https://www.unit.co/docs/api/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.unit.co/openapi.json, https://www.unit.co/swagger.json, https://www.unit.co/api/openapi.…”

   proof ↗⚑ flag

   Synctera—none0/10

   Evidence shows Synctera has API documentation, an OpenAPI spec, and llms.txt for docs discovery, but nothing indicates an interactive API reference with runnable/try-it-out examples (e.g., Swagger UI, Postman collections, live sandbox console). missing for 10: interactive explorer UI, runnable code samples, live 'try it' console evidence.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.synctera.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.synctera.com/llms.txt # Synctera - [v2 (658 pages)](https://docs.synctera.com/_llms/v2.md): Docume…”
   • [claimed-docs] “Once an API key is issued in Sandbox, you can immediately start calling the APIs below.”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Synctera
   Unit—none0/10

   Probes explicitly show no OpenAPI/swagger file at any candidate path (all 404), and no docs-md export exists either; no evidence of a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.unit.co/openapi.json, https://www.unit.co/swagger.json, https://www.unit.co/api/openapi.…”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.unit.co/docs/api/.md”

   proof ↗⚑ flag

   Synctera✓fullprobed9/10

   Probe confirms a live, machine-readable OpenAPI spec at docs.synctera.com/openapi.json returning a valid 'openapi' key, and docs also expose an llms.txt index for machine consumption. Missing for 10: no independent third-party corroboration of spec completeness/versioning beyond the probe.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.synctera.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.synctera.com/llms.txt # Synctera - [v2 (658 pages)](https://docs.synctera.com/_llms/v2.md): Docume…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Synctera
   Unit—none0/10

   Unit is a banking-as-a-service API platform, and sandbox/test environments are a standard, fair expectation for such a product, but none of the evidence mentions a sandbox environment, test mode, or separation from production data. Missing for 10: any mention of a sandbox/test environment, test API keys, or documentation describing safe non-production testing.

   ⚑ flag

   Synctera✓fullclaimed6/10

   Synctera's own docs describe a distinct Sandbox environment where an API key can be issued and used to call APIs immediately, implying a separate environment from production. Missing for 10: explicit documentation of sandbox data isolation guarantees, sample sandbox test data, and independent/hands-on confirmation that sandbox never touches production data.

   • [claimed-docs] “Once an API key is issued in Sandbox, you can immediately start calling the APIs below.”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Synctera
   Unit—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; OpenAPI spec and docs endpoints were not found (404s), and no changelog or version policy is mentioned anywhere in the pack.

   • [probe] “PROBE docs-md: HTTP 404 at https://www.unit.co/docs/api/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.unit.co/openapi.json, https://www.unit.co/swagger.json, https://www.unit.co/api/openapi.…”

   proof ↗⚑ flag

   Synctera~partialprobed4/10

   Evidence confirms Synctera has versioned API documentation (v0 and v2 exist per llms.txt) and a public OpenAPI spec, showing some API versioning discipline, but there is no mention of a documented deprecation policy, sunset timelines, or migration guidance between versions. missing for 10: explicit deprecation policy documentation, version sunset/migration guides, changelog or breaking-change notices.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.synctera.com/llms.txt # Synctera - [v2 (658 pages)](https://docs.synctera.com/_llms/v2.md): Docume…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.synctera.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Unit—none0/10

   The evidence describes Unit's account, payment, card, and credit APIs but never mentions batch/bulk endpoints, multi-item operations, or automation-scale processing across many records at once. Missing for 10: any documentation of batch APIs, bulk create/update endpoints, or evidence of automation-depth features letting an AI agent act on many items in one call.

   • [claimed-docs] “Create deposit accounts and wallet accounts held in FBO structures. Support use cases including operating accounts, customer wallets, sub-ac…”
   • [claimed-docs] “Send and receive money using payment capabilities including ACH, wires, real-time payments, checks, and international payments, with settlem…”
   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”

   proof ↗⚑ flag

   Synctera—none0/10

   The evidence pack covers individual resource APIs (customers, accounts, cards, transfers, verification) but never mentions batch/bulk endpoints, multi-item operations, or async bulk job APIs. Missing for 10: any documented bulk/batch API, bulk import/export tooling, or evidence of processing multiple records in a single call.

   ⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Synctera
   Unit—none0/10

   Unit is banking infrastructure where event-driven automation (e.g., webhooks triggering actions on transactions/payments) would be a reasonable capability, but the evidence pack contains no mention of webhooks, event triggers, or rule-based automation—only account, payment, card, and dashboard descriptions. Missing for 10: any documentation of webhook/event subscription system, rule definition interface, or automated action triggers.

   ⚑ flag

   Synctera~partialclaimed3/10

   Synctera's Webhook API lets integrators subscribe to platform events, which is the foundation for event-driven automation, but there's no evidence of a rules engine or declarative 'if event then action' capability built into the platform. Missing for 10: documented rule-definition interface, conditional logic/action mapping, and evidence of automated actions triggering without custom integrator code.

   • [claimed-docs] “The Webhook API enables integrators to subscribe to specific events on the Synctera platform.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Synctera
   Unit—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Synctera~partialclaimed3/10

   Synctera exposes a 'scheduled payments' API to create and manage recurring payment schedules, which is the only evidence of any recurring/scheduled execution capability. There is no evidence of a general-purpose job/workflow scheduler, cron-like automation, or orchestration engine that an AI-native user could use to schedule arbitrary recurring workflows beyond payments. Missing for 10: general recurring workflow/job scheduling API, agent/automation orchestration support, and independent confirmation of scheduling reliability.

   • [claimed-docs] “Create and manage scheduled payments for customers”

   proof ↗⚑ flag

Agent operations

1. ai-native userAn agent can operate an account within policy — scoped credentials that let it read balances and initiate transfers under amount caps and counterparty allowlists, a use the vendor documents by name

   weight 3 · round drawn
   Unit—none0/10

   Unit's evidence describes general banking-as-a-service capabilities (accounts, payments, cards) but contains no mention of AI agents, scoped credentials, amount caps, counterparty allowlists, or any agent-specific access model named by the vendor.

   ⚑ flag

   Synctera—none0/10

   Synctera's docs cover accounts, transfers, cards, KYC, and APIs generally, but there is no evidence of agent-specific scoped credentials, amount caps, counterparty allowlists, or any vendor-documented named feature for AI agents operating within policy. Missing for 10: named agent/AI credential scoping feature, amount cap enforcement docs, counterparty allowlist mechanism, any mention of AI agents at all.

   • [claimed-docs] “The Internal Transfer API allows you to transfer funds between two Synctera accounts, in real-time.”
   • [claimed-docs] “Once an API key is issued in Sandbox, you can immediately start calling the APIs below.”

   proof ↗⚑ flag

Agent visibility

1. ai-native userAn agent can read the full banking picture — accounts, transactions, pending activity, documents — through a clean API or MCP surface without screen-scraping a dashboard

   weight 2 · round to Synctera
   Unit~partialprobed5/10

   Unit's docs claim broad API access to accounts, balances, transactions, cards, and payments data (unit-docs-1,2,3,5), which covers much of the 'banking picture' via API rather than screen-scraping. However, there is no mention of an MCP surface, and probes show no discoverable OpenAPI/swagger spec or docs.md (unit-probe-2, unit-probe-3), and no evidence of document retrieval (e.g., statements) via API. Missing for 10: MCP server/tool surface, verifiable OpenAPI spec, document/statement API endpoints, and independent corroboration beyond vendor llms.txt claims.

   • [claimed-docs] “Create deposit accounts and wallet accounts held in FBO structures. Support use cases including operating accounts, customer wallets, sub-ac…”
   • [claimed-docs] “Send and receive money using payment capabilities including ACH, wires, real-time payments, checks, and international payments, with settlem…”
   • [claimed-docs] “Issue physical and virtual cards with configurable controls, real-time authorization capabilities, transaction data, and card lifecycle mana…”
   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.unit.co/docs/api/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.unit.co/openapi.json, https://www.unit.co/swagger.json, https://www.unit.co/api/openapi.…”

   proof ↗⚑ flag

   Synctera~partialprobed6/10

   Synctera exposes a broad REST/OpenAPI surface covering accounts, transactions, transfers, cards, external account balance/transaction retrieval, document verification, and webhook-driven event/pending-activity feeds, plus an llms.txt for AI discoverability — strongly supporting agent-readable banking data without screen-scraping. However there is no evidence of a dedicated MCP server or agent-specific read surface, only a general OpenAPI/webhook API. Missing for 10: explicit MCP server/tool endpoint, unified 'read full picture' aggregation endpoint, independent confirmation of AI-agent usage in production.

   • [claimed-docs] “Creates and manages customer accounts”
   • [claimed-docs] “The Internal Transfer API allows you to transfer funds between two Synctera accounts, in real-time.”
   • [claimed-docs] “Synctera has partnered with Plaid and Finicity to verify ownership and retrieve balance and transaction information.”
   • [claimed-docs] “Verify documentation for a customer”
   • [claimed-docs] “The Webhook API enables integrators to subscribe to specific events on the Synctera platform.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.synctera.com/llms.txt # Synctera - [v2 (658 pages)](https://docs.synctera.com/_llms/v2.md): Docume…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.synctera.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

Builtin ai

1. ops userThe product ships its own AI for banking operations — natural-language search over transactions, drafted responses to disputes and alerts, anomaly summaries — built in, not bolted on

   weight 2 · round drawn
   Unit—none0/10

   Evidence describes Unit as banking infrastructure (accounts, payments, cards, credit) but contains no mention of any built-in AI features such as natural-language transaction search, drafted dispute responses, or anomaly summaries.

   ⚑ flag

   Synctera—none0/10

   No evidence of any built-in AI features—natural-language transaction search, dispute/alert drafting, or anomaly summaries—anywhere in the docs; the evidence pack only covers core banking-as-a-service APIs (accounts, cards, transfers, KYC, webhooks). This is an applicable axis for a banking platform but nothing supports it.

   ⚑ flag

Card issuance

1. developerAccounts come with cards — issue virtual and physical debit cards tied to the account through the same API, with spend controls and digital wallet support

   weight 2 · round to Unit
   Unit~partialclaimed6/10

   Unit's docs explicitly confirm issuing both physical and virtual cards via API with configurable controls, real-time authorization, and lifecycle management, tied to accounts (unit-docs-3, unit-docs-10). However, no evidence in the pack mentions digital wallet (Apple Pay/Google Pay) provisioning support. Missing for 10: explicit digital wallet/tokenization support, independent/hands-on corroboration of card issuance API.

   • [claimed-docs] “Issue physical and virtual cards with configurable controls, real-time authorization capabilities, transaction data, and card lifecycle mana…”
   • [claimed-docs] “Store, move, spend, and lend money inside your product.”
   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”

   proof ↗⚑ flag

   Synctera~partialclaimed5/10

   Docs confirm card issuance and management is part of the same API platform as accounts (synctera-docs-4, synctera-docs-7), consistent with the story's core ask. However, there's no explicit evidence distinguishing virtual vs. physical card issuance, spend controls, or digital wallet (Apple/Google Pay) provisioning. Missing for 10: explicit virtual/physical card type documentation, spend control API details, digital wallet tokenization/push-provisioning support.

   • [claimed-docs] “Issues, activates, and manages cards for customers”
   • [claimed-docs] “Issue cards, accept payments, and transfer money between accounts”
   • [claimed-docs] “Creates and manages customer accounts”

   proof ↗⚑ flag

Disputes

1. ops userCard and ACH disputes are handled properly — Reg E investigation timelines, provisional credit mechanics, and my operational responsibilities documented and tooled

   weight 2 · round drawn
   Unit—none0/10

   Evidence only shows generic marketing claims about card issuance, ACH payments, and dashboard access — nothing addresses dispute handling, Reg E investigation timelines, provisional credit mechanics, or documented ops responsibilities for disputes.

   ⚑ flag

   Synctera—none0/10

   The evidence pack shows card issuance, account management, transfers, KYC, webhooks, and disclosures, but contains no mention of dispute management, Reg E investigation timelines, provisional credit mechanics, or ops tooling/responsibilities for chargebacks/disputes. This is a fair axis for a card/BaaS issuing platform, but no supporting evidence exists.

   ⚑ flag

Balances events

1. developerThe ledger is real-time and event-driven — balance reads that reflect holds and pending activity, and webhooks for every transaction state change so my system mirrors the bank exactly

   weight 3 · round to Synctera
   Unit~partialclaimed3/10

   Unit's docs mention real-time balances and transaction data across accounts, payments, and cards (unit-docs-1, unit-docs-2, unit-docs-3), suggesting some real-time ledger visibility, but there is no mention of holds/pending balance mechanics or of webhooks for transaction state changes anywhere in the evidence pack. missing for 10: explicit documentation of webhook events per transaction state change, explicit handling of holds/pending balances in real-time reads, independent/hands-on confirmation of event-driven architecture.

   • [claimed-docs] “Create deposit accounts and wallet accounts held in FBO structures. Support use cases including operating accounts, customer wallets, sub-ac…”
   • [claimed-docs] “Send and receive money using payment capabilities including ACH, wires, real-time payments, checks, and international payments, with settlem…”
   • [claimed-docs] “Issue physical and virtual cards with configurable controls, real-time authorization capabilities, transaction data, and card lifecycle mana…”

   proof ↗⚑ flag

   Synctera~partialclaimed5/10

   Synctera documents a Webhook API for subscribing to platform events and real-time internal transfers, which supports event-driven notification of transaction state changes, but the evidence pack does not explicitly confirm real-time balance reads reflecting holds/pending activity or an exhaustive webhook-to-ledger-state mapping. missing for 10: explicit documentation of hold/pending balance semantics in balance reads, confirmation that webhooks fire for every transaction state transition (not just select events), and independent/hands-on verification that the ledger mirrors bank state in real time.

   • [claimed-docs] “The Internal Transfer API allows you to transfer funds between two Synctera accounts, in real-time.”
   • [claimed-docs] “The Webhook API enables integrators to subscribe to specific events on the Synctera platform.”

   proof ↗⚑ flag

Data quality

1. developerTransaction data is rich enough to build on — counterparty details, rail-specific metadata, stable identifiers, and enrichment that makes a raw bank feed usable in-product

   weight 2 · round to Unit
   Unit~partialclaimed4/10

   Docs confirm Unit exposes transaction data via API/dashboard with settlement-level visibility for payments, cards, and accounts (unit-docs-1, unit-docs-2, unit-docs-3, unit-docs-5), but none of the evidence specifically describes counterparty detail fields, rail-specific metadata schemas, stable transaction identifiers, or enrichment logic that would make a raw bank feed usable in-product. missing for 10: explicit documentation of counterparty data fields, rail-specific metadata, stable/idempotent transaction IDs, and enrichment/categorization features.

   • [claimed-docs] “Create deposit accounts and wallet accounts held in FBO structures. Support use cases including operating accounts, customer wallets, sub-ac…”
   • [claimed-docs] “Send and receive money using payment capabilities including ACH, wires, real-time payments, checks, and international payments, with settlem…”
   • [claimed-docs] “Issue physical and virtual cards with configurable controls, real-time authorization capabilities, transaction data, and card lifecycle mana…”
   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”

   proof ↗⚑ flag

   Synctera~partialclaimed3/10

   Synctera exposes distinct transaction guides (domestic wires, internal transfers, external account linking via Plaid/Finicity, RDC) and a webhook API for event data, suggesting a structured transaction model, but no evidence explicitly documents counterparty detail fields, rail-specific metadata schemas, stable transaction identifiers, or enrichment logic that would make raw feeds directly usable in-product. missing for 10: explicit transaction object schema showing counterparty fields, rail metadata, stable IDs, and enrichment/categorization documentation.

   • [claimed-docs] “Domestic wires refer to the transfer of funds between 2 US based accounts.”
   • [claimed-docs] “The Internal Transfer API allows you to transfer funds between two Synctera accounts, in real-time.”
   • [claimed-docs] “Synctera has partnered with Plaid and Finicity to verify ownership and retrieve balance and transaction information.”
   • [claimed-docs] “The Webhook API enables integrators to subscribe to specific events on the Synctera platform.”
   • [claimed-docs] “Handles remote deposit capture (RDC) transactions”

   proof ↗⚑ flag

Statements

1. ops userThe paper obligations are automated — monthly statements generated per account, and tax documents (1099-INT) produced and retrievable through the API

   weight 2 · round drawn
   Unit—none0/10

   No evidence pack item mentions monthly statement generation or 1099-INT tax document production/retrieval via API; docs cover accounts, payments, cards, credit, and dashboard access but never statements or tax forms.

   ⚑ flag

   Synctera—none0/10

   No evidence in the pack mentions monthly statement generation or 1099-INT tax document production/retrieval via API; coverage includes accounts, cards, payments, KYC, and disclosures but nothing on statements or tax forms.

   ⚑ flag

Kyc kyb

1. developerCustomer verification is programmatic — KYC for individuals and KYB for businesses with document collection, watchlist screening, and clearly modeled application states

   weight 3 · round to Synctera
   Unit—none0/10

   The evidence pack only vaguely references 'compliance' data access (unit-docs-5) but contains no specifics on programmatic KYC/KYB flows, document collection, watchlist screening, or modeled application states — capabilities Unit is known to offer but which are unevidenced here.

   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”

   proof ↗⚑ flag

   Synctera~partialclaimed6/10

   Synctera has documented KYC/KYB verification objects covering personal and business customers, watchlist screening, and document verification, plus customer record management APIs. However, evidence does not explicitly show a modeled application/verification state machine (e.g., pending/approved/rejected/manual-review states) or detailed document collection workflow specifics. missing for 10: explicit documentation of verification application state model/lifecycle, document collection API details, and independent/hands-on corroboration of KYC/KYB flows.

   • [claimed-docs] “Creates and manages records for personal customers”
   • [claimed-docs] “Creates and manages records for business customers”
   • [claimed-docs] “Synctera's verification solution runs identity and watchlist checks for personal and business customers and records the results as `verifica…”
   • [claimed-docs] “Verify documentation for a customer”

   proof ↗⚑ flag

Review queues

1. ops userWork the onboarding queue — see why an application is pending, supply additional documents, and understand which decisions are mine versus the bank's

   weight 2 · round to Synctera
   Unit—none0/10

   The evidence pack covers account, payment, card, and credit infrastructure plus general Dashboard/API access to 'compliance and operational data' (unit-docs-5), but nothing describes an onboarding queue, reasons for pending applications, document collection workflows, or a clear delineation of ops-vs-bank decision authority. This is a plausible axis for a BaaS platform handling KYC/onboarding, but no evidence substantiates the specific capability.

   ⚑ flag

   Synctera~partialclaimed4/10

   Synctera exposes KYC/KYB verification objects, document verification, and an operational workflow platform pitched as offering 'complete data visibility and seamless collaboration' with bank partners, which touches on the onboarding-queue and bank/program collaboration themes. However, there is no concrete evidence of a queue UI showing why an application is pending, a document-upload workflow for ops, or an explicit description of which decisions belong to ops versus the bank. missing for 10: pending-reason visibility in a queue UI, ops-driven document request/upload flow, explicit ops-vs-bank decision boundaries.

   • [claimed-docs] “Manage all operational workflows in a centralized platform with a set of tools that provide complete data visibility and seamless collaborat…”
   • [claimed-docs] “Synctera's verification solution runs identity and watchlist checks for personal and business customers and records the results as `verifica…”
   • [claimed-docs] “Verify documentation for a customer”
   • [claimed-docs] “Handles legally required disclosures to customers”

   proof ↗⚑ flag

Limits holds

1. ops userSet risk controls per account and per program — transaction and velocity limits, holds on suspicious activity, and account freezes with documented reinstatement paths

   weight 2 · round drawn
   Unit—none0/10

   Evidence only shows generic 'configurable card controls' and general compliance/operational data access; there is no mention of transaction or velocity limits, suspicious-activity holds, account freezes, or documented reinstatement paths at the account/program level. missing for 10: velocity/transaction limit configuration, hold/freeze workflow documentation, reinstatement process details.

   • [claimed-docs] “Issue physical and virtual cards with configurable controls, real-time authorization capabilities, transaction data, and card lifecycle mana…”
   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”

   proof ↗⚑ flag

   Synctera—none0/10

   The evidence pack covers customer/account creation, cards, transfers, KYC/KYB, webhooks, and general 'operational workflows' but contains no specific mention of transaction/velocity limits, suspicious-activity holds, account freeze mechanisms, or documented reinstatement paths.

   • [claimed-docs] “Manage all operational workflows in a centralized platform with a set of tools that provide complete data visibility and seamless collaborat…”
   • [claimed-docs] “Synctera's verification solution runs identity and watchlist checks for personal and business customers and records the results as `verifica…”

   proof ↗⚑ flag

Loss allocation

1. finance leadFraud economics are explicit — who eats ACH return fraud, card disputes, and account takeover losses, with the platform's prevention tooling documented alongside the liability split

   weight 2 · round drawn
   Unit—none0/10

   Evidence describes Unit's banking, payments, and card infrastructure features but contains no discussion of who bears ACH return fraud, card dispute, or ATO losses, nor any liability-split documentation alongside fraud prevention tooling.

   ⚑ flag

   Synctera—none0/10

   Evidence shows Synctera's KYC/verification, payments, and card issuing docs, but nothing addresses fraud-loss liability allocation (who bears ACH return fraud, card dispute, or ATO losses) or documents prevention tooling alongside a liability split — the core of this story.

   ⚑ flag

Program scaling

1. founderGrowth doesn't hit invisible walls — program-level limits, approval stages, and the path to raising them are documented rather than discovered in an email from the bank

   weight 2 · round drawn
   Unit—none0/10

   No evidence pack item discusses program-level limits, underwriting/approval stages, or a documented process for raising limits; docs only describe product capabilities (accounts, payments, cards, credit products) without disclosing risk thresholds or escalation paths. This is a fair question for a BaaS platform since program limits and approval stages are core to bank-partner risk programs, so absence of evidence yields 'none' rather than 'na'.

   ⚑ flag

   Synctera—none0/10

   No evidence pack item documents program-level limits, approval-stage thresholds, or a defined process for raising limits; documentation covers API features (accounts, cards, transfers, KYC) but not growth-limit governance or escalation paths.

   ⚑ flag

Ach

1. developerOriginate ACH through the API — credits and debits, same-day windows, and the unhappy paths (returns, NOCs, reversals) modeled as first-class objects with webhooks

   weight 3 · round to Unit
   Unit~partialclaimed3/10

   Unit's docs confirm ACH is supported as a payment rail with transaction visibility, but there is no evidence of same-day ACH windows, or of returns, NOCs, and reversals modeled as first-class API objects with dedicated webhooks. missing for 10: same-day ACH windows, ACH return/NOC/reversal objects, webhook event documentation for these unhappy paths, and any API/OpenAPI reference confirming these fields.

   • [claimed-docs] “Send and receive money using payment capabilities including ACH, wires, real-time payments, checks, and international payments, with settlem…”
   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”

   proof ↗⚑ flag

   Synctera—none0/10

   The evidence pack covers internal transfers, domestic wires, scheduled payments, and webhooks generally, but contains no mention of ACH origination, credit/debit ACH types, same-day ACH windows, or ACH-specific unhappy-path objects like returns, NOCs, or reversals. Since Synctera is a banking-as-a-service platform where ACH is a plausible core money-movement capability, absence of evidence means this axis is unmet rather than inapplicable.

   ⚑ flag

Checks

1. ops userChecks still work — programmatic check issuance and check deposit with image capture, because real businesses still receive and send paper

   weight 2 · round to Synctera
   Unit~partialclaimed3/10

   Unit's docs list 'checks' as one of several payment rails alongside ACH, wires, and RTP, but there is no detail on check issuance workflows or remote deposit capture with image upload/processing. Missing for 10: specific API/endpoint documentation for check issuance, check printing/mailing, and deposit capture with image capture and verification.

   • [claimed-docs] “Send and receive money using payment capabilities including ACH, wires, real-time payments, checks, and international payments, with settlem…”

   proof ↗⚑ flag

   Synctera~partialclaimed5/10

   Synctera explicitly documents remote deposit capture (RDC) handling and card issuance, indicating check deposit capability, but there is no direct evidence of programmatic check issuance (printing/mailing physical checks) or details on the image capture API/workflow. missing for 10: explicit check-issuance API docs, image capture endpoint/schema details, independent or hands-on confirmation of RDC workflow.

   • [claimed-docs] “Handles remote deposit capture (RDC) transactions”
   • [claimed-docs] “Issues, activates, and manages cards for customers”

   proof ↗⚑ flag

Instant rails

1. developerThe faster rails are there when I need them — domestic wires, RTP, and FedNow origination and receipt through the same API, with per-rail capabilities documented

   weight 2 · round to Unit
   Unit~partialprobed4/10

   Unit's docs mention wires and 'real-time payments' (implying RTP) alongside ACH and checks, and claims direct Fed Reserve connectivity, but there is no explicit mention of FedNow origination/receipt, and no per-rail documentation of capabilities (limits, cutoffs, originate vs receive) is evidenced — in fact the docs/OpenAPI probes returned 404s, so detailed rail-specific documentation can't be confirmed. missing for 10: explicit FedNow support, per-rail capability tables (limits/cutoffs/origination vs receipt), and accessible detailed API docs confirming rail parity.

   • [claimed-docs] “Send and receive money using payment capabilities including ACH, wires, real-time payments, checks, and international payments, with settlem…”
   • [claimed-docs] “Unit is a registered Federal Reserve service provider with direct connectivity to Federal Reserve systems on behalf of partner banks.”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.unit.co/docs/api/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.unit.co/openapi.json, https://www.unit.co/swagger.json, https://www.unit.co/api/openapi.…”

   proof ↗⚑ flag

   Synctera~partialclaimed3/10

   Docs confirm domestic wire origination/receipt via API (synctera-docs-15) and general money-movement APIs (synctera-docs-5, synctera-docs-6, synctera-docs-7), but there is no evidence of RTP or FedNow rails, per-rail capability documentation, or same-API origination/receipt for those faster rails. Missing for 10: RTP support, FedNow support, per-rail capability docs, and origination vs receipt distinctions for faster payments.

   • [claimed-docs] “Domestic wires refer to the transfer of funds between 2 US based accounts.”
   • [claimed-docs] “The Internal Transfer API allows you to transfer funds between two Synctera accounts, in real-time.”
   • [claimed-docs] “Create and manage scheduled payments for customers”
   • [claimed-docs] “Issue cards, accept payments, and transfer money between accounts”

   proof ↗⚑ flag

International

1. founderMoney can cross borders — international wires or SWIFT, FX with transparent rates, and the coverage map of currencies and corridors documented

   weight 2 · round to Unit
   Unit~partialclaimed3/10

   Unit's docs mention 'international payments' as one of its payment capabilities, implying cross-border money movement exists, but there is no documentation of FX rate transparency, SWIFT specifics, or a coverage map of supported currencies/corridors. missing for 10: FX rate transparency details, SWIFT/wire specifics, currency and corridor coverage map.

   • [claimed-docs] “Send and receive money using payment capabilities including ACH, wires, real-time payments, checks, and international payments, with settlem…”

   proof ↗⚑ flag

   Synctera—none0/10

   Evidence only documents domestic wires explicitly scoped to transfers 'between 2 US based accounts' (synctera-docs-15), plus internal transfers between Synctera accounts (synctera-docs-5). There is no mention anywhere in the pack of international wires, SWIFT, FX rates, or a coverage map of currencies/corridors, suggesting Synctera is US-domestic focused.

   • [claimed-docs] “Domestic wires refer to the transfer of funds between 2 US based accounts.”
   • [claimed-docs] “The Internal Transfer API allows you to transfer funds between two Synctera accounts, in real-time.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Synctera
   Unit~partialprobed4/10

   Unit is API-first infrastructure with a Dashboard described as accessing the same customer/account/payment/card data as the APIs (unit-docs-5), suggesting reasonable UI-API parity, but there is no explicit claim that every dashboard action is API-exposed, and probes show missing OpenAPI spec and machine-readable docs (unit-probe-2, unit-probe-3), undermining verifiability for an AI-native consumer. Missing for 10: explicit parity statement, discoverable OpenAPI/API reference, and evidence of AI-agent-friendly API consumption.

   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.unit.co/docs/api/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.unit.co/openapi.json, https://www.unit.co/swagger.json, https://www.unit.co/api/openapi.…”

   proof ↗⚑ flag

   Synctera~partialprobed6/10

   Synctera's docs describe an extensive, well-documented REST API (OpenAPI spec, llms.txt) covering nearly all core banking operations—customers, accounts, cards, transfers, KYC, webhooks, disclosures—suggesting broad API-first coverage. However, the evidence also references a separate 'centralized platform' with UI tools for bank-partner collaboration (synctera-docs-16), and there is no explicit claim or verification that every UI-only workflow (e.g., dashboard operations, partner collaboration tools) is fully mirrored in the API. Missing for 10: explicit parity statement or audit confirming UI-exclusive features (e.g., operational dashboards) are also API-accessible, and independent/hands-on confirmation of full parity.

   • [claimed-docs] “Manage all operational workflows in a centralized platform with a set of tools that provide complete data visibility and seamless collaborat…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.synctera.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.synctera.com/llms.txt # Synctera - [v2 (658 pages)](https://docs.synctera.com/_llms/v2.md): Docume…”
   • [claimed-docs] “Once an API key is issued in Sandbox, you can immediately start calling the APIs below.”
   • [claimed-docs] “Issue cards, accept payments, and transfer money between accounts”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Unit—none0/10

   The evidence describes Unit's banking infrastructure capabilities (accounts, payments, cards, credit) and API/dashboard access to data, but nothing indicates a data export feature in open formats or any mechanism for a customer to extract and leave with their data. Missing for 10: any documented export/download feature, open-format data export (CSV/JSON dumps), or portability/exit tooling.

   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”

   proof ↗⚑ flag

   Synctera—none0/10

   The evidence pack shows Synctera's API and webhook documentation (docs-13, probe-1, probe-2) but no mention of a bulk data export feature, open-format data portability, or account-closure data extraction for customers. This is a fair axis for a BaaS platform handling customer financial data, but no evidence supports it.

   ⚑ flag

Charter clarity

1. founderExactly who holds the charter — whether the platform is a bank, a direct program with a named partner bank, or middleware between me and someone else's sponsor — and what happens to my customers if the platform fails

   weight 3 · round to Synctera
   Unit~partialclaimed3/10

   Docs confirm Unit operates as middleware working through 'one or multiple Unit bank partners' and is a Federal Reserve service provider on behalf of partner banks, establishing that Unit itself is not the chartered bank. However, there is no evidence naming specific partner banks per customer, no disclosure of FBO/pass-through insurance mechanics, and nothing addressing what happens to end-customers' funds if Unit itself fails or a program winds down. Missing for 10: named partner bank identification per account, FDIC pass-through insurance details, and explicit platform-failure/customer-protection disclosures.

   • [claimed-docs] “Companies can work with one or multiple Unit bank partners through the same infrastructure.”
   • [claimed-docs] “Unit is a registered Federal Reserve service provider with direct connectivity to Federal Reserve systems on behalf of partner banks.”
   • [claimed-docs] “Create deposit accounts and wallet accounts held in FBO structures. Support use cases including operating accounts, customer wallets, sub-ac…”

   proof ↗⚑ flag

   Synctera~partialclaimed4/10

   Docs confirm Synctera's sponsor-bank model — it explicitly connects founders with partner banks and provides collaboration tools 'between you and your bank partner' (synctera-docs-16, synctera-docs-17), making clear it is middleware rather than a chartered bank itself. However, there is no evidence addressing what happens to customer funds/accounts if Synctera itself fails or is wound down, which is a core part of this story. Missing for 10: explicit disclosure of failure/wind-down protections for end customers, clarity on which specific bank charter backs a given program, and any independent/regulatory confirmation of the sponsor relationship.

   • [claimed-docs] “Manage all operational workflows in a centralized platform with a set of tools that provide complete data visibility and seamless collaborat…”
   • [claimed-docs] “Synctera connects you with the banks in our network that best align with your product vision and timeline.”

   proof ↗⚑ flag

Compliance tooling

1. ops userThe compliance workload is tooled — transaction monitoring, sanctions screening, case management for alerts, and SAR-filing support with a clear split of duties between me, the platform, and the bank

   weight 2 · round to Synctera
   Unit—none0/10

   Evidence only mentions generic 'compliance data' access via dashboard/APIs, with no mention of transaction monitoring, sanctions screening, alert case management, SAR-filing support, or a defined split of compliance duties between ops, platform, and bank.

   • [claimed-docs] “The Unit Dashboard and APIs provide teams with access to customer, account, payment, card, transaction, compliance, and operational data.”

   proof ↗⚑ flag

   Synctera~partialclaimed4/10

   Docs show KYC/KYB verification with watchlist checks (implying sanctions screening) and a general claim of centralized operational tooling with bank-partner collaboration, suggesting some duty-split framework exists. However, there is no explicit evidence of transaction monitoring, alert case management, or SAR-filing support tooling. missing for 10: transaction monitoring tooling, case management for alerts, SAR-filing support, explicit description of duty split between ops/platform/bank for compliance workflows.

   • [claimed-docs] “Synctera's verification solution runs identity and watchlist checks for personal and business customers and records the results as `verifica…”
   • [claimed-docs] “Manage all operational workflows in a centralized platform with a set of tools that provide complete data visibility and seamless collaborat…”
   • [claimed-docs] “Handles legally required disclosures to customers”

   proof ↗⚑ flag

Reconciliation

1. finance leadThe platform ledger reconciles to the bank core — documented daily reconciliation between what the API reports and what the bank holds, the failure that sank Synapse-era programs

   weight 3 · round drawn
   Unit—none0/10

   No evidence of documented daily reconciliation processes, ledger-to-bank-core matching, or any explicit reconciliation guarantee; evidence only covers general account/payment/card capabilities and real-time balances, not reconciliation controls addressing the Synapse-style failure mode.

   ⚑ flag

   Synctera—none0/10

   The evidence pack contains no documentation of a reconciliation process, ledger-to-bank-core matching, or any daily reconciliation reporting mechanism — only vague references to 'complete data visibility' and general product features (customer/card/transfer APIs). Given the sponsor-bank model risk highlighted by Synapse's collapse, this is a fair and material axis for a BaaS platform, but no concrete evidence shows Synctera documents or automates ledger reconciliation with bank partners.

   ⚑ flag