[
  {
    "startMs": 12920,
    "text": "Anyone here ever get tired of clicking approve on their coding agents, giving ChatGPT the permission to be able to scrape that website? Or even just giving Hermes the ability to be able to read your-- the MCP that you definitely told it it's allowed to read. Anyone in the room get annoyed?"
  },
  {
    "startMs": 32780,
    "text": "I."
  },
  {
    "startMs": 32820,
    "text": "True. Now imagine that was the experience every time you were using an assistant that promised you to save you time, reduce the complexity in your life, and ultimately provide you value. Everyone in this room, the AI evangelists of the world, we promised our normies that are sitting outside this room the-- an assistant, something that's going to reduce the complexity of their lives. But instead, when it hit reality, we ended up providing them with a queue of requests."
  },
  {
    "startMs": 64780,
    "text": "So, hi, I'm Emil. Um, I lead, um, data and AI product at Wise. And I'm gonna be talking you guys through about how we're thinking about removing that complexity for our users and trying to give an agent useful autonomy without making our customer the API. So for those of you who aren't familiar with Wise, um, which I expect some of you might not be given the US-based audience, um, we're a technology company that's building the best way to be able to move and manage the world's"
  },
  {
    "startMs": 94560,
    "text": "money. We have this vision of achieving money without borders and making sure that people can manage their funds and lifestyle across multiple geographies and currencies. To do that, we've built three products. We've built the Wise Account, and that's helping regular people manage their life across borders, helping them spend like a local and save like a local. The second is Wise Business, which allows businesses small and medium-sized to be global from day one."
  },
  {
    "startMs": 125100,
    "text": "And the last is Wise Platform, which allows banks and other financial institutions to tap directly into the payments infrastructure that we've built over the la-- since twenty-eleven and provide a Wise-like experience directly to their customers. And to do this, we've built one single global payments network powered by over ninety different local banks and pay-payment providers from across the world and connecting directly into domestic payment schemes."
  },
  {
    "startMs": 153900,
    "text": "And that network has proved really effective. Last year, we've moved over two hundred and forty-three billion in cross-quarter-- in cross-border volume, and we're serving over, uh, just nearly nineteen million active customers. So we know this, this, this model scales."
  },
  {
    "startMs": 173780,
    "text": "And to be able to do that, we hold more than eighty different licenses worldwide."
  },
  {
    "startMs": 180960,
    "text": "And that has meant that in different currencies, different countries, different regulated entities, and different products all bring different requirements. And that doesn't disappear when we put a chat bar in front of it, unfortunately. Our regulators still expect us to know what a customer is authorized, control what happens to their money, and explain the outcome."
  },
  {
    "startMs": 204320,
    "text": "So how can we give an agent useful autonomy that is actually going to simplify our user's life and still answer for what it does?"
  },
  {
    "startMs": 216020,
    "text": "So here's what a typical job might look like that we might give to an agent. So some small business owner might say, \"Handle this week's approved payment suppliers, reconcile the results, and bring back the exceptions to me.\" The business wants the work handled. They don't want to coordinate every lookup. They don't want to coordinate every status check. And they want this to ultimately provide them with the ability to focus on what matters most to them, running their business. So how do we-- so how are we going about achieving-- how are we going about achieving this?"
  },
  {
    "startMs": 245200,
    "text": "This might look very familiar to you if anyone's used an agent relatively recently. You'll have list of different approved steps, checking whether or not you can look up their, uh, the payment account details, checking whether or not you can scan a PDF in to be able to understand the, um, the invoice, et cetera, et cetera. Took eight steps, probably some time in between, to be able to get to something that was ultimately useful."
  },
  {
    "startMs": 272780,
    "text": "And so for the engineers in this room, this might look relatively familiar, right? In the-- If anyone can remember the before times, and if you weren't using dangerously skip permissions, this is what coding agent used to look like. We have to go through and approve every step. We're watching the terminal, check your-- run your tests. Sure. Fetch the-- Fetch the latest documentation from Confluence. Sure. And click Approve all the way through. We ended up having to watch the ter-terminal instead of getting real work handled."
  },
  {
    "startMs": 302940,
    "text": "We ultimately made the human the API. So how did co-coding agent solve this? Anthropic came up with this idea of auto mode, right? And that meaningfully reduced the friction that we experience as engineers. Permission rules, classifiers, sandbox helped be able to introduce controls necessary for us to be able to trust the agent wasn't gonna go delete our production databases. These controls matter. But a payment needs a different kind of answer"
  },
  {
    "startMs": 333120,
    "text": "to a different kind of question. While a coding agent is asking, \"Does this action look safe?\" What a payment is asking is, \"Did this customer authorize this payment to this recipient on these terms?\""
  },
  {
    "startMs": 348500,
    "text": "So again, we're at an AI conference. You might say, \"Cool. Let's, let's chuck some EVLs at it.\" For those of you all on the bleeding edge, let's say we can build a harness to be able to do this and embed the controls inside the harness. That unfortunately doesn't give us the answer to whether or not the customer actually agreed to this job."
  },
  {
    "startMs": 369620,
    "text": "What we need is an agreement. We need something immutable that our customers agree to that allows the agent to operate from within those bounds."
  },
  {
    "startMs": 381260,
    "text": "I was not saying we don't need the evals and we don't need the harness. We're still gonna need both. But w-what we don't want is that the model said this is what the customer wanted and authorizing that payment based on that."
  },
  {
    "startMs": 395460,
    "text": "We want them to agree to the job, not every step."
  },
  {
    "startMs": 402220,
    "text": "So how are we, how are we thinking about this? So the idea is we wanna be able to go from intent to something that is immutable. So we want something to be able to take that, take the vague customer p-prompt that we have, ingest that, have trusted, verified software that we've built, we spent the last twenty-five years building VerifyIt, and show the customer a particular outcome and have them confirm whether or not that is the bounds by which they want the a-agent to be able to operate within."
  },
  {
    "startMs": 433580,
    "text": "We can then take that, embed that into our trusted, the, our trusted stack, and pr-provision the authority based on what the customer agreed to. The agent can then plan and act as usual. Our services, which are actually executing that payment, can then check whether or not the, the payment should be executed on. And the results and exceptions can get surfaced back to the user."
  },
  {
    "startMs": 460300,
    "text": "If something needs to change, and that changes that fundamental agreement, we surface back to the user. But if the, if something is changing that's not going to affect the payment terms, we can still go back and have the agent re-plan. So a different plan can still stay within inside that agreement. Different terms ultimately need a revised proposal and a customer decision. So we need the customer to agree to the job, the agent to choose the steps, and our"
  },
  {
    "startMs": 490320,
    "text": "software to enforce that agreement."
  },
  {
    "startMs": 495500,
    "text": "So let's take a hypothetical example. Let's say Sarah, our business owner from before, sends this off to an agent. What does this ultimately look like? So first, we take Sarah's credentials, and we take the, the, all the setup that Sarah's had, and we go gather the context necessary to be able to propose a job. So first, the agent explores with limited read-only access, all the information necessary to be able to close that loop. The trusted software that we've"
  },
  {
    "startMs": 525000,
    "text": "attached to the account actually resolves the suppliers, the bank details, the amounts from those records, and this preparation doesn't actually give the agent permission to be able to execute anything meaningful. We then surface that to Sarah, and here's the job that she will see. She'll see this is the thing that we wanna be able to do. This is, like, the three suppliers, seven hundred and seventy-five dollars with around, like, some for the fees that she might have to pay. And this is the draft that she will see."
  },
  {
    "startMs": 555100,
    "text": "What also gives-- Wh-what's also important is the bounds in which the agent is able to operate in, so the decisions that she's comfortable offsetting to the agent versus the decisions that she wants to be able to be, um, looped back into. Any missing or conflicting details need to be resolved before the, b-before the job gets, um, made immutable. And so what this means is we have two views of that job. One is the thing that Sarah sees, which is the, is the promise that we're making in human language."
  },
  {
    "startMs": 585580,
    "text": "The second is what our services can see, and that's ultimately a machine-readable promise that we're making that allows our services to be able to verify that this payment is a, is, is operating within a specific set of bounds and gives the agent very specific instructions in what to operate within those bounds. And so when she clicks Approve, that then becomes immutable. She confirms and authenticates, and her decision is recorded against that exact version, and that draft becomes an authorized job."
  },
  {
    "startMs": 618780,
    "text": "What you approve is ultimately what we enforce, and that's how we're thinking about reducing the complexity."
  },
  {
    "startMs": 625960,
    "text": "So what happens next? So we take that c-- we take that confirmed job, and we give a trusted provisioning platform the ability to be able to provision access purely based on what's been approved. The code deterministically checks three things: the confirmed job, what m-- Wise permits the agent to do, and Sarah's current rights. And we look at the intersection between those, along, along with what the job has proposed, to be able to provision limited"
  },
  {
    "startMs": 655660,
    "text": "access rights to an execution agent. Those then split out into two workers. One is a payment worker and a reconciliation worker, and those are what is going to be able to actually execute based on that job."
  },
  {
    "startMs": 670400,
    "text": "This still allows the plan to be able to change. The agent is still deciding how to best achieve the job that has been provisioned for them. What does-- what doesn't is the agreement. And so the flexibility th-that we promised, the ability for a customer to be able to delegate the job instead of supervising that implementation, still remains."
  },
  {
    "startMs": 692340,
    "text": "So there's fundamentally two different loops, and this gives us some element of resilience here, right? So let's say, um, the job needs to be retried for whatever reason. A Kubernetes pod needs to be restarted, and the job or the app crashes on her phone, and she needs to be able to restart that job. Given that that job's immutable and th-- we're sharing that payment state, it's not a second payment. Services will share the ability to be able to, um, execute that payment but also be able to look up what has already been executed. And so the"
  },
  {
    "startMs": 722380,
    "text": "worker follows the existing payment job rather than creating another one. However, if they discover that a, a quota has changed later on or a quota might have expired, surface that back to Sarah 'cause she wants to know. Sarah approved that specific quote, and the agent then will prepare an updated proposal, but can't approve the replacement itself."
  },
  {
    "startMs": 744560,
    "text": "And so we can show Sarah what's changed, get her to agree to a new version, and within that arrangement, the agent still keeps working."
  },
  {
    "startMs": 755400,
    "text": "So this is a rough, like, sketch of what we're try-- of what we've built at Wise so far, is we have, like, our different gateways that ultimately allow for the provisioning of these agents and also the ability to be able to have that immutable job be, be, be verified against our services. We have the very controlled routes to our LLM providers, and we have an agentic gateway, which ultimately provides mechanisms for our tools to be able to, uh, be registered, but also be evidenced."
  },
  {
    "startMs": 785920,
    "text": "So we follow that one payment through the gateway. The worker checks what, what tools it can use, executes that against the payment service, and makes sure that the bounds within they're operating within still comply with the promise that we made the user, that immutable job record."
  },
  {
    "startMs": 805260,
    "text": "But let's say there's some nefarious actions happening, right? So suppo-suppose we get prompt-- we get, it get, it gets prompt injected somewhere, and the, the-- an agent says pay-- our payment details is updated. And let's actually say that the agent actually believes it, right? Its belief itself cannot change the confirmed job. So the new payee fails when the ser-- at, at the service check, and the agent cannot rewrite its own agreement. So the boundary doesn't actually depend on the model spotting"
  },
  {
    "startMs": 835240,
    "text": "the scam. It depends on our downstream services supporting the ability to be able to check those, but also enforcing on what we agreed. So the software stack that we've built over the la-- since twenty-twenty-- since twenty eleven is still the one that we're gonna be relying on, and it's still the one that's gonna be remaining compliant for all of the orders in the room."
  },
  {
    "startMs": 859100,
    "text": "So what can we answer for?"
  },
  {
    "startMs": 862560,
    "text": "We know who authorized the job. We know what the agent can do. We know what happened when that payment went through. We know what we can stop. We ultimately know who, who's responsible, and we know whether or not it's doing good work. And so that one chain of evidence, we get everything we need to be able to allow for our customers to be able to reduce the complexity when using agents, but still make sure that their money is safe."
  },
  {
    "startMs": 891460,
    "text": "So there's one thing I want you to take away from this. If you wanna introduce a new approval flow, if you wanna introduce a new agent into your, like, into your stack, get the customer to agree to the job and delegate it out. Allow your agent to be able to choose how it wants to execute that job, and allow your services to be able to enforce that agreement. And that way, Sarah doesn't have to worry about needing to approve a hundred different steps. So please, stop making your"
  },
  {
    "startMs": 920760,
    "text": "hu-humans your agent's API. Thank you."
  }
]
