All Episodes
Agentic Commerce #15November 19, 2026·34 min

Giving Agents an Identity So They Can Pay

Sponsors

VisaMesh

Show Notes

On Ep. 15 of Agentic Commerce, Simon Taylor, Founder @ Brainfood & Market Dev @ Tempo and Bam Azizi, CEO & Founder @ Mesh are joined by Pat Kinsel, Founder & CEO @ Proof to discuss why KYA and KYC alone cannot establish legal authorization, comparing Google, Shopify, Visa and Mastercard's agentic commerce protocols, how x401 uses verifiable credentials to authorize agent transactions and more!


Timestamps:

  • 00:00 Introduction
  • 04:00 Deepfakes, cybersecurity threats and identity challenges in agentic commerce
  • 04:59 Why KYA and KYC alone cannot establish legal authorization
  • 06:23 Comparing Google, Shopify, Visa and Mastercard's agentic commerce protocols
  • 10:44 How x401 uses verifiable credentials to authorize agent transactions
  • 15:07 Why financial institutions block AI agents and need secure access
  • 17:06 Intent mandates, step-up authentication and legally enforceable transaction evidence
  • 19:39 Stablecoin micropayments and combining identity with payment authorization
  • 23:36 FinCEN guidance, trusted credential issuers and identity verification liability
  • 28:09 Delegating agent spending authority through signed mandates and revocable credentials
  • 30:16 Implementing x401 through Cloudflare and transaction-specific authorization policies

Tokenized is sponsored by Visa
A world leader in digital payments, Visa is bridging the gap between traditional financial institutions and innovative blockchain networks, helping players in the payments ecosystem navigate the ever-evolving world of tokenized fiat currencies with confidence and ease. Learn more at visa.com/crypto.


Tokenized is also presented by Mesh
As the first global crypto payments network, Mesh makes it possible for anyone — or any agent — to pay or get paid instantly, from any wallet, on any chain, anywhere in the world. Learn more at meshpay.com

***

We’d also like to remind you that the views or opinions of our contributors today are their own and do not necessarily reflect those of the companies they are representing. Nothing we say should be taken as tax, financial, investment or legal advice, do your own research!

 

Music by Henry McLean

Transcript

Sy Taylor  0:10  
Welcome to Tokenized, the show focused on stablecoins and the institutional adoption of tokenized real-world assets. My name is Simon Taylor, head of market there at Tempo, author at Brainfood, and of course, back once again with my agentic commerce co-host Bamazi, founder of Mesh. How are you doing, sir?

Bam Azizi  0:28  
Good, good. Excited for this episode. Thank you, Simon.

Sy Taylor  0:31  
I'm excited too because joining us today is Pat Consel, who is founder and CEO of Proof. How are you doing, Pat?

Pat Kinsel  0:37  
Good. Excited to be here.

Sy Taylor  0:38  
I'm excited to have you on because we are talking about not x4 or two no no no x4 101 which does sound like some crazy X Men reference but it's even more interesting than that quite possibly.

Pat Kinsel  0:51  
I was going to make an eight minute abs joke versus five minute abs. So

Sy Taylor  0:55  
yeah, yeah. Now you got me thinking about something about Mary, which is a great reference all the way along. But before we get into all of that, I've got to remind viewers and listeners that views and opinions of our contributors today are their own and might not reflect those of company they represent. And please don't take anything we say as tax, legal, or financial advice. And of course, this series is brought to you by Visa and our friends at Mesh. This episode is brought to you by Mesh, the global crypto payments network. Mesh makes it possible for anyone or any agent to get paid or pay instantly from any wallet on any chain anywhere in the world. You can learn more at meshpay.com. Hi, Pat. Since you're here, you co-founded a company called Spindle, which Twitter bought back when they were called Twitter. Do we call them the OS, as formerly known as these days? And then you founded Notarize in 2015, and Notarize became Proof in 2023. So, tell me about that journey from where you were to where you are?

Pat Kinsel  2:01  
Yeah, I actually even before starting Spindle was at Microsoft, and at Microsoft really did two projects that are noteworthy. One, Docs.com, which was a collaboration with Facebook, and we were actually their launch partner for Facebook Connect and what they called granular data permissions. And so this identity thing going all the way back to Docs.com, and then I built a search engine internally for Microsoft on top of Twitter and Facebook data. So Spindle was an extension of that. Built a search engine, sold it to Twitter. You missed that I was the lead investor in Drizzly. So Drizzly was an alcohol commerce company sold to Uber, and that's relevant because a lot of identity issues, a lot of regulatory issues associated with Drizzly, so I got that exposure. And then ultimately, when Twitter went public, I had to get a document notarized, and I went into a notary. Notary screwed it up. It was a huge pain in the butt for me, and that really set me off on someone's got to got to solve this problem. So it's been about 10 years now, and really, what we've done is we've gone out and digitized transactions, changed regulation, and figured out how to authorize things with full legal effect. And that is very relevant in the age of agentic. That's the problem everyone's trying to work on.

Sy Taylor  3:15  
So talk to me about where we are now. Right, everything's agents. Everybody's worried about it. Everything I'm seeing, there's a new report by Visa saying 50 of the time it works every time with agentic commerce. They're they're struggling to even buy the right thing. What do you see as the core problems that that agents are having, and where are we at in this evolution of the whole space?

Pat Kinsel  3:40  
Yeah, I think even to broaden the context more than that, I mean, you got to go back to COVID, and COVID forced the world to go remote, and so all these institutions now 7080, 90% of all of their customer interactions are remote and digital. After COVID comes deep fakes and this idea that you can't trust who you're you're doing business with on the other side of any transaction, and so agentic is really just the the full expression of that challenge. You you now don't know if it's a deep fake. You don't know if it's a human on the other side of a transaction that's explicitly authorized something. And also, let's talk about Project Glasswing. You have these major you know financial institutions that are under tremendous threat from cybersecurity, and so I think they're struggling across the board to have confidence and certainty in who they're doing business with, and exactly what their customers are authorizing them to do.

Bam Azizi  4:33  
What's the role of KYC and KYA on on the agent e-commerce side?

Pat Kinsel  4:39  
Yeah, it's so funny. KYA to me is just about bot detection, effectively, right? And a lot of people are really focused right now on KYA to filter traffic. They want to know that it's an agent that's actually hitting their services. But then what? You know, how do you actually create a channel where the agent can do something? And to me, that is where not just KYC, but intent mandates and legal authorization come into play. And I think again, so much of the world is focused on agentic commerce. You know, the event that with Simon we co-hosted in Las Vegas was about it's bigger than the buy button, right? Every industry is having these challenges now, whether it be mortgage, retirement, auto, wealth aren't simple purchases of $500 shoes, right? These are highly regulated transactions with real legal obligations and compliance requirements, and that's where we're very focused is on on full legal effect, right? How do you actually, you know, meet all of the industry obligations and still provide a tremendous customer experience out of these platforms,

Sy Taylor  5:41  
so talk to me about that a little bit more because there's an alphabet soup of protocols coming out the woodwork. I think Decagon has one for something, and then the guys at Sierra worked with Messer and a bunch of other companies. Just talk to me about that alphabet soup of protocols and where you think what you guys are doing fits into all of that?

Pat Kinsel  6:03  
There's always been an alphabet super protocols, right? And you know, a lot of this stuff we've been working with Google and Visa on for two and three years, and that was just the tail end of five and 10 year processes through FIDO and other institutions around identity, right? And so again, this is just this sort of sudden, dramatic expression of challenges on the internet, which is how do you know it's your customer? How do you create an authenticated session? You know, how do you assign intent mandates? And so, the way that I see sort of this all playing out is, you know, Google has been very focused on, you know, AP two, which is how do you sign, you know, a payment instruction. Shopify with UPC has been focused on how do you express your catalog, right? So if you're a merchant, how do you actually express and have your catalog indexed? Visa with Tap is basically a you know how do you register the agent? Mastercard with fair viable intent is how do you you know sign a mandate? When you look at all of those protocols, they all ask a key question, which is that someone has to issue the trusted keys to the consumer, and so that's where proof comes into play. Is that irrespective of what is being authorized, how do we make clear that Simon actually authorized this transaction, and otherwise we're carrying the rest of these protocols forward? So you know what Sierra came out with with PAP or PAPI is really a form of authentication. So for read-write access, right? In financial services, I would make the point or highlight the fact that you can't sign into the bank with you can't create an account with Google Auth. I can't go to a new bank and just sign in with Google and get an account. And when I need to do a wire, the fact that I'm signed in isn't enough already, right? They have additional step ups. It could be SMS OTP. It could be an MFA experience coming back through their apps. Could be something you sign. Could be something you notarize, and that's really where proof comes into play. Is is going passed off into the full legal effect of these transactions.

Bam Azizi  7:59  
So you said like about bot detection. Do you think after we decided, okay, this is an agent. Now I want to know that agent. Do you think there is a link between? It's going to be a link between KYA and KYC. So I know it's an agent, but next step is like who is the user behind the agent and what are the roles and responsibilities that the agent has? So, if something goes wrong, then the user is basically is not going to be on the hook from like legal standpoint. I

Pat Kinsel  8:30  
think that's exactly right. I mean, again, look, KYA has a lot behind it. I mean, one is like a nationalistic cybersecurity thing, right? And knowing these aren't Chinese models, or so. How does a merchant or relying party know this. For example, is an OpenAI ChatGPT versus Claude versus you know whatever. Two is model performance. I mean, some models are going to be better at carrying out users' instructions versus not, right? And so that's as Visa just came out with with their benchmark. It's going to know that this Muse model is actually good at following customers' instructions versus others not, and so KYA is important for a lot of those reasons around model performance and accuracy. You alluded to this fact, but ultimately taking on some responsibility for that. If you have a signed intent mandate from a consumer, so I hey, this is Bam. He told me to buy five green shoes. I have this explicit payload authorizing that transaction, but the instruction that Muse sent was for green shoes. Well, that's Muse not you know operating successfully. You can figure out who screwed up in that chain, right? So yes, you know KYA plus our version of KYC, which which by the way is can be privacy preserving. It's not always the point to actually share someone's personal information. It's creating this strong cryptographic link between what they've authorized and the fact that you can chain to a person. Right? They come together. They compose.

Sy Taylor  9:54  
And then on that, it's probably worth explaining x4 101 and your vision for how you link a human to. To its agent and to those intents, because that whole space is like this new language. Everybody's trying to figure it out. So, really help me get what x4 101 is and and explain it in the context of I've asked my agent to do a thing on my behalf, and how is that legal consent followed from me and proof of who I am to the agent and proof of who it is and the intent all the way through.

Pat Kinsel  10:24  
Yeah, so maybe before 401, I'll explain what we do for credentials. It's lock and key, right? And sometimes it's easier to understand the key than the lock. And so at Proof, what we do is we verify identity to a high legal standard IL two, and we issue verifiable credentials backed by our own certificate authority, and so these are credentials that can chain all the way, right? So you understand the the cryptography and the policy, all the way from the credential back to the issuance, storage, access management, revocation, all sorts of things like that. It is equivalent to the EMV chip in someone's credit card, right? So if you think about the transformational benefit of a of card present transactions versus card not present transactions, that's attributable to the chip. So we're giving the same equivalent chip to transactions, and it supports transaction signing. That's that's a critical distinction, right? So the ability to take a payload, it could be buy this for me, wire this for me. Add a beneficiary to my account. Yes, I agree to borrow this money. You can actually cryptographically sign that payload with someone's unique key, and so I know it's tamper evident. It's chained to you. You you sign this thing, right? And so that's what proof credentials solve. x4 101 is a way for a website to very easily gate any resource, and so it could be access to a system, it could be to trade something, you know, could be what we announced for collaborating with Circle on, which is actually sign, you know, stablecoin transaction and agentic transactions, whatever, and to actually say what's required, and so you can say for this transaction, I need a verified ID. I need an email address, address, whatever it is. You can specify what you need, and then you can say what credentials you're going to trust. So you could trust proof, but it's an open protocol. So you could you could say that you want to trust someone else that meets the specification. That agent hits the site. It gets blocked. It reads x4 101 and understand what's required, and then it can, you know, query the consumer, access the credentials, sign the transaction, and then agent to agent can move forward. So we're huge believer in this future that agent to agent there's going to be many, you know, much larger share of global commerce, and this really allows for machine identity.

Bam Azizi  12:40  
Makes sense. The x4 101 existed before, or it is your invention.

Pat Kinsel  12:45  
I guess you could say it's our invention. I mean, it's it's inspired by other great work. I mean, so x4 102, you know, Coinbase and others that have carried for it. So it's 402 because HTTP protocol, you know, status codes already had 402 for payment required. 401 was already authorized, unauthorized, and what we would say is that the internet was always intended to have an identity protocol and an identity layer. It's just no one ever did it, right? And so modeled after what they did, so we've created this and designed it. We had some great design partners that gave us feedback, and we've now submitted it to FIDO as an open protocol.

Sy Taylor  13:20  
And round out the vision for x4 101 for me. What problem is that going to be able to solve in this new world in which we're trying to make agents be able to do things with with some link back to the human?

Pat Kinsel  13:34  
Yeah, I mean, right now, again, we're spending a lot of energy in stablecoin space. One of the benefits of market clarity there is that real financial institutions are engaging, and so they need identity that actually satisfies their compliance obligations. We're spending a lot of energy there. We're spending a lot of energy with large banks, financial institutions, insurance companies, wealth management firms. They want to open up agents as a channel. You know, if you go read any of these sites, they say they meet their strategy is to meet customers where they are, right? So their customers are in Muse and they're in Chat GPT, and they want to enable these experiences. And so we're we're walking down the path of enabling those scenarios. A lot of exchanges, and so we're having folks taking a dependency. You can put an API behind x4 101, not just a website. So thinking about how you know it can require signed identity, you know, presentation inside of an exchange. So it's really it's flexible. There's there's tons of stuff that's going on.

Sy Taylor  14:33  
I'm excited to learn more. I'm kind of interested in how it fits into this whole narrative at the moment about the whole. Some companies are blocking agents. Some are trying to like build them an MCP. Like, what was your perspective on all that? The

Pat Kinsel  14:47  
whole blocking agents thing. What do people expect? Right. Like, if you're a regulated financial institution, again, I mentioned Project Glasswing earlier. You're getting hammered right now by cybersecurity issues. You know, a lot of large banks are dedicating huge percentages of their engineering resources to just like battening the hatches down, right? And all of a sudden, this thing comes along that is breaking all of your security, you know, policies. So, look, I've sat in some rooms lately with some of the largest banks where, if you think about their model risk governance and their their various policies and control surface area, like they're actually extremely sophisticated with how they're thinking about this, right? End to end, who's responsible for what? So a lot of work on sort of the legal frameworks around this sort of stuff, and most of the people are are actively working to create happy paths. I think what people should understand is these agents, like you may block them on your website, but they know how to make phone calls, so they're calling the call center and they're pretending to be your client, which is an even worse problem. And so, most people recognize that they have to create happy paths. Those happy paths have to enforce real identity authorization policy, and that's the right end state. And so, we're working with many of the people that have said that they're not allowing this, they're trying to figure out how to. I

Sy Taylor  16:04  
wonder who some of those might be.

Bam Azizi  16:07  
So you're saying that instead of like blocking or giving full access, there should be something in the middle that's more granular, right? So, and when I was working identity, there was a concept called AAA, like authentication, authorization, and accounting. So authentication is obvious, like you authenticate the username pass or your phone number. Then authorization shows like what level of access your agent can have, and then the accounting is the session time, right? So how long you have that access in that level? Do you guys have similar like type of mechanism built for x4 101 for the agentic commerce.

Pat Kinsel  16:46  
Yeah, I mean, and it's again, it gets into our our verifiable credentials. I mean, the thing about being a CA, so a certificate authority, is you have to publish your policies. So we have a published, you know, certificate practice statement and things like that, and it goes into how identity verification is done, how access is granted, and reauthentication occurs, and it's very transparent. And so, in the PKI world, you have things called OIDs, right? So it has to do with, you know, a time of transaction. Was it cashed? You know, did it require a biometric? Did it require a full step up? And so, a lot of regulated industries may have a specific policy that's required, right? Like, if you're going to do a mortgage, right, or anything that touches those types of transactions, you have to collect identity at time of transaction. It doesn't matter, you know, what level of efficiency people want to provide. I think from your, you know, AAA, what's missing and what's required in this agentic world is the intent mandate, and so we talk a lot about verifiable evidence. If you think about, for you know, payment geeks out there, compelling evidence, right? Dispute frameworks. What can you go and request? What data you get? Does it stand up in court, right? And that's so much of what our 10-year history is, you know, producing a digital transaction that stands up in court, you know, that doesn't create some new liability bomb for industries and allows them trans to transact with full legal effect.

Sy Taylor  18:13  
Let's avoid those liability bombs as much as we can. I'm going to do my best as well to avoid angering our sponsors. So we'll take a quick pause here while we hear from them. Stablecoin operations usually mean a wallet from one vendor and on-ramp from another, and then controls stitched together across all of them. Visa's stablecoin platform fixes this fundamentally. You can mint, move, and manage stablecoins across OpenUSD, and you remain your own custodian, all in one single environment. Then, stablecoin linked cards let you spend balances anywhere Visa is accepted. That's Visa, the global leader in payments, and of course sponsor of this show. You can find out more@visa.com forward slash crypto. All right, thank you to our sponsors, Pat. You've been doing some stuff with x4 101 and x4 102 as well. So, talk to me about the stablecoin land. We are on tokenized after all. What's your exposure to that be?

Pat Kinsel  19:19  
I'm thrilled with the state of you know where things are with with stablecoins, the industry at large, you know Brian Armstrong came out and he says that he thinks that crypto and stablecoins will be the payment rail for agentic, and I agree completely. It's funny in our history, I was never asked to put anything on a blockchain in in 10 years, despite you know digitizing real estate and retirement and all these industries, and we've seen a total change in interest in how we can interface with the crypto industry because of stablecoins. And so, really, it's two-sided. So, one is we now accept payment ourselves, you know, over 402 with MPP coming. And really, if you think about this, if you want. Don't allow machine transactions. They're not going to go negotiate an enterprise license agreement. They're not going to make volume commitments. They want to have micro payments, and they want to basically enroll and pay at just just in time. And so it's not just that we're accepting 402 MPP. It's that we're allowing someone to register at the edge for our service. And so there's a really easy way for someone to put basically code on their site, which makes them a relying party for our credentials at time of transaction, and so that they can do this without signing an agreement and pay as they go. That's critical. And the second thing is thinking about how they can run side by side, right? And so how you actually have one authorization that includes identity and payment, and so industries can really unlock agentic commerce and commerce broadly, not just you know paying for things with a credit card, but know who someone is, know that they can pay through those rails and those things coming together. We think is the great unlock. Do

Bam Azizi  20:56  
you see in your vision? Do you think blockchain, besides payment, is a good ledger for identity in a decentralized way. So I can have my identity and I have my private key, so I can sign requests. So proof that basically I am BAM as easy. Do you think those type of project will come to fruition at some point because of the payment use case?

Pat Kinsel  21:18  
Such a loaded question. I look. I think it's an evolution. I mean, verifiable credentials live on device at the edge, right? And so it's already in our implementation. You already are storing, you know, a portion of your identity at the edge. The reality, though, is that regulated industries still require the collection of data, and so our vision and plan is that you first have to convince people to rely on a verifiable credential. You then can talk about zero knowledge proofs and what's what's required. If you have someone that is basically attesting to the process having been performed, taking on liability and risk associated with that, you can start to talk about there not being an exchange of PAI, but we see it as a phased approach to get to that point. And then also in our design for 401 in our scheme, we do account for there being other issuers, right? And so it's not unlike the payment networks where you have open standards, open protocols, you have governing associations that you know manage a lot of these things. Then you have people that operate networks on top, and those networks win based on their efficacy and scale. We see the same playing out for identity.

Sy Taylor  22:27  
Yeah, identity networks are really interesting idea. For the simple fact that I think on a lot of the decentralized identity stuff is probably built in a vacuum, unaware of how decentralized verifiable credentials are, and the legal definition of identity is when a government identifies you and says they they sort of point the finger at you and say that's Pat, and so you're looking for that non-reputable true at source token, that PKI verifiable credential that came from a government source and also another issuer of identity. If you can triangulate these things, then what do I need to put them on a blockchain for? I think is a fair question. Or maybe I want to build a marketplace of that, and their blockchains might be might be helpful and suitable for things of that nature.

Pat Kinsel  23:16  
I think you just hit on a couple really important points that people should understand. So one, verifiable credentials can be copied, right? And it's literally it's just a format for the expression of data. Like I, on my computer right now, can generate a verifiable credential that says I'm you, Simon. Like I can take your name and your address, and I can create a verifiable credential. So the question is, who issued it, and do you trust the person that issued it, and can you prove that it was that it's been unaltered since it was issued, and and and and that is why we also built a certificate authority and why we sign our verifiable credentials with our CA, because then you know okay here's this credential that I have, it meets the standard in terms of presentation of data, and it was issued by a company called Proof, and I can see all of the policy and cryptography from the moment of issuance to the moment of of presentation. We think that is critical, and not all verifiable credentials are the same. Then you get into transaction binding and signing. I think it's also important for people to know this is why the FinCEN guidance that came out is such a big deal. FinCEN came out and said for the first time ever that a private issuer of verifiable credentials can be used in KYC SIP and not just a government-issued identity. You know, people talk a lot about MDLs, and we really see two core issues. One is enrollment. There's just not a lot of people that have MDLs, and so how can you do just-in-time enrollment? It's been a big focus of ours. You're in Muse and you're trying to get a prescription from Amazon Pharmacy. Hypothetical, you got to be able to meet it right here, right now. And then the second thing is liability. Like you cannot go back to the state and say you're liable for this transaction, right? And so. That's where we think a private network that sits and manages these standards is critical to advance all this forward. I

Sy Taylor  25:07  
think mobile drivers licenses (MDLs). Yeah, I don't know how many states they're available in. Is it four now? Maybe six? Something like that?

Pat Kinsel  25:15  
No, it's it's. I'm going to forget the number, but it's more than that.

Sy Taylor  25:18  
Okay, but the amount of people that actually use those as well versus having the physical driver's license is is kind of few and far between. The amount of people that have a bank account have been through some form of KYC though is is kind of enormous. And so, if I've taken you through that identification process, why shouldn't I monetize that? People want to be able to verify identity, and they want to identify it from a brand they've heard of and they trust. So, being able to do that is really, really hard. But to your point, liability. Do I want to be exposing myself to that liability? I think that's always been a bit of a hard question. But the FinTech guidance said, "Look, this is something that we expect that the market will develop." So I'm so interested in how that continues to evolve over time, and you know what you're seeing from your early customers, like who's adopting this now, and what are the going to be the use cases?

Pat Kinsel  26:05  
Yeah, so we have you know nearly 10,000 businesses on our platform. That was one of our advantages, as we have all sorts of industries doing these highly regulated transactions on our platform. We've done more than a trillion dollars of volume in our history, and so our initial challenge was how do we issue a credential that can just be used by our own customers? So these are wealth management customers, retirement, typically associated with large flows of funds. And so someone is withdrawing, you know, $160,000 out of their retirement account. And so it has to be valuable, right? So it's not, hey, here's this cool fancy tech. It's, hey, better customer experience, better security, higher conversion rates, right? Those are the ways that you can deploy credentials into these into these workflows, and then the fact that it ultimately creates a network is, you know, an artifact that comes, you know, at a later date, and that's really been our strategy. One

Bam Azizi  27:01  
question about the you said you were excited about agentic to agentic type of transaction. So agent to agent is going to be bigger than agent to humans or human to agents from like volume perspective at some point. And the reason is very simple. Like we have 5 billion users connected to internet. You will have hundreds of billions of agents connected to internet. Human, they do two to three transactions per day. Agents are doing 1000s of transactions per second, so it's really not hard to kind of calculate the math that agent to agent would be bigger. But what I'm hearing from you is identity could be here the bottleneck. So if every time that there is a transaction, I need to kind of ping my human to like approve my transaction. Would that slow down the agent to agent transactions?

Pat Kinsel  27:49  
Yeah, but you don't need to. I think that's what's critically important. I mean, like a couple things. Like one of the ways I've sold our product at points in time is to basically say to someone in IT, "Hey, imagine if you know a third-party service doing an API integration didn't use you know TLS, and you allowed unsigned instructions in your organization. And they're like, like I would never do that. And I said, well, that's what you do with every person that you are interacting with, right? They're signing things, they're submitting things. You have no idea who it is. What if you could bring people into the same security paradigm of the web as machines are, and that's really what we've done with PKI and and verifiable credentials, and then everything else is policy, right? So if you're going to allow someone to delegate access or authority, is that how long should that be lived, right? And from an intent mandate perspective, you know, hey, when the Taylor Swift concerts, you know, drop under $500. Buy them for me. A lot of commerce is not is not point in time, right? It's no different to how a merchant you know stores a payment credential, right? It's tokenized. It has a caching policy and a replay policy. There's, it's just policy, right? I think what's critical though is let's just say you hit a gate, and that business has a real compliance obligation or a fraud concern. You know how do you then mitigate that, right? How do you step up so much of credit cards? Now, just think about this. Like, you know, my Amex, for example, I get an alert that it was used, right? I have a centralized place to go and see the transactions that I've authorized. I can revoke access to credentials, right? And it's all the same concepts for identity are are required and are we're moving toward.

Sy Taylor  29:28  
Pat, if people are trying to get their head around, hey, I'm expecting some agent traffic. I'm already seeing some of it. You've talked about the the CISO angle. You've talked about you know kind of people on on that side and building happy paths, how would they get started if they wanted to talk to you? How would they implement like an x4 101? How would they work with your certificate authority? Like, how would you advise them to just get control of this agent traffic that's coming at them right now?

Pat Kinsel  29:56  
What's happening right now is everyone's focused on detection. And then they're using that to just try to get a handle on the situation and effectively shut it off. Now they're dealing with call center. That's where the traffic has shifted, and so we have a bunch of tools. Almost all of our customers start in call center, and so we have a lot of tools to think about how to get someone into a secure identity posture out of the call center. But when it comes time to start to actually open up to agentic traffic in real and supported ways. You know, we deployed Cloudflare workers, and so more than half of our customers, for example, on Cloudflare, they can one-click deploy this thing in Cloudflare. And I think something that is relevant to what you brought up earlier, Simon, around liability is we have transaction templates, and so in payments, think about MCC codes, right? They treat going to a gaming site differently than buying a sandwich, right? And so, we have these transaction templates that allow someone to start to authorize individual use cases, start to define the identity policy and interaction model around those those individual use cases. And so, a lot of what we're doing right now is trying to create industry alignment, not just around this broad concept of agentic authorization, but talking about specific use cases, what data should be exchanged, with a focus on data minimization. So we're not sharing too much information. What specific intent mandate needs to be signed? How does it carry KYA, KYC, the intent mandate. What's the step up policy associated with this? All of it, right? And that's where we're working with our customers to walk down this path. And so, to me, it's pick a use case, right? You know, robots.txt, right? Like ultimately, people putting skills files and agents files on their site. They're publishing what they will and won't do. One things I found. This is an aside. Is it's so interesting. Like we publish, you know, 401. I ask Claude and ChatGPT questions like, "What's a leading agentic protocol?" It'll pick 401. But then when you ask it about use cases, it doesn't always land. And the reason is because people have to actually express their intent. Like it's amazing how these agentic systems understand intent, and for a site to simply in an agent's file or skills file say, "Hey, we are working to enable, right? And here's a place where we are willing to start." It's amazing how these agents will figure it out and start to respect where you want your traffic to go.

Sy Taylor  32:17  
Hey, agent, I would like you to do this thing. Is a surprisingly powerful way to greet them. I often describe a lot of what we need to do is just build really good handshakes. There's so many customs for humans to greet each other in various parts of the world, and we learn each other's customs. We should probably learn the customs of agents. So, Pat, if people do want to get started, where do they go to learn more?

Pat Kinsel  32:38  
Just go to proof.com/x401. We're all over the internet, so you know we're working with a ton of customers right now. You'd be surprised, like we can get this stood up in a matter of a day or two if people want to POC it, and it's in production, so like people can do this right now.

Sy Taylor  32:52  
All right, that's awesome. Thank you very much, Pat, and and that brings us to a close for today. So, Bam, why don't you tell me where people can find out more about you and everything you're doing at Mesh and all of your really spooky ghost cards.

Bam Azizi  33:03  
Yeah, you can go to meshpay.com or find me bam at zmesh on X or LinkedIn.

Sy Taylor  33:08  
Yeah, you'll find me at sy Taylor on all of the socials at bringfood.xyz screaming into the void, and of course at tempo.xyz as well. Just making top-level domain names that are hard for corporates to get access to, as always, and you'll find a lot more of this show if you hit the subscribe button. And I think for conversations like this, it was well worth your time, gentlemen. Thank you very much, and we'll catch you next time.