earlyink
141 first flagged17 Oct 2026

Policy Probe: multilingual policy audits for money-moving banking agents

Replays customer requests in Spanish and other languages to test whether banking agents follow fee, confirmation and privacy policy. Banks pay.

Competitive · Agent guards flip verdicts across languages

Written for: Small startup team

Next step

Call the head of model risk at a US consumer lender with many Spanish-speaking customers, the kind Oportun serves. Ask whether the guard on their servicing agent has ever been tested with Spanish requests, and offer to run 200 translated policy cases for free.

Why now

Fintechs with large Spanish-speaking customer bases are putting agents in charge of waiving fees, moving money and changing account details, while model risk teams validate them in English. Two papers now provide both an audit method and a measured failure. This differs from Fair Shake, which tests outcome fairness, and from Guardrail Fuzzer, which tests typed decision models. Policy Probe tests whether whole tool-call trajectories follow written bank policy, in every language customers use. With Citi and others restricting outside agents, banks' own agents get more traffic and more scrutiny.

What became possible

PROBE trains auditors that check whether a tool-using agent obeyed policies on pricing, privacy, confirmation and safety. That gap is not covered by capability benchmarks or by content red-teaming. LinguaGuardBench shows that translating only the user's request, with everything else unchanged, changes what step-level guards decide. Guards trained and tested in English are a security weakness.

Two ways in

  1. Policy-to-test generator

    Turns a bank's written agent policies into trajectories with labelled outcomes, translates them into the bank's top customer languages, and reports where the agent or its guard flips.

    Customer
    Model risk and compliance at fintech lenders and neobanks
    Model
    Per-agent validation engagement, then annual subscription
  2. CI gate

    Reruns the multilingual suite on every prompt, model or tool change and blocks the release on new violations.

    Customer
    AI platform teams at banks
    Model
    Seat plus run-volume pricing

Competition

Competitive

This is a competitive space. Hamming already pitches policy-violation red teaming of bank agents with multilingual scenarios and CI.

Full competition notes (8 competitors)

This is a competitive space. Hamming already pitches policy-violation red teaming of bank agents with multilingual scenarios and CI. Giskard sells multi-turn agent testing to bank compliance teams. Generic simulation tools like Okareo, Coval and FutureAGI cover CI gating. So the CI gate idea is basically a commodity feature and won't stand alone. The narrower gap is the policy-to-test generator done as an audit artifact. That means taking a bank's written fee, confirmation and privacy rules and producing labelled trajectories tied to specific clauses. It also means translating them faithfully into the bank's actual customer languages, including US Spanish with code-switching, and reporting results by language: the same scenario passes in English but flips in Spanish, whether in the agent or in its guard. None of the vendors I found clearly ships clause-traceable policy coverage with differential results by language, packaged as evidence for model risk management (SR 11-7 style) and fair-lending or UDAAP reviewers. That buyer cares about language parity because of disparate-treatment exposure. A new entrant could win by owning that compliance-evidence framing and a curated banking policy and translation corpus, and by selling to model risk teams rather than engineers. The risk is that Hamming or Giskard add a "language parity report" as a feature, so the moat would have to come from domain-labelled data and regulator-ready reporting rather than from the test harness itself.

  • Hamming AI

    Demoed at FinovateFall 2026. Red-teams bank voice and chat agents for policy violations, data leakage and authentication failures. Generates scenarios in multiple languages and regional variants (https://hamming.ai/product/automated-testing/scenario-generation) and markets CI/CD integration. This is the closest direct overlap with both product ideas.

  • Giskard

    Evaluation and red-teaming platform sold to banking and insurance compliance teams. It generates test cases from a knowledge base and from agent descriptions, with a bank support agent as its own example. Hub 3.0 (Sept 2026) added multi-turn scenarios with checks on individual turns. It also published a red-teaming benchmark built on a banking assistant. I didn't confirm that it turns individual policy rules into labelled trajectories.

  • Aveni Agent Approve

    Pre-production testing for financial-services agents. Runs synthetic personas and scores conversations against an FCA-aligned conduct and Consumer Duty taxonomy. In early access. Focused on the UK, and I saw no multilingual angle.

  • Cekura

    Voice agent testing with explicit language-plus-accent pairing (for example, Spanish with a Latin American accent) and code-switching. Not specific to banking or policy.

  • Enkrypt AI

    Agent red teaming that supports multilingual agents and maps results to NIST, OWASP and the EU AI Act. A general security tool rather than a fee or confirmation policy auditor for banks.

  • Okareo / Coval / FutureAGI / Maxim (agent simulation tools)

    Generic agent simulation and regression tools with CI hooks, marketed to fintech. These cover the CI gate idea as general infrastructure, without bank policy content.

  • Gradient Labs

    Builds AI agents for financial services and publishes guidance on staged evaluation involving compliance teams. Probably a builder that does its own evals, not a third-party auditor.

  • Sierra tau3-bench banking domain / MAPS benchmark

    Open benchmarks. Tau3-bench has a banking domain with 97 tasks over 698 policy documents, in English only. MAPS (https://papers.lunadong.com/paper/7069) extends agent benchmarks into 11 languages and shows that non-English input causes wrong transfers in a banking example. Academic work like FraudBench and ReguSim also probes policy-grounded financial agents. Together these validate the problem and supply free building blocks.

Checked 2026-10-17

Risks

  • Model risk sales cycles can run longer than the 3-month horizon
  • Results depend on translation quality and on realistic phrasing in each language
  • Agent vendors may bundle multilingual guard testing themselves

Strong team fit and buildability; market pull is the weak point (6).

tech 7 · pull 6 · space 7 · fit 8 · build 8

Exposed

SOFICHYMDAVEOPRT

Companies that could benefit or be threatened. News and context, not investment advice.

Momentum of its main topic

168 developments this week +53 vs last week
21 Sep: 0 developments22 Sep: 0 developments23 Sep: 0 developments24 Sep: 0 developments25 Sep: 0 developments26 Sep: 0 developments27 Sep: 0 developments28 Sep: 0 developments29 Sep: 0 developments30 Sep: 0 developments1 Oct: 0 developments2 Oct: 0 developments3 Oct: 0 developments4 Oct: 0 developments5 Oct: 0 developments6 Oct: 0 developments7 Oct: 0 developments8 Oct: 32 developments9 Oct: 26 developments10 Oct: 13 developments11 Oct: 11 developments12 Oct: 14 developments13 Oct: 19 developments14 Oct: 24 developments15 Oct: 35 developments16 Oct: 31 developments17 Oct: 15 developments18 Oct: 14 developments19 Oct: 23 developments20 Oct: 26 developments
Stage: Coverage

Sources

  1. PROBE: Learning to Audit Policy Compliance in Tool-Using LLM AgentsarXiv
  2. Language Is a Security Surface for Agent GuardsarXiv
  3. Citi becomes latest US bank to restrict AI agents from accessing accountsFT Markets

Status history

  • 2026-10-17 Flagged as buildable