WEBVTT - Stripe's John Collison on How Agentic Commerce Will Reshape the Internet

0:00:02.720 --> 0:00:14.000
<v Speaker 1>Bloomberg Audio Studios, Podcasts, radio News.

0:00:18.079 --> 0:00:21.680
<v Speaker 2>Hello and welcome to another episode of the Odd Lots Podcast.

0:00:21.760 --> 0:00:24.080
<v Speaker 3>I'm Joe Wasn't though, and I'm Tracy Alloway.

0:00:24.400 --> 0:00:27.400
<v Speaker 2>So Tracy, another episode where I can mention that I've

0:00:27.400 --> 0:00:30.680
<v Speaker 2>been vib no. But you know, here's something that I

0:00:30.720 --> 0:00:32.240
<v Speaker 2>may have mentioned before.

0:00:32.360 --> 0:00:34.040
<v Speaker 3>I'm sure you have, Joe, but.

0:00:34.000 --> 0:00:36.000
<v Speaker 2>I'm not one hundred percent sure. Okay, I think I've

0:00:36.040 --> 0:00:37.920
<v Speaker 2>mentioned it. It's actually very easy. You just come up

0:00:37.920 --> 0:00:39.519
<v Speaker 2>with an idea and you type it in English and

0:00:39.520 --> 0:00:42.920
<v Speaker 2>then it's there. You know, the hardest part registering a

0:00:43.000 --> 0:00:47.440
<v Speaker 2>domain game. Yeah, so everything else is so smooth, right,

0:00:47.520 --> 0:00:50.280
<v Speaker 2>You just type it in English and then you're like,

0:00:50.479 --> 0:00:52.559
<v Speaker 2>have your little app or whatever, and then it's like, oh,

0:00:52.560 --> 0:00:53.840
<v Speaker 2>I want to put this somewhere on the web. But

0:00:53.880 --> 0:00:56.120
<v Speaker 2>then you go to like a domain name registrar. I

0:00:56.120 --> 0:00:58.640
<v Speaker 2>had been using go Daddy for a long time, and

0:00:58.680 --> 0:01:00.760
<v Speaker 2>then it's like, let's hit this feel for this field

0:01:00.760 --> 0:01:02.840
<v Speaker 2>and this field for this field, and toggle this and

0:01:03.000 --> 0:01:05.320
<v Speaker 2>this worker this page is in the A field and

0:01:05.400 --> 0:01:08.120
<v Speaker 2>the app field of the B field, and I swear

0:01:08.840 --> 0:01:12.040
<v Speaker 2>that's like, it's like so maddening. I just hated it

0:01:12.120 --> 0:01:14.040
<v Speaker 2>so much. It's so annoying. It is the hardest part

0:01:14.040 --> 0:01:14.800
<v Speaker 2>of the whole aspect.

0:01:15.080 --> 0:01:18.120
<v Speaker 3>I have terrible memories as well about dealing with blue

0:01:18.120 --> 0:01:20.479
<v Speaker 3>host and things like that. Is this the first time

0:01:20.480 --> 0:01:21.600
<v Speaker 3>you've ever set up a domain?

0:01:22.000 --> 0:01:22.800
<v Speaker 2>No, there's the thing.

0:01:23.080 --> 0:01:24.000
<v Speaker 4>This is the other thing.

0:01:24.120 --> 0:01:26.880
<v Speaker 2>Yeah, I've done it before, Like I've done it before,

0:01:27.040 --> 0:01:28.600
<v Speaker 2>and it's still incredibly annoying.

0:01:28.840 --> 0:01:31.319
<v Speaker 3>Progress comes slow to domain registration.

0:01:31.880 --> 0:01:34.600
<v Speaker 2>I mean, there's probably good reason for it to be complicated.

0:01:34.680 --> 0:01:36.960
<v Speaker 2>You don't want it to switch in the wrong direction. Anyway,

0:01:37.720 --> 0:01:40.720
<v Speaker 2>I was very excited a couple of weeks ago. There's

0:01:40.760 --> 0:01:43.200
<v Speaker 2>actually well, the two of us were in Madrid. The

0:01:43.240 --> 0:01:46.280
<v Speaker 2>company Stripe, the payments company, announced that there was going

0:01:46.360 --> 0:01:48.880
<v Speaker 2>to be some agreement with cloud Flair, which does a

0:01:48.880 --> 0:01:50.880
<v Speaker 2>lot of web hostings, where you could just have the

0:01:50.920 --> 0:01:53.400
<v Speaker 2>agent buy a domain name for you, and so you

0:01:53.440 --> 0:01:54.840
<v Speaker 2>think of one and you just type it in buy

0:01:54.840 --> 0:01:57.440
<v Speaker 2>this domain name and host it there. And I immediately like,

0:01:57.480 --> 0:01:59.600
<v Speaker 2>oh my god. I wrote about it the newsletter. It's like,

0:01:59.600 --> 0:02:01.600
<v Speaker 2>this should be so, this would have been so nice

0:02:01.600 --> 0:02:02.040
<v Speaker 2>a month a.

0:02:02.200 --> 0:02:04.360
<v Speaker 3>Yet another thing that you will never have to do again,

0:02:04.600 --> 0:02:08.320
<v Speaker 3>exactly let another So, I mean I saw the Stripe

0:02:08.320 --> 0:02:10.360
<v Speaker 3>news and it generated a lot of buzz. And it

0:02:10.400 --> 0:02:13.560
<v Speaker 3>all comes under the umbrella, I guess, of agentic commerce.

0:02:13.600 --> 0:02:15.680
<v Speaker 3>So this idea that you can have agents that are

0:02:15.680 --> 0:02:19.680
<v Speaker 3>actually directly transacting on your behalf with other agents or

0:02:19.720 --> 0:02:22.840
<v Speaker 3>other websites. And I have to say, as someone who

0:02:22.880 --> 0:02:26.320
<v Speaker 3>shops online a lot, this is the first time I

0:02:26.400 --> 0:02:28.919
<v Speaker 3>feel disintermediated by AIM.

0:02:29.240 --> 0:02:34.000
<v Speaker 2>I'm actually particularly excited about this episode because I'm very

0:02:34.080 --> 0:02:38.920
<v Speaker 2>curious basically what you specifically will ask as someone as.

0:02:38.840 --> 0:02:40.480
<v Speaker 3>A person a professional shopper.

0:02:40.680 --> 0:02:44.600
<v Speaker 5>I was going to say, as a person of taste.

0:02:43.240 --> 0:02:47.840
<v Speaker 5>As a person of taste, I've seen you say scrolling

0:02:48.520 --> 0:02:52.160
<v Speaker 5>very nice paper like websites fuck wallpapers and things like that,

0:02:52.880 --> 0:02:55.680
<v Speaker 5>and I'm curious what does it mean for that if

0:02:55.800 --> 0:02:58.680
<v Speaker 5>your AI bought two years from now knows you so well.

0:02:59.000 --> 0:03:01.160
<v Speaker 5>It's like, Tracy, I, I thought you needed this new

0:03:01.160 --> 0:03:03.480
<v Speaker 5>wallpaper because you're doing this, I just went ahead and

0:03:03.600 --> 0:03:05.400
<v Speaker 5>order it to you to be delivered tomorrow.

0:03:05.840 --> 0:03:06.800
<v Speaker 2>This changes the world.

0:03:06.960 --> 0:03:11.320
<v Speaker 3>It brings up so many interesting questions about discoverability and taste,

0:03:11.400 --> 0:03:14.840
<v Speaker 3>as you mentioned, and also just the nature of the Internet,

0:03:14.960 --> 0:03:17.600
<v Speaker 3>because when I think about the Internet, like a lot

0:03:17.600 --> 0:03:20.360
<v Speaker 3>of other things, it's basically built to sell you things,

0:03:20.440 --> 0:03:24.520
<v Speaker 3>whether that's products or information content, and we know that

0:03:24.560 --> 0:03:27.200
<v Speaker 3>it also runs on those sales in the sense that

0:03:27.360 --> 0:03:30.440
<v Speaker 3>a lot of the Internet is driven by advertising, which

0:03:30.480 --> 0:03:33.359
<v Speaker 3>is related to traffic. Obviously, we actually did that episode

0:03:33.400 --> 0:03:36.360
<v Speaker 3>way back about how the Internet runs on millions se

0:03:37.240 --> 0:03:42.080
<v Speaker 3>ad auctions. That's and so this topic of agentic commerce

0:03:42.200 --> 0:03:45.360
<v Speaker 3>and the payment system, obviously it's of interest to anyone

0:03:45.400 --> 0:03:48.200
<v Speaker 3>who shops and does stuff online, but it's also really

0:03:48.240 --> 0:03:51.320
<v Speaker 3>relevant to the actual evolution of the Internet.

0:03:51.400 --> 0:03:53.720
<v Speaker 2>Couldn't agree more and I would go further and say

0:03:53.720 --> 0:03:57.680
<v Speaker 2>it's really important for like culture itself, advertising creation of culture.

0:03:57.760 --> 0:04:00.440
<v Speaker 2>Adds are influential. Ads do all this stuff. What if

0:04:00.440 --> 0:04:02.920
<v Speaker 2>there's a changing and advertise it all these kind of stuff. Anyway,

0:04:03.600 --> 0:04:06.280
<v Speaker 2>let's stop hearing from ourselves. We really do have the

0:04:06.280 --> 0:04:08.520
<v Speaker 2>perfect guest, someone we've wanted to talk to for a

0:04:08.520 --> 0:04:10.640
<v Speaker 2>long time, someone who's right in the thick of it

0:04:10.800 --> 0:04:13.200
<v Speaker 2>and all this stuff with agentic commerce and payments. We're

0:04:13.200 --> 0:04:15.440
<v Speaker 2>going to be speaking with John Collison, the president and

0:04:15.520 --> 0:04:18.440
<v Speaker 2>co founder of Stripe. So, John, thank you so much

0:04:18.480 --> 0:04:21.760
<v Speaker 2>for coming on odd Lots great to be here. I'm

0:04:21.839 --> 0:04:26.120
<v Speaker 2>very excited. Yeah, buzzwords et cetera. What is quote agentic

0:04:26.200 --> 0:04:27.280
<v Speaker 2>commerce unquote.

0:04:27.920 --> 0:04:30.520
<v Speaker 4>Yeah, so there's a bit of a definitional question, but

0:04:30.600 --> 0:04:34.479
<v Speaker 4>broadly it is AI buying something for you. Okay, And

0:04:34.520 --> 0:04:38.560
<v Speaker 4>we think about this in two categories. One is on

0:04:38.600 --> 0:04:40.520
<v Speaker 4>the consumer side of things. This is where you were

0:04:40.520 --> 0:04:43.320
<v Speaker 4>a skeptical whether Tracy will ever be an adopter, where

0:04:43.480 --> 0:04:46.440
<v Speaker 4>you research something in Chatchy t or claud or what

0:04:46.600 --> 0:04:48.560
<v Speaker 4>have you, and then go buy us there or have

0:04:48.720 --> 0:04:50.960
<v Speaker 4>it buy it for you. But then the second is

0:04:51.000 --> 0:04:53.800
<v Speaker 4>your cloud Flare example, and so it's B to B

0:04:54.360 --> 0:04:57.200
<v Speaker 4>or developer led agentic commerce where you're just trying to

0:04:57.200 --> 0:05:00.599
<v Speaker 4>have cloud code do something for you. And as parts

0:05:00.640 --> 0:05:02.280
<v Speaker 4>of this needs to buy resources, and we can talk

0:05:02.320 --> 0:05:03.560
<v Speaker 4>about that because are quite different.

0:05:03.839 --> 0:05:06.520
<v Speaker 2>Yeah, Tracy, and we'll get to this. But the resources

0:05:06.640 --> 0:05:08.760
<v Speaker 2>is another thing I've whined about, which is that when

0:05:08.760 --> 0:05:10.760
<v Speaker 2>you do an API key, you're like, have an idea

0:05:10.800 --> 0:05:12.039
<v Speaker 2>and you're like, oh, you have to go to the

0:05:12.040 --> 0:05:16.679
<v Speaker 2>web enter credit card number. That's really annoying, et cetera.

0:05:16.920 --> 0:05:18.919
<v Speaker 2>But we'll get into that. But that is another big

0:05:19.000 --> 0:05:21.239
<v Speaker 2>element of it that I feel like is getting closer

0:05:21.240 --> 0:05:21.880
<v Speaker 2>to being solved.

0:05:22.160 --> 0:05:24.640
<v Speaker 3>Okay, Well, on this credit card point, I mean, the

0:05:24.680 --> 0:05:29.720
<v Speaker 3>history of online payments is basically a continuous elimination of

0:05:29.760 --> 0:05:31.960
<v Speaker 3>the friction, right and going from I have to enter

0:05:32.000 --> 0:05:34.320
<v Speaker 3>my credit card details to I have to log into

0:05:34.320 --> 0:05:37.239
<v Speaker 3>PayPal too. Now I can just basically click a button,

0:05:37.360 --> 0:05:42.040
<v Speaker 3>whether it's Apple pay or something else. Is agentic commerce?

0:05:42.440 --> 0:05:46.000
<v Speaker 3>Is this just another leg of the frictionless process or

0:05:46.160 --> 0:05:49.400
<v Speaker 3>is something fundamental in your view changing here?

0:05:51.600 --> 0:05:55.080
<v Speaker 4>Both? So part of agentic commerce is just reducing the friction.

0:05:55.160 --> 0:05:58.200
<v Speaker 4>And you're right that the general direction of travel over time,

0:05:58.360 --> 0:06:00.680
<v Speaker 4>you're back to the introduction of credit cards, when the

0:06:00.720 --> 0:06:05.080
<v Speaker 4>earliest adopters of computer networks, and then the originally commerce

0:06:05.120 --> 0:06:06.960
<v Speaker 4>and now like you're saying, well, it's like Apple paying,

0:06:06.960 --> 0:06:08.960
<v Speaker 4>Google pay, and we have a product call link and

0:06:09.000 --> 0:06:12.320
<v Speaker 4>things like that. So there's generally been this elimination of friction.

0:06:12.920 --> 0:06:16.080
<v Speaker 4>And our view is that at a very minimum, we're

0:06:16.120 --> 0:06:18.159
<v Speaker 4>going to see and Tracy, I think this is where

0:06:18.160 --> 0:06:21.119
<v Speaker 4>you can maybe get behind us. Is leave aside any

0:06:21.160 --> 0:06:26.479
<v Speaker 4>agent decision making that's happening just the final step of

0:06:26.520 --> 0:06:29.320
<v Speaker 4>buying something. You know, you might have researched a product

0:06:29.440 --> 0:06:31.599
<v Speaker 4>in an AI app before, where you're going back and forth.

0:06:31.640 --> 0:06:33.280
<v Speaker 4>I was trying to buy a bike case recently to

0:06:33.320 --> 0:06:35.679
<v Speaker 4>travel with my bike, and you're asking all these questions

0:06:35.680 --> 0:06:37.480
<v Speaker 4>hard versus soft and do you need to take off

0:06:37.480 --> 0:06:39.280
<v Speaker 4>the handlebars? And what's the right one? And it's finding

0:06:39.279 --> 0:06:41.440
<v Speaker 4>all these cool little niche brands. I think it's actually

0:06:41.520 --> 0:06:44.240
<v Speaker 4>quite good for smaller merchants, by the way, because you

0:06:44.279 --> 0:06:46.440
<v Speaker 4>have the ability for them to be discovered that they

0:06:46.520 --> 0:06:49.279
<v Speaker 4>mightn't have had otherwise. But anyway, when you find the

0:06:49.320 --> 0:06:52.200
<v Speaker 4>product at the very end, do you really then want

0:06:52.200 --> 0:06:54.160
<v Speaker 4>to go and be filling out all these web form

0:06:54.200 --> 0:06:56.279
<v Speaker 4>fields and things like that, or do you want to

0:06:56.360 --> 0:06:58.719
<v Speaker 4>just say, yeah, that sounds good, buy it for me

0:06:58.760 --> 0:07:02.280
<v Speaker 4>in this size And our best is that people will

0:07:02.279 --> 0:07:04.400
<v Speaker 4>want the lower friction option. I think in the history

0:07:04.440 --> 0:07:07.200
<v Speaker 4>of technology, the lower friction option tends to win out,

0:07:07.240 --> 0:07:10.280
<v Speaker 4>and so we think that clearly will happen and is

0:07:10.360 --> 0:07:13.320
<v Speaker 4>happening to some degree already. It's just the agent filling

0:07:13.320 --> 0:07:15.800
<v Speaker 4>out the forums for you. I think where you get

0:07:15.800 --> 0:07:19.640
<v Speaker 4>this interesting question is and when people hear a genta commerce,

0:07:19.680 --> 0:07:22.720
<v Speaker 4>I think their mind jumps to the agent actually having

0:07:22.720 --> 0:07:25.600
<v Speaker 4>some autonomy and some decision making for you. I think

0:07:25.640 --> 0:07:30.760
<v Speaker 4>they're The problem is people somehow jump to the examples.

0:07:30.960 --> 0:07:33.280
<v Speaker 4>Anyone who talks about this from them, they pick terrible examples.

0:07:33.360 --> 0:07:35.800
<v Speaker 4>They're like, oh, the agent will book you know, all

0:07:35.800 --> 0:07:38.240
<v Speaker 4>the activities on your vacation for you. It's like people

0:07:39.160 --> 0:07:40.920
<v Speaker 4>think about they daydream about their vacation.

0:07:41.160 --> 0:07:44.960
<v Speaker 3>All yeah, part researching and buddy is the fun part.

0:07:45.400 --> 0:07:48.160
<v Speaker 4>That's the fun part. Or similarly with women's fashion, it's

0:07:48.160 --> 0:07:51.040
<v Speaker 4>like the whole point is the scrolling, not just the buying.

0:07:51.320 --> 0:07:55.160
<v Speaker 4>And so people pick these, you know, super enjoy Like

0:07:55.240 --> 0:07:57.360
<v Speaker 4>it's the robots taking the jobs and when people want

0:07:57.360 --> 0:08:00.240
<v Speaker 4>to keep those scrolling jobs. And so when you think

0:08:00.240 --> 0:08:05.200
<v Speaker 4>about robots having autonomy, I would instead profer some examples

0:08:05.440 --> 0:08:07.880
<v Speaker 4>where you really don't need to be You give the

0:08:07.960 --> 0:08:11.200
<v Speaker 4>AI a recipe and say buy the things that we

0:08:11.320 --> 0:08:13.920
<v Speaker 4>need to make this tonight, and yeah, the AI can

0:08:13.960 --> 0:08:16.320
<v Speaker 4>probably guess that you have salt and you have garlic

0:08:16.360 --> 0:08:19.480
<v Speaker 4>at home, but you need the grand pork. Or again

0:08:19.760 --> 0:08:22.640
<v Speaker 4>then migrating to the B to B example, no one

0:08:22.680 --> 0:08:25.160
<v Speaker 4>needs to configure yes another domain and go through all

0:08:25.160 --> 0:08:28.040
<v Speaker 4>those forms. If claud codes can work with cloud flare

0:08:28.160 --> 0:08:29.880
<v Speaker 4>to buy the domain for you and set it up,

0:08:30.040 --> 0:08:32.240
<v Speaker 4>I think Joe will be much happier. I just feel

0:08:32.280 --> 0:08:34.000
<v Speaker 4>like he's missed out on a valuable life experience.

0:08:34.559 --> 0:08:36.400
<v Speaker 2>I want to talk more about the B to B stuff,

0:08:36.400 --> 0:08:39.200
<v Speaker 2>but let's for a moment stick around on the B

0:08:39.240 --> 0:08:42.000
<v Speaker 2>two C element, because I think there are gradations of this,

0:08:42.080 --> 0:08:45.160
<v Speaker 2>so one is just another elimination of the friction layer.

0:08:45.840 --> 0:08:49.040
<v Speaker 2>At the far end of the spectrum, conceivably there will

0:08:49.080 --> 0:08:52.760
<v Speaker 2>be things where the AI truly does anticipatory buy you

0:08:52.920 --> 0:08:55.640
<v Speaker 2>things that you didn't know you need, etc. Then there

0:08:55.720 --> 0:08:59.360
<v Speaker 2>might be like some middle I saw this screenshow recently

0:08:59.400 --> 0:09:02.559
<v Speaker 2>and I couldn't find it before the episode. Someone tweeted it.

0:09:02.600 --> 0:09:05.960
<v Speaker 2>But some retailer I think was a shoe retailer had

0:09:06.000 --> 0:09:08.040
<v Speaker 2>put a bunch of shoes on their website, but instead

0:09:08.080 --> 0:09:11.160
<v Speaker 2>of like putting any brand names on the shoe, like

0:09:11.160 --> 0:09:13.160
<v Speaker 2>we would say like a Nike Pegasus or a Nike

0:09:13.280 --> 0:09:18.280
<v Speaker 2>Air Jordan, all of the shoes were like hiking boot

0:09:18.360 --> 0:09:20.800
<v Speaker 2>that's good for semi serious hiker.

0:09:21.480 --> 0:09:22.319
<v Speaker 4>Do you see this.

0:09:22.440 --> 0:09:26.320
<v Speaker 2>Currently like where we are on the augentic commerce trajectory,

0:09:26.440 --> 0:09:29.720
<v Speaker 2>do you see this currently where there's already a change

0:09:29.880 --> 0:09:34.840
<v Speaker 2>in how retailers are presenting or displaying or promoting their

0:09:34.880 --> 0:09:38.320
<v Speaker 2>wares such that they're more at tuned for what the

0:09:38.440 --> 0:09:41.559
<v Speaker 2>chatbot would identify or the AI would identify as cool

0:09:42.000 --> 0:09:45.120
<v Speaker 2>versus what a human influenced by brands would pick up

0:09:45.200 --> 0:09:45.520
<v Speaker 2>is cool.

0:09:46.520 --> 0:09:50.319
<v Speaker 4>Yes and no. I mean there's definitely changes. I think

0:09:50.720 --> 0:09:52.959
<v Speaker 4>some of the stuff that's most notable is often not

0:09:53.040 --> 0:09:54.880
<v Speaker 4>the most relevant. It's a little bit It sounds like

0:09:54.880 --> 0:09:56.520
<v Speaker 4>what you're describing is a little bit like the Thai

0:09:56.640 --> 0:09:59.600
<v Speaker 4>restaurant calls typhood near too, you know, do best in

0:09:59.640 --> 0:10:03.600
<v Speaker 4>the se But I think what we see as kind

0:10:03.600 --> 0:10:05.720
<v Speaker 4>of maybe a more interesting direction of travel is again

0:10:05.880 --> 0:10:09.079
<v Speaker 4>what's happening already some amount of the form fields being

0:10:09.080 --> 0:10:10.680
<v Speaker 4>filled out for you and kind of the friction reduction

0:10:11.000 --> 0:10:13.520
<v Speaker 4>and a huge amount of again I presume you guys

0:10:13.520 --> 0:10:16.840
<v Speaker 4>have both done this is at research in AI apps,

0:10:16.880 --> 0:10:18.440
<v Speaker 4>And you know, the way I would frame that is

0:10:18.520 --> 0:10:22.040
<v Speaker 4>just keyword search is ridiculous. It's ridiculous that we got

0:10:22.040 --> 0:10:24.959
<v Speaker 4>to the year twenty twenty six relying on keyword search,

0:10:25.000 --> 0:10:28.280
<v Speaker 4>where that makes sense for buying a book or a DVD,

0:10:29.000 --> 0:10:31.240
<v Speaker 4>where you know the title of the book or a

0:10:31.320 --> 0:10:33.320
<v Speaker 4>DVD that you're trying to buy. But that's about the

0:10:33.360 --> 0:10:35.360
<v Speaker 4>limit of keyword search. And so the fact that anyone

0:10:35.440 --> 0:10:38.840
<v Speaker 4>was trying to buy furniture or clothes or anything like that,

0:10:39.200 --> 0:10:41.599
<v Speaker 4>and there was this text box at the top of

0:10:41.640 --> 0:10:43.520
<v Speaker 4>the website where you put in your keywords. It's like,

0:10:43.559 --> 0:10:45.439
<v Speaker 4>that's just that's not how anyone shops in the real word,

0:10:45.520 --> 0:10:48.600
<v Speaker 4>things like that. And so we're seeing this AI powered

0:10:48.640 --> 0:10:52.240
<v Speaker 4>research where people can explore product space and start to

0:10:52.280 --> 0:10:57.920
<v Speaker 4>give constraints and you have this textual search interface, but

0:10:58.360 --> 0:11:00.640
<v Speaker 4>you end up with kind of much higher search where

0:11:00.679 --> 0:11:02.439
<v Speaker 4>it's like, Okay, I have a spot in this room

0:11:02.440 --> 0:11:04.680
<v Speaker 4>where I'm looking for a piece of furniture that's this

0:11:04.840 --> 0:11:07.800
<v Speaker 4>why is max and this high because I need to

0:11:07.800 --> 0:11:09.680
<v Speaker 4>fit it in there. That's the kind of thing that's

0:11:09.679 --> 0:11:11.719
<v Speaker 4>just much better suited to the imodaliti. So you see

0:11:11.720 --> 0:11:13.959
<v Speaker 4>different kinds of product research possible. And like we said,

0:11:14.360 --> 0:11:18.839
<v Speaker 4>it's very helpful to smaller brands because people aren't necessarily

0:11:18.880 --> 0:11:22.000
<v Speaker 4>stuck behind the traditional aggregators anymore. They can break out.

0:11:22.040 --> 0:11:25.319
<v Speaker 4>And again I have found in my little research projects

0:11:25.320 --> 0:11:28.439
<v Speaker 4>that I've done, finding how you often get these small

0:11:28.520 --> 0:11:31.560
<v Speaker 4>brands surfaced that you mightn't have heard of before. And

0:11:31.600 --> 0:11:34.360
<v Speaker 4>so we think it's actually probably quite good for the dynamism.

0:11:34.280 --> 0:11:36.959
<v Speaker 3>Well let me ask Joe's question in a slightly different way,

0:11:37.000 --> 0:11:39.640
<v Speaker 3>which is, if we assume that in the future, if

0:11:39.679 --> 0:11:44.080
<v Speaker 3>I'm a business selling something online. Previously I was selling

0:11:44.400 --> 0:11:47.200
<v Speaker 3>to humans more or less, like maybe I'd optimize for

0:11:47.240 --> 0:11:49.560
<v Speaker 3>Google search results or whatever, but like, mostly I'm trying

0:11:49.559 --> 0:11:52.240
<v Speaker 3>to appeal to humans, and now I'm trying to appeal

0:11:52.440 --> 0:11:58.080
<v Speaker 3>more to agents. What does optimizing for agents actually look like?

0:12:00.080 --> 0:12:03.920
<v Speaker 4>Part of it is similar to traditional SEO, right, so

0:12:03.960 --> 0:12:06.679
<v Speaker 4>you want to be legible to those agents, you want

0:12:06.720 --> 0:12:10.520
<v Speaker 4>to be discovered by them. But part of what, at

0:12:10.559 --> 0:12:14.480
<v Speaker 4>least I've seen is that the ais have pretty good taste. Joe,

0:12:14.480 --> 0:12:16.320
<v Speaker 4>I don't know if you've found this in your vibe coding.

0:12:16.480 --> 0:12:18.319
<v Speaker 4>By the way, Joe, I'm reminded of its sort of

0:12:18.320 --> 0:12:19.880
<v Speaker 4>like the old joke, how do you know if someone

0:12:20.040 --> 0:12:25.600
<v Speaker 4>vibe codes they'll tell you about it exactly but guilt,

0:12:25.679 --> 0:12:28.920
<v Speaker 4>And I'm guessing you found that theies are very tasteful

0:12:28.920 --> 0:12:34.920
<v Speaker 4>at picking libraries and picking specific subcomponents to use. And similarly,

0:12:35.000 --> 0:12:37.600
<v Speaker 4>in our kind of early experience of the agenta commerce,

0:12:37.760 --> 0:12:41.080
<v Speaker 4>they're quite tasteful in finding tools that suit the job

0:12:41.120 --> 0:12:43.679
<v Speaker 4>pretty well. And so I think you may get this

0:12:43.840 --> 0:12:47.680
<v Speaker 4>more efficient market phenomenon, where at least in picking coding

0:12:47.720 --> 0:12:50.400
<v Speaker 4>libraries or something like that, the ais are have quite

0:12:50.440 --> 0:12:52.959
<v Speaker 4>like I find when I do stuff, they're discovering libraries

0:12:53.000 --> 0:12:54.880
<v Speaker 4>that are perfect for the job that I hadn't even

0:12:54.920 --> 0:12:57.040
<v Speaker 4>heard of, or something like that. I think you're starting

0:12:57.040 --> 0:12:59.600
<v Speaker 4>to see the same phenomenon with products, where again I've

0:12:59.600 --> 0:13:01.040
<v Speaker 4>had the experience of you know, I was trying to

0:13:01.040 --> 0:13:02.920
<v Speaker 4>find a travel adapter and I found it from this

0:13:02.960 --> 0:13:05.640
<v Speaker 4>tiny company. This I had never heard of, was doing

0:13:05.679 --> 0:13:07.320
<v Speaker 4>exactly what I want to where it's like an integrated

0:13:07.320 --> 0:13:10.079
<v Speaker 4>travel adopter in power break. It's really good and I

0:13:10.120 --> 0:13:12.079
<v Speaker 4>would never have come across that company otherwise.

0:13:12.360 --> 0:13:16.000
<v Speaker 2>This is incredibly important because, as I mentioned the beginning,

0:13:16.760 --> 0:13:21.520
<v Speaker 2>advertising creates culture. It's part of culture, especially iconic advertising.

0:13:21.559 --> 0:13:24.319
<v Speaker 2>And maybe it'll be a little while before the Nikes

0:13:24.320 --> 0:13:26.400
<v Speaker 2>of the world, they're the Nikes and Apples of the world.

0:13:26.400 --> 0:13:28.320
<v Speaker 2>They're going to be advertising for a long time. But

0:13:29.080 --> 0:13:32.000
<v Speaker 2>do you see this eventually as sort of like one

0:13:32.040 --> 0:13:34.559
<v Speaker 2>of the things I think that the Internet appreciates about

0:13:34.640 --> 0:13:37.440
<v Speaker 2>Stripe as a company is you and your brother's commitment

0:13:37.480 --> 0:13:41.320
<v Speaker 2>to interesting discussions of economics and so forth, and you

0:13:41.360 --> 0:13:44.520
<v Speaker 2>talk about econ history. There are great debates about whether

0:13:45.240 --> 0:13:48.960
<v Speaker 2>spending is a huge deadweight loss on the economy or

0:13:49.000 --> 0:13:51.960
<v Speaker 2>whether it's something positive, et cetera. And I'm curious, could

0:13:52.040 --> 0:13:56.120
<v Speaker 2>you see a sort of post advertising future, you know,

0:13:56.160 --> 0:13:58.000
<v Speaker 2>at some point on the horizon.

0:13:59.240 --> 0:14:03.520
<v Speaker 4>No, I think we're quite skeptical of that for two reasons.

0:14:03.760 --> 0:14:07.840
<v Speaker 4>One again, with agentic commerce, we don't think the human

0:14:08.360 --> 0:14:10.440
<v Speaker 4>goes away and the human in the loop goes away.

0:14:10.679 --> 0:14:12.640
<v Speaker 4>And there's a huge amount of agentic commerce that can

0:14:12.679 --> 0:14:16.280
<v Speaker 4>happen like we're describing, where you still have the human

0:14:16.320 --> 0:14:19.120
<v Speaker 4>as the end decider. And so it will likely to

0:14:19.160 --> 0:14:21.160
<v Speaker 4>be the case that if you are searching for something,

0:14:21.200 --> 0:14:23.720
<v Speaker 4>if you have on a new microphone for the adlot's studio,

0:14:23.960 --> 0:14:26.440
<v Speaker 4>you might ask it to go research and it'll present

0:14:26.840 --> 0:14:29.400
<v Speaker 4>three or four different options with different trade offs. There's

0:14:29.400 --> 0:14:31.160
<v Speaker 4>no right microphone that is going to be kind of

0:14:31.200 --> 0:14:34.360
<v Speaker 4>castrated on anythings like that. And then ultimately you will

0:14:34.360 --> 0:14:36.760
<v Speaker 4>make a call and it'll go buy it for you.

0:14:37.120 --> 0:14:40.880
<v Speaker 4>And when you make that call, some brand preference you have,

0:14:41.080 --> 0:14:43.880
<v Speaker 4>Oh sure, I just know that they're like the ones

0:14:43.920 --> 0:14:46.480
<v Speaker 4>with the really good sound quality. Not clear why you

0:14:46.480 --> 0:14:49.040
<v Speaker 4>have that association. Maybe there some advertising in there somewhere,

0:14:49.280 --> 0:14:51.560
<v Speaker 4>But so we think brand preference and as part of

0:14:51.560 --> 0:14:54.880
<v Speaker 4>that advertising will clearly stick around. Because again it's definitely

0:14:54.880 --> 0:14:56.960
<v Speaker 4>not going to be the case that agentic commerce means

0:14:57.000 --> 0:15:00.360
<v Speaker 4>no humans make buying decisions. That's absolutely not case. But

0:15:00.360 --> 0:15:02.000
<v Speaker 4>again this may be a good example. You want to

0:15:02.000 --> 0:15:04.120
<v Speaker 4>buy new microphones for the studio, you do a lot

0:15:04.120 --> 0:15:06.440
<v Speaker 4>of AI research, you don't have a human decide, and

0:15:06.480 --> 0:15:08.320
<v Speaker 4>then you do a lot of AI execution, and so

0:15:08.360 --> 0:15:11.040
<v Speaker 4>it's a on both sides, and then human decision making

0:15:11.080 --> 0:15:14.120
<v Speaker 4>in the middle. Brand affinity really matters in that world.

0:15:14.320 --> 0:15:17.360
<v Speaker 4>The other thing, of course, is commerce can be directed

0:15:17.440 --> 0:15:20.400
<v Speaker 4>or undirected. Where in the directed side, like I was saying,

0:15:20.440 --> 0:15:21.760
<v Speaker 4>trying to buy a bike, case it's like this is

0:15:21.760 --> 0:15:22.880
<v Speaker 4>a thing that I know I need to go do.

0:15:22.920 --> 0:15:25.200
<v Speaker 4>I'm going to go do some research. Previously, you know,

0:15:25.320 --> 0:15:28.080
<v Speaker 4>Google ad might have been irrelevant to me, whereas now

0:15:28.080 --> 0:15:31.560
<v Speaker 4>it's what appears in the AI search results. Obviously that

0:15:31.600 --> 0:15:35.520
<v Speaker 4>does remove some advertising, but for now at least, maybe

0:15:35.560 --> 0:15:37.240
<v Speaker 4>some of the AI as at least choose to bring

0:15:37.280 --> 0:15:39.720
<v Speaker 4>back some advertising in those cases. But then a lot

0:15:39.720 --> 0:15:42.160
<v Speaker 4>of shopping is undirected where you're scrolling Instagram, and the

0:15:42.200 --> 0:15:44.720
<v Speaker 4>joke goes that these days on Instagram, the ads are

0:15:44.760 --> 0:15:47.640
<v Speaker 4>better than the organic content because they've gotten so good

0:15:47.640 --> 0:15:49.800
<v Speaker 4>with the targeting and there's nice, reassuring things that you

0:15:49.880 --> 0:15:53.200
<v Speaker 4>might want to buy, and there that is advertising, and

0:15:53.200 --> 0:15:55.840
<v Speaker 4>people are going to stay scrolling social apps and finding

0:15:55.840 --> 0:15:57.640
<v Speaker 4>cool products they want to buy. So I wouldn't be

0:15:57.680 --> 0:15:58.960
<v Speaker 4>short advertising in this world.

0:16:15.200 --> 0:16:18.320
<v Speaker 3>You mentioned machine readability earlier. Talk to us about the

0:16:18.320 --> 0:16:21.960
<v Speaker 3>actual process of converting your catalog into something that an

0:16:22.000 --> 0:16:25.920
<v Speaker 3>agent can actually read, and how standardized that is at

0:16:25.920 --> 0:16:28.600
<v Speaker 3>the moment, and how standardized do you expect it to

0:16:28.640 --> 0:16:30.520
<v Speaker 3>be in the future. And then also, like, if you're

0:16:30.560 --> 0:16:36.600
<v Speaker 3>standardizing for machine readability, I feel like it's difficult to

0:16:36.760 --> 0:16:40.640
<v Speaker 3>capture some of what might make a product interesting. It's

0:16:40.680 --> 0:16:43.640
<v Speaker 3>difficult to like code the actual vibes of a product.

0:16:44.120 --> 0:16:48.040
<v Speaker 3>Even with lms. I just find there's something difficult to capture.

0:16:48.120 --> 0:16:50.120
<v Speaker 3>So talk to us about how you make you make

0:16:50.160 --> 0:16:53.480
<v Speaker 3>it so that agents fully understand what is available to them.

0:16:53.880 --> 0:16:56.800
<v Speaker 4>Yeah, so there's two levels here. The first is just

0:16:57.680 --> 0:17:01.120
<v Speaker 4>being known in the same way that you'd be known

0:17:01.160 --> 0:17:04.480
<v Speaker 4>to humans. Because obviously all the lms have read the

0:17:04.480 --> 0:17:08.080
<v Speaker 4>whole Internet. That's what they're trained on, and they can

0:17:08.119 --> 0:17:11.560
<v Speaker 4>do web searches. And so if you have good product

0:17:11.600 --> 0:17:14.800
<v Speaker 4>pages that are informative and lay out the details of

0:17:14.920 --> 0:17:17.320
<v Speaker 4>what the product does. If you have reviews, you know,

0:17:17.359 --> 0:17:19.719
<v Speaker 4>if there's like a bunch of wirecutter reviews things like that,

0:17:19.840 --> 0:17:22.399
<v Speaker 4>you've probably seen this in research searches where you know,

0:17:22.480 --> 0:17:24.439
<v Speaker 4>the AI app will say, you know, people love this

0:17:24.600 --> 0:17:26.840
<v Speaker 4>product and they say X, y Z, but they've read

0:17:26.840 --> 0:17:29.160
<v Speaker 4>the whole internet, and so being known, you know, I'm

0:17:29.160 --> 0:17:31.560
<v Speaker 4>a big deal on the internet helps with the AI

0:17:31.640 --> 0:17:33.880
<v Speaker 4>apps as it does for humans. That's kind of step one.

0:17:34.160 --> 0:17:36.840
<v Speaker 4>Step two, and where a stripe gets more involved is

0:17:36.840 --> 0:17:39.760
<v Speaker 4>you need a lot of the mechanical wiring up so

0:17:39.800 --> 0:17:42.920
<v Speaker 4>that the ais can do stuff that are more programmatic.

0:17:42.920 --> 0:17:44.960
<v Speaker 4>And this is where our agentic commerce suites that we

0:17:45.000 --> 0:17:46.560
<v Speaker 4>you know, had an announcement about, and this is what

0:17:46.560 --> 0:17:49.560
<v Speaker 4>we're working on with Google and Microsoft and Meta and

0:17:49.760 --> 0:17:52.040
<v Speaker 4>you know open ai and all those folks to actually

0:17:52.040 --> 0:17:53.800
<v Speaker 4>do some of the commerce wiring up. And there, I'd

0:17:53.840 --> 0:17:58.160
<v Speaker 4>say it's two things. One is you need a machine

0:17:59.160 --> 0:18:03.040
<v Speaker 4>compatible way to get the very latest information about the

0:18:03.080 --> 0:18:06.159
<v Speaker 4>product details. So it's one thing for the AI to

0:18:06.240 --> 0:18:09.200
<v Speaker 4>have in its training run maybe a year ago, read

0:18:09.200 --> 0:18:11.600
<v Speaker 4>the whole internet and know that that this product is good.

0:18:11.960 --> 0:18:13.520
<v Speaker 4>You need to be able to tell the AI is

0:18:13.520 --> 0:18:17.120
<v Speaker 4>it still on sale, whats skews are in stock, which

0:18:17.200 --> 0:18:19.800
<v Speaker 4>sizes we have right now, and things like that, and

0:18:19.880 --> 0:18:22.080
<v Speaker 4>so that kind of up to date, being able to

0:18:22.080 --> 0:18:25.199
<v Speaker 4>make real time calls to the seller so that the

0:18:25.280 --> 0:18:28.640
<v Speaker 4>AI has fresh, correct information that it can present. That's

0:18:28.680 --> 0:18:31.199
<v Speaker 4>thing one, and then thing two is wiring up the

0:18:31.440 --> 0:18:34.320
<v Speaker 4>agentic checkout so the AI can actually buy it. And

0:18:34.400 --> 0:18:36.720
<v Speaker 4>here you get into a bunch of boring like payments details.

0:18:36.720 --> 0:18:40.239
<v Speaker 4>But for example, you you're not allowed you don't want

0:18:40.280 --> 0:18:42.600
<v Speaker 4>to be you're not allowed to describe that's true.

0:18:42.600 --> 0:18:50.720
<v Speaker 2>Detail is boring. So start yeah, keep going.

0:18:50.920 --> 0:18:54.240
<v Speaker 4>Start Okay. So then for actually kind of handling a

0:18:54.240 --> 0:18:58.840
<v Speaker 4>three way transaction where there's you in chat GBT buying

0:18:58.880 --> 0:19:01.840
<v Speaker 4>a product from this something like that, we're facilitating that

0:19:01.880 --> 0:19:03.879
<v Speaker 4>transaction and there you want to be. You don't have

0:19:03.880 --> 0:19:05.720
<v Speaker 4>to be re entering your payment details on each website.

0:19:05.760 --> 0:19:07.119
<v Speaker 4>At the same time, you don't want to be flinging

0:19:07.119 --> 0:19:10.280
<v Speaker 4>your payment details around across different websites. And so we

0:19:10.359 --> 0:19:12.440
<v Speaker 4>built all the wiring up and also don't forget, a

0:19:12.480 --> 0:19:15.040
<v Speaker 4>lot of websites have Historically bots used to be a

0:19:15.080 --> 0:19:17.520
<v Speaker 4>bad thing. They used to discriminating spots. They would have

0:19:17.560 --> 0:19:20.680
<v Speaker 4>bought protections and things like that, whereas now it's like, okay, no,

0:19:20.760 --> 0:19:22.560
<v Speaker 4>we actually want agents to be able to do this,

0:19:22.840 --> 0:19:25.520
<v Speaker 4>and so you're unwinding some of the bot protections and

0:19:25.680 --> 0:19:27.840
<v Speaker 4>having a little tsa pre for the bots that we

0:19:27.920 --> 0:19:31.360
<v Speaker 4>work with, a way to kind of securely transfer one

0:19:31.359 --> 0:19:33.720
<v Speaker 4>time use payment credential and things like this. There's a

0:19:33.760 --> 0:19:36.320
<v Speaker 4>lot of wiring up beneath the c businesses have to do.

0:19:36.480 --> 0:19:39.560
<v Speaker 2>This is actually maybe like a good spot to slightly

0:19:39.760 --> 0:19:43.560
<v Speaker 2>seg over into the B to B element of agentic commerce,

0:19:43.840 --> 0:19:46.440
<v Speaker 2>because this gets to another thing that I think about,

0:19:46.560 --> 0:19:48.280
<v Speaker 2>you know, I know one of the things that a

0:19:48.320 --> 0:19:52.719
<v Speaker 2>valuable training data is literally just looking at user mouse behavior,

0:19:52.800 --> 0:19:56.280
<v Speaker 2>right because then theoretically the AI model can go to

0:19:56.320 --> 0:19:58.600
<v Speaker 2>a website and click the buttons just the way a

0:19:58.680 --> 0:20:02.199
<v Speaker 2>human want. Well, it seems silly to me, like, ultimately,

0:20:02.640 --> 0:20:05.640
<v Speaker 2>if we're building a human we're building websites for human use,

0:20:06.160 --> 0:20:08.280
<v Speaker 2>and then a bot's going to actually scrape them, why

0:20:08.320 --> 0:20:10.639
<v Speaker 2>not just actually build it for bots in the first place?

0:20:10.880 --> 0:20:13.000
<v Speaker 2>What are we seeing there. What are you seeing from

0:20:13.119 --> 0:20:17.560
<v Speaker 2>retailers where the fundamental experience is it going to be

0:20:17.680 --> 0:20:20.960
<v Speaker 2>reshaped such that what we call the UX, the user

0:20:21.080 --> 0:20:25.440
<v Speaker 2>experience is not really the U is not the person,

0:20:25.480 --> 0:20:27.680
<v Speaker 2>but the U is the bot? And is that changing

0:20:27.960 --> 0:20:30.000
<v Speaker 2>how the Internet is just going to look?

0:20:31.720 --> 0:20:35.639
<v Speaker 4>So you're getting to a very core debate that's happening

0:20:35.680 --> 0:20:37.560
<v Speaker 4>in AI right now, Like some of these kind of

0:20:37.640 --> 0:20:40.560
<v Speaker 4>questions at the frontier of AI as to where things

0:20:40.560 --> 0:20:43.520
<v Speaker 4>go for practical purposes, but one of them is when

0:20:43.600 --> 0:20:46.880
<v Speaker 4>you think about AI adoption for real world tasks, there's

0:20:46.880 --> 0:20:51.520
<v Speaker 4>almost a race between maybe we make the world consumable

0:20:51.560 --> 0:20:55.240
<v Speaker 4>by AI, and we make the websites friendly for AIS

0:20:55.280 --> 0:20:59.040
<v Speaker 4>to navigate and things like that, or maybe just the

0:20:59.080 --> 0:21:02.200
<v Speaker 4>AIS get good enough unstructured computer use that you give

0:21:02.240 --> 0:21:04.159
<v Speaker 4>them a desktop, and you give them a mouse and

0:21:04.200 --> 0:21:07.359
<v Speaker 4>a keyboard, and there's no backwards compatibility that we built,

0:21:07.600 --> 0:21:10.240
<v Speaker 4>but they just end up figuring his house anyway. And

0:21:10.280 --> 0:21:14.240
<v Speaker 4>it feels like over the next year, two or maybe three,

0:21:14.400 --> 0:21:18.280
<v Speaker 4>this question will be resolved. Right now, a lot of people,

0:21:18.280 --> 0:21:22.280
<v Speaker 4>including us, are working on making the stripe dashboard, merchant

0:21:22.359 --> 0:21:25.199
<v Speaker 4>website things like that consumable by the AIS. And what

0:21:25.200 --> 0:21:29.360
<v Speaker 4>that means basically is text where the AIS are very

0:21:29.359 --> 0:21:31.960
<v Speaker 4>good at working with text, and so you need a

0:21:32.000 --> 0:21:35.320
<v Speaker 4>textual interface for a bunch of things that previously might

0:21:35.359 --> 0:21:37.000
<v Speaker 4>have been clicking around on a website.

0:21:37.200 --> 0:21:40.439
<v Speaker 2>But maybe sorry, just to be clear, this reminds me

0:21:40.480 --> 0:21:42.560
<v Speaker 2>a little bit about the debate whether like apps in

0:21:42.600 --> 0:21:45.399
<v Speaker 2>the app Store should be skewmorphic or not. But just

0:21:45.440 --> 0:21:49.159
<v Speaker 2>to be clear, Stripe is kind of taking a bet

0:21:49.200 --> 0:21:52.680
<v Speaker 2>on the other side that actually, the websites that look

0:21:52.760 --> 0:21:56.120
<v Speaker 2>like they're designed for humans will not be the way

0:21:56.160 --> 0:21:58.200
<v Speaker 2>to place where to place your chips.

0:21:58.680 --> 0:22:00.919
<v Speaker 4>Well, it's an option, right, because ais get really good

0:22:00.960 --> 0:22:03.120
<v Speaker 4>at computer use quickly, then it's good, you know, then

0:22:03.200 --> 0:22:05.040
<v Speaker 4>we have that answer. And you see this a little bit.

0:22:05.119 --> 0:22:07.280
<v Speaker 4>When people get their open Claw to go buy something

0:22:07.400 --> 0:22:09.560
<v Speaker 4>and it's running on their Macmini at home. The merchant

0:22:09.640 --> 0:22:12.440
<v Speaker 4>might say, oh, but I don't have an agentic interface.

0:22:12.480 --> 0:22:14.840
<v Speaker 4>It's like, well, we bought it anyway. The Claw just

0:22:14.880 --> 0:22:17.159
<v Speaker 4>went and did it and used a headless browser. And

0:22:17.320 --> 0:22:19.960
<v Speaker 4>so you don't need to do anything to enable the

0:22:20.000 --> 0:22:21.800
<v Speaker 4>computer use world, because the whole point is that it's

0:22:21.800 --> 0:22:25.640
<v Speaker 4>fully backwards compatible with the current world. But in the meantime,

0:22:25.680 --> 0:22:28.400
<v Speaker 4>I think people want to have these really powerful agentic experiences.

0:22:28.400 --> 0:22:30.560
<v Speaker 4>It's a bit of a race, right, I think businesses

0:22:30.800 --> 0:22:33.439
<v Speaker 4>correctly you want to be the first ones to capture

0:22:33.440 --> 0:22:35.000
<v Speaker 4>all this demand, because I think it'd be the case

0:22:35.040 --> 0:22:38.480
<v Speaker 4>if you start getting presented results in an AI app

0:22:38.680 --> 0:22:40.600
<v Speaker 4>and it's like, Okay, here are a bunch of options.

0:22:40.760 --> 0:22:42.920
<v Speaker 4>This one you can just click buy now and it'll

0:22:43.000 --> 0:22:45.080
<v Speaker 4>arrive in two days, or this one you have to

0:22:45.119 --> 0:22:46.920
<v Speaker 4>go to the website and click around and blah blah

0:22:46.920 --> 0:22:49.600
<v Speaker 4>blah blah. I think you start seeing some consumer preference

0:22:49.640 --> 0:22:51.360
<v Speaker 4>for the one they click one, kind of like on Amazon,

0:22:51.560 --> 0:22:54.800
<v Speaker 4>when there's like a seller that has Amazon Prime in

0:22:54.840 --> 0:22:57.280
<v Speaker 4>the third party sellers, you're way more likely to pick that.

0:22:57.359 --> 0:22:59.560
<v Speaker 4>And Amazon has done studies on this. You can imagine

0:22:59.560 --> 0:23:02.680
<v Speaker 4>and aagous world within the AI apps where the businesses

0:23:02.680 --> 0:23:06.560
<v Speaker 4>that supports agentic commerce sooner outperform the ones that don't.

0:23:07.320 --> 0:23:10.520
<v Speaker 3>Can you talk to us about how agentic commerce could

0:23:10.600 --> 0:23:13.640
<v Speaker 3>impact prices? And we all know that already. When people

0:23:13.680 --> 0:23:15.920
<v Speaker 3>are researching for products, you might put in a prompt

0:23:15.920 --> 0:23:19.720
<v Speaker 3>saying like find me the cheapest pair of I don't

0:23:19.760 --> 0:23:23.480
<v Speaker 3>know sneakers that fit the following standard, and so you

0:23:23.480 --> 0:23:26.960
<v Speaker 3>could imagine a world where lots and lots of consumers

0:23:26.960 --> 0:23:31.399
<v Speaker 3>are being driven to the cheapest possible option for their needs.

0:23:31.440 --> 0:23:34.040
<v Speaker 3>And you could also imagine a world where maybe shops

0:23:34.080 --> 0:23:38.480
<v Speaker 3>start to respond with more sophisticated price pack architecture, maybe

0:23:38.560 --> 0:23:41.399
<v Speaker 3>dynamic pricing or something like that, which makes me wonder

0:23:41.760 --> 0:23:44.200
<v Speaker 3>if the future is just going to be bots negotiating

0:23:44.240 --> 0:23:46.480
<v Speaker 3>with each other over price endlessly.

0:23:47.480 --> 0:23:49.560
<v Speaker 4>I think it's a bit I mean, we can all

0:23:49.560 --> 0:23:51.280
<v Speaker 4>speculate it. I think it's a bit too early to

0:23:51.320 --> 0:23:56.040
<v Speaker 4>have realized data there, because one, it's an early phenomenon obviously. Secondly,

0:23:56.359 --> 0:23:59.439
<v Speaker 4>the leading edge of AI apps is quite high income,

0:23:59.640 --> 0:24:02.680
<v Speaker 4>which is it's not necessarily representative of what the durable

0:24:02.760 --> 0:24:06.560
<v Speaker 4>equilibrium will be. The one that we think about a

0:24:06.600 --> 0:24:11.240
<v Speaker 4>lot is micro transactions are probably going to be now possible. Yeah,

0:24:11.280 --> 0:24:14.360
<v Speaker 4>and so you probably have this whole segment of commerce

0:24:14.400 --> 0:24:17.320
<v Speaker 4>that previously wasn't double its micro transactions. They never work,

0:24:17.680 --> 0:24:21.199
<v Speaker 4>or never have worked historically because of the kind of

0:24:21.560 --> 0:24:25.760
<v Speaker 4>mental load of deciding. There's no point at selling Bloomberg

0:24:25.840 --> 0:24:28.879
<v Speaker 4>articles for you know, forty cents each, because by the

0:24:28.880 --> 0:24:31.160
<v Speaker 4>time you've decided, you might as well, just have bought

0:24:31.280 --> 0:24:34.720
<v Speaker 4>a day pass or a subscription or something like that. However,

0:24:35.119 --> 0:24:38.240
<v Speaker 4>if Bloomberg, and actually I would love if Bloomberg had

0:24:38.240 --> 0:24:39.960
<v Speaker 4>a proper API for their data, because if you want

0:24:39.960 --> 0:24:41.880
<v Speaker 4>to do anything involving in finance, when your vibe coding,

0:24:41.920 --> 0:24:43.840
<v Speaker 4>it'd be really handy to have the Bloomberg data. And

0:24:43.960 --> 0:24:46.680
<v Speaker 4>the terminal is not exactly at the right interface for AI,

0:24:46.960 --> 0:24:50.280
<v Speaker 4>but selling Bloomberg data by the SIP, so it's like, Okay,

0:24:50.320 --> 0:24:52.200
<v Speaker 4>we're doing a query about the strait of Hormuz. Let's

0:24:52.200 --> 0:24:53.880
<v Speaker 4>pull in the Bloomberg DTA for that, and you pay

0:24:53.920 --> 0:24:56.400
<v Speaker 4>whatever a small amount for that one little data request.

0:24:56.680 --> 0:24:59.000
<v Speaker 4>That's a micro transaction that could actually happen. So that's

0:24:59.040 --> 0:25:01.520
<v Speaker 4>the big effect that we think the time is finally

0:25:01.560 --> 0:25:03.720
<v Speaker 4>there because the mental load has traditionally been too high

0:25:03.720 --> 0:25:06.760
<v Speaker 4>for humans. But I just love overthinking things. They love

0:25:07.000 --> 0:25:09.719
<v Speaker 4>scrutinizing every decision, and so we might as well do that.

0:25:10.160 --> 0:25:11.960
<v Speaker 3>This is something I've been thinking about as well. If

0:25:11.960 --> 0:25:15.320
<v Speaker 3>micro transactions become friction, yes, right, do people try to

0:25:15.359 --> 0:25:18.440
<v Speaker 3>monetize more and more content such that basically like you're

0:25:18.520 --> 0:25:21.199
<v Speaker 3>kind of paying attack to browse the internet.

0:25:21.280 --> 0:25:23.040
<v Speaker 2>By the way, John, I just want to let you know.

0:25:23.280 --> 0:25:25.080
<v Speaker 2>I don't know if you know this, but Bloomberg has

0:25:25.160 --> 0:25:27.639
<v Speaker 2>actually delegated some of these big strategic questions to me

0:25:27.680 --> 0:25:30.960
<v Speaker 2>and Tracy so we can They've actually said, no, the

0:25:31.000 --> 0:25:33.560
<v Speaker 2>podcasters should get to do that, so that we could work,

0:25:33.560 --> 0:25:34.840
<v Speaker 2>we could actually talk about this.

0:25:34.840 --> 0:25:37.359
<v Speaker 4>If you guys could put word in with Mike and

0:25:37.400 --> 0:25:40.720
<v Speaker 4>the crew that just I would like my coding agents

0:25:40.760 --> 0:25:42.159
<v Speaker 4>to be able to talk to Bloomberg.

0:25:42.240 --> 0:25:45.760
<v Speaker 3>Ye, like we're messaging him right now.

0:25:45.800 --> 0:25:48.639
<v Speaker 2>But no, there's actually once again perfectly segs to my

0:25:48.680 --> 0:25:51.000
<v Speaker 2>next question. One of the things for I hear from

0:25:51.040 --> 0:25:54.200
<v Speaker 2>I've heard for years from my software developer friends. They

0:25:54.280 --> 0:25:56.959
<v Speaker 2>use this binary free as in beer or free as

0:25:57.000 --> 0:25:59.639
<v Speaker 2>in speech. Right, so there's like software that you can

0:25:59.680 --> 0:26:02.840
<v Speaker 2>downloa for free, and that's you know, that's freeze and beer.

0:26:02.880 --> 0:26:04.840
<v Speaker 2>But then free can also mean sort of like can

0:26:04.920 --> 0:26:07.320
<v Speaker 2>do anything you want with that freeze in speech. I'm

0:26:07.359 --> 0:26:10.000
<v Speaker 2>wondering on this point whether we need a third sort

0:26:10.040 --> 0:26:14.119
<v Speaker 2>of one. Free isn't roaming free roaming because every piece

0:26:14.119 --> 0:26:18.320
<v Speaker 2>of data is theoretically valuable to a model maker, and

0:26:18.440 --> 0:26:21.240
<v Speaker 2>every interaction with a piece of data, which maybe is

0:26:21.240 --> 0:26:25.280
<v Speaker 2>called metadata that's all that interaction activity is also very valuable,

0:26:25.400 --> 0:26:29.080
<v Speaker 2>et cetera. And I'm curious, given that every interaction and

0:26:29.200 --> 0:26:31.200
<v Speaker 2>any version of that is valuable, are we going to

0:26:31.240 --> 0:26:33.439
<v Speaker 2>be at the end of the sort of free roaming

0:26:33.520 --> 0:26:37.120
<v Speaker 2>internet or we where we always just be paying these

0:26:37.160 --> 0:26:42.080
<v Speaker 2>brilliant of ascent micro transactions which theoretically become doable and

0:26:42.200 --> 0:26:45.200
<v Speaker 2>reasonable as we just sort of go along the internet

0:26:45.520 --> 0:26:49.520
<v Speaker 2>surf the web, because this is all very valuable information

0:26:49.600 --> 0:26:51.080
<v Speaker 2>that's theoretically being exposed.

0:26:52.600 --> 0:26:55.000
<v Speaker 4>I don't think AI is causing the end of the

0:26:55.040 --> 0:26:58.680
<v Speaker 4>free roaming Internet, because there's always been a lot of

0:26:59.359 --> 0:27:04.520
<v Speaker 4>propriety three stuff newspaper paywalls. I don't remember a free

0:27:04.600 --> 0:27:08.080
<v Speaker 4>roaming Bloomberg that I could read without paying even the

0:27:08.160 --> 0:27:09.520
<v Speaker 4>aire that's a subscription.

0:27:09.640 --> 0:27:13.560
<v Speaker 2>Man, you can actually get the terminal. Sorry, yes, I

0:27:13.560 --> 0:27:17.320
<v Speaker 2>feel like I know you really want our term anyway, Sorry,

0:27:17.359 --> 0:27:17.760
<v Speaker 2>keep going.

0:27:18.119 --> 0:27:21.200
<v Speaker 4>Yes, So there's always been a lot of prietary stuff

0:27:21.240 --> 0:27:23.000
<v Speaker 4>on the kind of consumer side where you know, this

0:27:23.080 --> 0:27:25.760
<v Speaker 4>content is only available behind a paywall. And then again

0:27:25.800 --> 0:27:28.359
<v Speaker 4>to the data point this Bloomberg and fact set and

0:27:28.560 --> 0:27:31.600
<v Speaker 4>FMP and you know, all these different providers, and so

0:27:32.280 --> 0:27:35.280
<v Speaker 4>I think, what all the providers are thinking about is

0:27:35.720 --> 0:27:37.720
<v Speaker 4>how do I make this stuff available to the AI

0:27:37.840 --> 0:27:40.439
<v Speaker 4>without just necessarily making it available for free. And so

0:27:40.480 --> 0:27:43.320
<v Speaker 4>what that looks like with the data owners is content

0:27:43.359 --> 0:27:45.720
<v Speaker 4>licensing deals. Right, Reddit now makes a lot of money

0:27:45.800 --> 0:27:47.800
<v Speaker 4>from selling the Reddit data. Because you have all this

0:27:47.960 --> 0:27:51.880
<v Speaker 4>like super interesting human discussion, you have the various media

0:27:51.920 --> 0:27:55.159
<v Speaker 4>publishers either kind of suing or doing partnerships with or

0:27:55.200 --> 0:28:00.000
<v Speaker 4>both the AI companies. We're very interested in data providers generally,

0:28:00.119 --> 0:28:01.959
<v Speaker 4>Like we did a demo of sessions as to how

0:28:01.960 --> 0:28:03.960
<v Speaker 4>you know you could do a financial research project with

0:28:04.080 --> 0:28:07.000
<v Speaker 4>your coding agents buying the information it needs to put

0:28:07.000 --> 0:28:11.320
<v Speaker 4>together the PDF answer. But we're quite airly in that journey.

0:28:11.320 --> 0:28:13.640
<v Speaker 4>But no, I think there's been lots of proprietary data

0:28:13.680 --> 0:28:15.919
<v Speaker 4>for a long time, and so it's more about how

0:28:15.920 --> 0:28:17.800
<v Speaker 4>do we open that up to AI agents. I'm not

0:28:17.840 --> 0:28:21.240
<v Speaker 4>sure you'd see that much of a constriction on what's

0:28:21.240 --> 0:28:22.359
<v Speaker 4>available on the free Internet.

0:28:22.520 --> 0:28:24.280
<v Speaker 3>But just to push back on that a little bit,

0:28:24.320 --> 0:28:26.399
<v Speaker 3>there's also been a lot of free stuff on the Internet,

0:28:26.480 --> 0:28:28.280
<v Speaker 3>and one of the reasons it's been free is because

0:28:28.320 --> 0:28:32.639
<v Speaker 3>of traffic and advertising. And so if that's not going

0:28:32.720 --> 0:28:35.600
<v Speaker 3>to get as much advertising or traffic anymore, because everything

0:28:35.640 --> 0:28:38.560
<v Speaker 3>is going through an LLM platform and people just aren't

0:28:38.560 --> 0:28:41.840
<v Speaker 3>linking back directly. The temptation would be to try to

0:28:41.880 --> 0:28:45.360
<v Speaker 3>make up that revenue by charging for the actual content.

0:28:47.040 --> 0:28:53.280
<v Speaker 4>Yeah, but that assumes that what the AIS want to

0:28:53.320 --> 0:28:55.520
<v Speaker 4>browse and what the humans want to browse will be

0:28:55.520 --> 0:28:59.160
<v Speaker 4>the same thing, And I'm not sure that'll necessarily be

0:28:59.360 --> 0:29:01.880
<v Speaker 4>the case. Where there'll still be the case that's say

0:29:01.880 --> 0:29:05.680
<v Speaker 4>for media properties, you know that is aimed at human consumption,

0:29:05.880 --> 0:29:08.680
<v Speaker 4>and so they'll do fine with the advertising revenue they had.

0:29:08.680 --> 0:29:11.040
<v Speaker 4>Maybe they have some incremental revenue that they can guess

0:29:11.080 --> 0:29:13.800
<v Speaker 4>from the AI stuff. And then I mean, maybe you're

0:29:13.880 --> 0:29:18.040
<v Speaker 4>right that the really crummy aggregator pages where it's like

0:29:18.120 --> 0:29:20.120
<v Speaker 4>top ten lists. You know, you google something and you

0:29:20.200 --> 0:29:22.840
<v Speaker 4>get some SEO page and there's like a million taboolah

0:29:22.880 --> 0:29:24.440
<v Speaker 4>ads on us that you're trying to kick through, and

0:29:24.480 --> 0:29:27.800
<v Speaker 4>the pop over takes over your screen. Maybe those sites

0:29:28.240 --> 0:29:30.680
<v Speaker 4>have a harder time, But I don't think anyone's going

0:29:30.720 --> 0:29:34.200
<v Speaker 4>to really be too sad about that.

0:29:34.480 --> 0:29:37.040
<v Speaker 2>But you've talked about this yourself, I think in a

0:29:37.120 --> 0:29:40.280
<v Speaker 2>recent speech you gave. It's actually depressing to me because

0:29:40.560 --> 0:29:43.360
<v Speaker 2>now thanks to the vibe coding apps. There's a bunch

0:29:43.400 --> 0:29:45.480
<v Speaker 2>of stuff I would have liked to build, say around

0:29:45.760 --> 0:29:48.600
<v Speaker 2>Twitter data, right, And there was an actual era in

0:29:48.640 --> 0:29:51.400
<v Speaker 2>which a lot of these social platforms are very open

0:29:51.400 --> 0:29:53.920
<v Speaker 2>with their APIs, et cetera. And now everything's sort of

0:29:53.920 --> 0:29:55.760
<v Speaker 2>shut down, so you can't even really, you know, unless

0:29:55.760 --> 0:29:58.280
<v Speaker 2>I want to spend thousands of dollars, you couldn't really

0:29:58.280 --> 0:30:01.600
<v Speaker 2>build like an app that does something with someone's Twitter account,

0:30:01.640 --> 0:30:03.560
<v Speaker 2>et cetera. And I think you talked about this in

0:30:03.560 --> 0:30:07.520
<v Speaker 2>your recent speech. Doesn't this further accelerate the move of

0:30:07.560 --> 0:30:11.360
<v Speaker 2>everyone to just sort of clamp down and allow people

0:30:11.400 --> 0:30:13.640
<v Speaker 2>to roam their site and slop up data.

0:30:14.480 --> 0:30:18.840
<v Speaker 4>Yes, but just to clarify the human roaming has you know,

0:30:18.920 --> 0:30:21.560
<v Speaker 4>you can still browse free. You can still browse Twitter

0:30:21.680 --> 0:30:24.800
<v Speaker 4>for free. What they're clamping down on in some cases

0:30:25.160 --> 0:30:28.840
<v Speaker 4>is AI training scraping where they want to put a

0:30:29.000 --> 0:30:33.320
<v Speaker 4>toll on that. And maybe they didn't kind of intend

0:30:33.680 --> 0:30:36.080
<v Speaker 4>for all that information to be kind of freely available

0:30:36.120 --> 0:30:39.160
<v Speaker 4>to the AI apps, And there you can argue whether

0:30:39.200 --> 0:30:41.240
<v Speaker 4>that should be freely available to Open a eye and

0:30:41.280 --> 0:30:43.000
<v Speaker 4>Google and everyone like that, or they should have to

0:30:43.000 --> 0:30:45.000
<v Speaker 4>pay for us. But it's not the case that are

0:30:45.320 --> 0:30:49.040
<v Speaker 4>very important intellectual commons is of reddis and X and

0:30:49.320 --> 0:30:51.479
<v Speaker 4>all the other asylums that we like to frequent our

0:30:51.520 --> 0:30:52.680
<v Speaker 4>gougway for us as humans.

0:31:08.400 --> 0:31:10.600
<v Speaker 2>You know, you're talking about micro transactions, and people have

0:31:10.640 --> 0:31:14.040
<v Speaker 2>been talking about micro transactions for literally decades, probably in

0:31:14.120 --> 0:31:16.560
<v Speaker 2>the example you gave of oh, why can't we just

0:31:16.560 --> 0:31:18.959
<v Speaker 2>buy an article for fifty cents? I think there's various

0:31:18.960 --> 0:31:22.640
<v Speaker 2>reasons why that never took off, But one aspect is

0:31:22.680 --> 0:31:26.280
<v Speaker 2>just the cost of a transaction. And with theoretically, particularly

0:31:26.360 --> 0:31:30.640
<v Speaker 2>with like stable coins, you could have almost free transactions.

0:31:30.960 --> 0:31:35.440
<v Speaker 2>Are you seeing actual use of stable coins in sort

0:31:35.480 --> 0:31:39.520
<v Speaker 2>of B to B transactions because the sheer cost is

0:31:39.560 --> 0:31:42.240
<v Speaker 2>so low? Like, where do stable coins come into this?

0:31:43.400 --> 0:31:47.040
<v Speaker 4>Yeah, you're right. This when you have this pay by

0:31:47.080 --> 0:31:51.280
<v Speaker 4>the SIP model, you obviously just can't economically speaking, have

0:31:51.640 --> 0:31:56.080
<v Speaker 4>kind of a an individual card transaction per per usage.

0:31:56.160 --> 0:31:58.680
<v Speaker 4>And by the way, this is the economic model of

0:31:58.720 --> 0:32:03.160
<v Speaker 4>the AI economy because you have marginal costs for each token,

0:32:03.600 --> 0:32:07.040
<v Speaker 4>and so no one really offers an all you can

0:32:07.080 --> 0:32:09.720
<v Speaker 4>eat plan. You can subscribe to chat, GPT or cloud

0:32:09.840 --> 0:32:11.480
<v Speaker 4>or something like that, and you'll have a plan and

0:32:11.480 --> 0:32:15.480
<v Speaker 4>you'll eventually hit usage limits, or you can pay on

0:32:15.520 --> 0:32:17.400
<v Speaker 4>an API basis, and you know you'll top up with

0:32:17.480 --> 0:32:19.360
<v Speaker 4>some amount of credits and then burn down the tokens.

0:32:19.480 --> 0:32:24.400
<v Speaker 4>But everyone charges per usage at some level, and so

0:32:24.520 --> 0:32:27.360
<v Speaker 4>then what do you do? And the kind of common

0:32:27.360 --> 0:32:28.600
<v Speaker 4>mode which we power a lot of, is kind of

0:32:28.640 --> 0:32:31.080
<v Speaker 4>this usage based billing. We actually bought a company on

0:32:31.160 --> 0:32:33.920
<v Speaker 4>Metronome to power that where you track credits, right, and

0:32:33.920 --> 0:32:35.800
<v Speaker 4>so that kind of telco billing, you have your card

0:32:35.840 --> 0:32:38.920
<v Speaker 4>on file and then you track credits. We are quite

0:32:38.920 --> 0:32:42.479
<v Speaker 4>excited about what you're referencing, which is stable coins for this.

0:32:43.120 --> 0:32:44.520
<v Speaker 4>You're asking kind of how much are we seeing of

0:32:44.560 --> 0:32:47.840
<v Speaker 4>it right now? Not that much yet, but we're building

0:32:47.880 --> 0:32:51.400
<v Speaker 4>out all the infrastructure for us. The place where I

0:32:51.560 --> 0:32:55.160
<v Speaker 4>think stable coins could be really exciting is you don't

0:32:55.240 --> 0:32:58.360
<v Speaker 4>have to then go have a relationship with all these services.

0:32:58.400 --> 0:33:00.600
<v Speaker 4>And so if you want a vibe code little website

0:33:00.640 --> 0:33:02.360
<v Speaker 4>and you're like, Okay, I'm going to buy the domain

0:33:02.360 --> 0:33:04.640
<v Speaker 4>from cloud flare and host on versil and all these things,

0:33:04.880 --> 0:33:06.920
<v Speaker 4>you know you've had the experience of you have to

0:33:06.920 --> 0:33:09.160
<v Speaker 4>go and sign up for all these services and these things.

0:33:09.400 --> 0:33:11.480
<v Speaker 4>And we think that experience of signing up for all

0:33:11.480 --> 0:33:13.800
<v Speaker 4>these services should go away, and so we are making

0:33:13.800 --> 0:33:15.760
<v Speaker 4>as where you don't need to do that, and paying

0:33:15.880 --> 0:33:18.360
<v Speaker 4>via stable coins could be one way where you pay

0:33:18.760 --> 0:33:23.120
<v Speaker 4>per web requester, you know, per individual use very small

0:33:23.120 --> 0:33:25.120
<v Speaker 4>amounts and you don't have to go sign up for

0:33:25.120 --> 0:33:26.160
<v Speaker 4>a whole bunch of different services.

0:33:27.000 --> 0:33:30.080
<v Speaker 3>So I realized the agent to commerce is a spectrum

0:33:30.200 --> 0:33:33.480
<v Speaker 3>of services, everything from just simply filling out a form

0:33:33.920 --> 0:33:37.280
<v Speaker 3>to giving an agent a certain amount of wallet spend

0:33:37.280 --> 0:33:39.360
<v Speaker 3>and saying, go off and figure out my life for

0:33:39.400 --> 0:33:44.040
<v Speaker 3>me and spend the following on whatever. Everyone also likes

0:33:44.080 --> 0:33:47.320
<v Speaker 3>to talk about bots going wild, right and going rogue,

0:33:47.400 --> 0:33:49.880
<v Speaker 3>and so I imagine if you are giving an agent

0:33:49.960 --> 0:33:52.160
<v Speaker 3>a certain amount of money and telling it to spend

0:33:52.240 --> 0:33:56.680
<v Speaker 3>in a certain way instruction specificity can vary. But what

0:33:56.880 --> 0:33:59.800
<v Speaker 3>happens if things go bad or what happens if you're

0:34:00.880 --> 0:34:05.680
<v Speaker 3>dissatisfied with the choice that the agent makes? Whose fault

0:34:05.840 --> 0:34:08.880
<v Speaker 3>is that? Like, where does the liability actually lie?

0:34:09.239 --> 0:34:13.680
<v Speaker 4>I think this concern is quite overstated because one the

0:34:13.800 --> 0:34:16.880
<v Speaker 4>agents can do a huge amount of useful work for

0:34:16.960 --> 0:34:19.359
<v Speaker 4>you while there's still a human in the loop. And

0:34:19.520 --> 0:34:22.440
<v Speaker 4>so imagineif claud code asks you are you okay if

0:34:22.480 --> 0:34:25.120
<v Speaker 4>I spend this amount and you just have to hit enter.

0:34:25.480 --> 0:34:28.719
<v Speaker 4>That's much better than the experience of signing up for

0:34:28.760 --> 0:34:30.560
<v Speaker 4>a service and clicking around the webface and things like that.

0:34:30.600 --> 0:34:32.680
<v Speaker 4>So you've still saved a huge amount of time, even

0:34:32.719 --> 0:34:34.960
<v Speaker 4>if you're kind of reviewing the transaction. Similarly, again, in

0:34:35.000 --> 0:34:37.840
<v Speaker 4>the consumer use case, the way we suggest people visualize

0:34:37.840 --> 0:34:39.640
<v Speaker 4>agentic commerce is you still have a human in the

0:34:39.680 --> 0:34:43.359
<v Speaker 4>loop deciding, making the final decision of both what thing

0:34:43.400 --> 0:34:46.680
<v Speaker 4>I buy and am I okay spending this much money?

0:34:46.920 --> 0:34:49.600
<v Speaker 4>But the AIS can still be hugely beneficial as part

0:34:49.640 --> 0:34:51.920
<v Speaker 4>of your shopping journey, even if you're as a human

0:34:51.960 --> 0:34:54.440
<v Speaker 4>signing off on that transaction. And then you get a

0:34:54.440 --> 0:34:56.520
<v Speaker 4>bit into delegated authority. It's kind of like, you know,

0:34:56.560 --> 0:34:59.120
<v Speaker 4>we run a you know at Stripe, a large company,

0:34:59.160 --> 0:35:01.120
<v Speaker 4>and we spend dollars a year and there's lots of

0:35:01.160 --> 0:35:03.359
<v Speaker 4>delegated authority. You might say, what if you have one

0:35:03.560 --> 0:35:05.719
<v Speaker 4>crazy person who makes a bad spending decision and they

0:35:05.760 --> 0:35:07.640
<v Speaker 4>occasionally have that, and you know, how do you solve

0:35:07.680 --> 0:35:09.920
<v Speaker 4>it? It's like, I don't know, give people spending limits on

0:35:09.960 --> 0:35:11.960
<v Speaker 4>how much they can spend, and you you know, whack

0:35:11.960 --> 0:35:14.560
<v Speaker 4>them on the knuckles if they do something really crazy

0:35:14.600 --> 0:35:17.320
<v Speaker 4>and you just solve it with kind of sensible limits

0:35:17.320 --> 0:35:20.080
<v Speaker 4>and delegated authority and approval process. And it's kind of

0:35:20.080 --> 0:35:21.480
<v Speaker 4>the same with an agent.

0:35:21.760 --> 0:35:23.319
<v Speaker 2>Well, this gets me to a question that I wanted

0:35:23.360 --> 0:35:26.120
<v Speaker 2>to ask about running a big company in the age

0:35:26.560 --> 0:35:32.280
<v Speaker 2>of AI. Things are changing insanely fastly fast, fastly fast.

0:35:32.320 --> 0:35:36.719
<v Speaker 2>Things are changing. Things are changing extremely fast. And there

0:35:36.719 --> 0:35:39.200
<v Speaker 2>are certain things that people were excited about last year

0:35:39.280 --> 0:35:41.560
<v Speaker 2>that didn't fizzle out in the same way, or certain

0:35:41.600 --> 0:35:44.160
<v Speaker 2>things that people got really excited about even in December

0:35:44.200 --> 0:35:47.239
<v Speaker 2>twenty twenty five that became the next hot thing for

0:35:47.360 --> 0:35:50.520
<v Speaker 2>Stripe specifically or for a company. How do you think

0:35:50.560 --> 0:35:53.640
<v Speaker 2>about say like, Okay, here's a thing that we want

0:35:53.680 --> 0:35:56.200
<v Speaker 2>to exploit. Here's a moment, and we want to take

0:35:56.239 --> 0:35:58.200
<v Speaker 2>advantage of it, and we're going to build the thing

0:35:58.280 --> 0:36:02.840
<v Speaker 2>for this moment, versus is we want to allocate resources

0:36:03.160 --> 0:36:06.200
<v Speaker 2>for anticipating what's going to be the thing twenty four

0:36:06.400 --> 0:36:09.600
<v Speaker 2>months from now, explore where this is going. How do

0:36:09.640 --> 0:36:13.760
<v Speaker 2>you think about the sort of resource allocation between exploring

0:36:13.800 --> 0:36:17.040
<v Speaker 2>and exploiting in such a fast moving environment From the

0:36:17.080 --> 0:36:19.040
<v Speaker 2>corporate standpoint.

0:36:18.760 --> 0:36:22.680
<v Speaker 4>I would say you need to be very flexible because,

0:36:22.680 --> 0:36:25.200
<v Speaker 4>as you're saying, if your information is three months out

0:36:25.200 --> 0:36:27.080
<v Speaker 4>of date or six months out of dates, it's just

0:36:27.160 --> 0:36:31.239
<v Speaker 4>woefully old. And so we try to be pretty flexible.

0:36:31.480 --> 0:36:33.840
<v Speaker 4>And I know there's AI somehow brings out a desire

0:36:33.880 --> 0:36:38.040
<v Speaker 4>for thought leadership in people. Every brand plants, but yeah,

0:36:38.160 --> 0:36:39.760
<v Speaker 4>and just I don't know, like we have more questions

0:36:39.760 --> 0:36:41.560
<v Speaker 4>and answers and we're trying to figure it out as

0:36:41.560 --> 0:36:43.359
<v Speaker 4>we go through. So that's one. It's kind of having

0:36:43.360 --> 0:36:46.719
<v Speaker 4>the right level of humility. The second thing is you

0:36:46.800 --> 0:36:49.040
<v Speaker 4>kind of need to have the similarly, the right level

0:36:49.040 --> 0:36:51.640
<v Speaker 4>of AI psychosis that the dose makes the poison, where

0:36:51.680 --> 0:36:54.440
<v Speaker 4>you need to really believe in the capabilities of the models,

0:36:54.840 --> 0:36:57.759
<v Speaker 4>but you also have to be willing to reason about

0:36:57.760 --> 0:37:00.279
<v Speaker 4>the limits. And so to give you an example, really

0:37:00.320 --> 0:37:05.399
<v Speaker 4>amazing at writing codes and huge productivity uplift there if

0:37:05.400 --> 0:37:06.560
<v Speaker 4>you try to do anything. I don't know if you

0:37:06.560 --> 0:37:08.839
<v Speaker 4>guys have tried to do anything like a financial analysis

0:37:08.880 --> 0:37:12.239
<v Speaker 4>with the models. They're just horrible at numbers, numerous and

0:37:12.320 --> 0:37:14.719
<v Speaker 4>they can kind of fool you because they can put

0:37:14.760 --> 0:37:17.279
<v Speaker 4>together something that they can build a really nice spreadsheet,

0:37:17.320 --> 0:37:19.400
<v Speaker 4>but you're like but the number is just go completely

0:37:19.440 --> 0:37:21.920
<v Speaker 4>wrong halfway through the spreadsheet. Oh great, points, you're absolutely right,

0:37:22.200 --> 0:37:24.200
<v Speaker 4>and so you need to have kind of a bit

0:37:24.200 --> 0:37:26.120
<v Speaker 4>of a fingertip sense for what the models are good

0:37:26.120 --> 0:37:28.680
<v Speaker 4>at versus bad at. I kind of think of this

0:37:29.400 --> 0:37:31.759
<v Speaker 4>in you split up the company into the traditional you

0:37:31.760 --> 0:37:34.200
<v Speaker 4>know this, R and D go to Marcus and GNA,

0:37:34.480 --> 0:37:37.040
<v Speaker 4>and if you think about the different domains, they work

0:37:37.280 --> 0:37:42.200
<v Speaker 4>quite differently. Within engineering, engineers have always been passionate about

0:37:42.200 --> 0:37:46.080
<v Speaker 4>tools and better tools, and any kind of a half

0:37:46.160 --> 0:37:50.560
<v Speaker 4>self respecting engineer is very eagerly adopting AI. You don't

0:37:50.600 --> 0:37:52.360
<v Speaker 4>get too many laggards, and so we have seen a

0:37:52.400 --> 0:37:55.960
<v Speaker 4>huge amount of adoption within software engineering at Stripe that's

0:37:56.000 --> 0:37:58.239
<v Speaker 4>going really quickly. I don't think we're at the end

0:37:58.239 --> 0:38:01.160
<v Speaker 4>of state, but we're pretty like that machine, I would say,

0:38:01.200 --> 0:38:03.160
<v Speaker 4>is pretty well set up to be in this self

0:38:03.200 --> 0:38:05.600
<v Speaker 4>improving loop because the people who are kind of doing

0:38:05.640 --> 0:38:08.440
<v Speaker 4>the engineering day in day out also think about how

0:38:08.440 --> 0:38:10.600
<v Speaker 4>can I better assmate this process, how can I use

0:38:10.640 --> 0:38:13.399
<v Speaker 4>AI to make it work faster? And so a lot

0:38:13.400 --> 0:38:15.279
<v Speaker 4>of bugs that are fixed at Stripe no one ever

0:38:15.360 --> 0:38:18.080
<v Speaker 4>opens an editor for them. They just hit the fix

0:38:18.160 --> 0:38:21.640
<v Speaker 4>this bug button in the interface, and that'sgentically, so that's

0:38:21.800 --> 0:38:25.080
<v Speaker 4>software engineering on sales and kind of go to market.

0:38:25.400 --> 0:38:29.200
<v Speaker 4>What helps you is that it is the most measurable

0:38:29.239 --> 0:38:32.560
<v Speaker 4>domain inside of tech companies and companies broadly, and so

0:38:32.960 --> 0:38:36.360
<v Speaker 4>you can reason about the specific productivity of a specific

0:38:36.440 --> 0:38:39.440
<v Speaker 4>salesperson in a way that you can't with a software

0:38:39.440 --> 0:38:42.279
<v Speaker 4>engineer or a lawyer or something where any kind of

0:38:42.280 --> 0:38:45.080
<v Speaker 4>metrics there is very subject to Goodheart's law, whereas with

0:38:45.160 --> 0:38:47.640
<v Speaker 4>good market it's measurable. And so we have seen at

0:38:47.680 --> 0:38:52.000
<v Speaker 4>Stripe at least our sellers are super into AI. They're

0:38:52.040 --> 0:38:55.960
<v Speaker 4>adopting it very eagerly. And you can't ascribe causality in

0:38:56.000 --> 0:38:58.399
<v Speaker 4>the productivity numbers, but the productivity numbers are very good.

0:38:58.520 --> 0:39:01.440
<v Speaker 4>The place where I think it's tricky is within the

0:39:01.640 --> 0:39:05.319
<v Speaker 4>other general functions you think about legal and finance and

0:39:05.560 --> 0:39:07.600
<v Speaker 4>risk and things like that, and there there is a

0:39:07.600 --> 0:39:10.719
<v Speaker 4>lot of AI happening, but it's just tricky because one

0:39:11.480 --> 0:39:13.840
<v Speaker 4>there's a huge amount of infrastructure work that needs to happen.

0:39:13.840 --> 0:39:16.080
<v Speaker 4>It's like, okay, we actually have to get this financial

0:39:16.160 --> 0:39:18.840
<v Speaker 4>data into a form where it's usable by the AIS,

0:39:18.840 --> 0:39:20.200
<v Speaker 4>and we used to keep it under lock and key

0:39:20.239 --> 0:39:21.680
<v Speaker 4>and now we need to kind of load it in

0:39:21.680 --> 0:39:23.359
<v Speaker 4>a way that the AI can use. So we had

0:39:23.360 --> 0:39:27.280
<v Speaker 4>a big infrastructure builded stripe to make the data usable

0:39:27.280 --> 0:39:28.960
<v Speaker 4>to the AIS, but also kind of keep it locked

0:39:28.960 --> 0:39:31.680
<v Speaker 4>down appropriately and things like that. And then, like I said,

0:39:31.800 --> 0:39:34.759
<v Speaker 4>the AIS are just uneven in which domains they are

0:39:34.800 --> 0:39:37.040
<v Speaker 4>good at. And so if it is a coding problem

0:39:37.160 --> 0:39:38.760
<v Speaker 4>or if it could be turned into a coding problem,

0:39:38.840 --> 0:39:41.239
<v Speaker 4>very good at that. The public tax code and the

0:39:41.239 --> 0:39:43.920
<v Speaker 4>public legal code, they're very good at that because it's

0:39:44.000 --> 0:39:47.360
<v Speaker 4>texts that they've been trained on. But working with I

0:39:47.360 --> 0:39:50.480
<v Speaker 4>would say specific financial data stripe or kind of specific

0:39:50.600 --> 0:39:53.000
<v Speaker 4>internal stuff that we have, that's just kind of harder

0:39:53.000 --> 0:39:55.000
<v Speaker 4>to get good results out. It's not impossible, and the

0:39:55.000 --> 0:39:56.640
<v Speaker 4>models will improve a lot, but I would say that

0:39:56.680 --> 0:39:58.840
<v Speaker 4>is kind of the trickiest demain to get great results.

0:39:59.400 --> 0:40:01.840
<v Speaker 3>So, just going back to the beginning of this conversation,

0:40:01.960 --> 0:40:05.480
<v Speaker 3>we talked about how the Internet basically runs on commerce,

0:40:05.520 --> 0:40:07.799
<v Speaker 3>and if the nature of that commerce is changing, you

0:40:07.840 --> 0:40:10.960
<v Speaker 3>would expect some impact on the Internet. We've been asking

0:40:10.960 --> 0:40:14.239
<v Speaker 3>you various questions about that, but I'm just gonna ask

0:40:14.280 --> 0:40:18.240
<v Speaker 3>you very directly, what is your sort of broad vision

0:40:18.719 --> 0:40:21.880
<v Speaker 3>of the Internet. In the world of agentic commerce.

0:40:23.080 --> 0:40:26.560
<v Speaker 4>We're very excited for the intelligence explosion, and so in

0:40:26.680 --> 0:40:31.800
<v Speaker 4>our pocket of the Internet, we are seeing much more

0:40:32.520 --> 0:40:35.480
<v Speaker 4>entrepreneurship happening. That shows up in the numbers. So to

0:40:35.480 --> 0:40:38.719
<v Speaker 4>give you a sense, new business creation on Stripe in

0:40:38.800 --> 0:40:42.759
<v Speaker 4>Q one was up seventy one percent a year over year.

0:40:43.120 --> 0:40:45.360
<v Speaker 4>That business generally is not growing back quickly. It's like

0:40:45.400 --> 0:40:49.280
<v Speaker 4>the leading edge numbers are seeing much more business creation.

0:40:49.680 --> 0:40:52.200
<v Speaker 4>You see this in other numbers too. So the app

0:40:52.239 --> 0:40:55.440
<v Speaker 4>store like number of app launches was quite flat for

0:40:55.520 --> 0:40:57.600
<v Speaker 4>many many years, and now it's seeing kind of similar

0:40:57.600 --> 0:41:00.759
<v Speaker 4>growth to that, and so so there are going to

0:41:00.800 --> 0:41:06.319
<v Speaker 4>be many, many fruits of the intelligence explosion. But we

0:41:06.400 --> 0:41:09.879
<v Speaker 4>get quite excited about the idea that you have more

0:41:09.920 --> 0:41:14.719
<v Speaker 4>people creating companies and maybe you get more dynamism. Right,

0:41:14.760 --> 0:41:16.279
<v Speaker 4>we talked about some of the effects where you know

0:41:16.320 --> 0:41:18.880
<v Speaker 4>you'll maybe see more price competition. If you work at

0:41:18.880 --> 0:41:20.799
<v Speaker 4>a big company and you think, hey, the way we

0:41:20.840 --> 0:41:22.680
<v Speaker 4>are doing this is really silly. I could do it

0:41:22.719 --> 0:41:25.040
<v Speaker 4>so much better. The bar to you being able to

0:41:25.120 --> 0:41:28.840
<v Speaker 4>quit the company and develop a competing better offering is

0:41:28.880 --> 0:41:32.279
<v Speaker 4>now lower. Because you have more power available to you.

0:41:32.280 --> 0:41:35.359
<v Speaker 4>You can recruit the intelligence that's available to you, and

0:41:35.440 --> 0:41:40.480
<v Speaker 4>so our prediction is that you get more economic dynamism,

0:41:40.560 --> 0:41:42.560
<v Speaker 4>which we're already seeing in our leading edge numbers. You know,

0:41:42.600 --> 0:41:45.279
<v Speaker 4>we're seeing more startup formation. But we talked about this

0:41:45.280 --> 0:41:47.560
<v Speaker 4>about stripe sessions, you know, kind of an Ecocian sense.

0:41:47.840 --> 0:41:51.319
<v Speaker 4>Maybe you see smaller firms and more of them because

0:41:51.360 --> 0:41:53.160
<v Speaker 4>it's easier for them to coordinate.

0:41:53.200 --> 0:41:56.480
<v Speaker 2>To gentlemen, John, I have like a million more questions

0:41:56.520 --> 0:41:58.719
<v Speaker 2>for you, but I'm aware of the time, so let's

0:41:58.760 --> 0:42:00.480
<v Speaker 2>just leave it there. This was such a We really

0:42:00.560 --> 0:42:03.279
<v Speaker 2>enjoyed getting the chance to talk and would love to

0:42:03.280 --> 0:42:19.560
<v Speaker 2>have you back some time. Absolutely, Tracy, I really thought

0:42:19.560 --> 0:42:21.640
<v Speaker 2>that conversation was super interesting.

0:42:21.680 --> 0:42:21.840
<v Speaker 4>I do.

0:42:21.920 --> 0:42:24.040
<v Speaker 2>I mean, just to start, there's a lot here. This

0:42:24.120 --> 0:42:26.759
<v Speaker 2>is a big deal. I think we where it's gonna go,

0:42:27.520 --> 0:42:30.480
<v Speaker 2>the question of whether just commerce directly, and then also

0:42:30.520 --> 0:42:33.520
<v Speaker 2>your question of the Internet more broadly. There's some pretty

0:42:33.520 --> 0:42:38.000
<v Speaker 2>big questions and big implications from which way some of

0:42:38.040 --> 0:42:39.120
<v Speaker 2>this stuff unfolds.

0:42:39.320 --> 0:42:42.799
<v Speaker 3>Yeah, and I'm glad that John appreciates the enjoyability of

0:42:42.800 --> 0:42:47.160
<v Speaker 3>the human Yeah. Well, yes, I do have questions about

0:42:47.280 --> 0:42:51.240
<v Speaker 3>I guess discoverability when it comes to agents so everyone

0:42:51.280 --> 0:42:54.400
<v Speaker 3>by now knows. The example of you go on Netflix

0:42:54.480 --> 0:42:58.320
<v Speaker 3>the first video or movie TV series you ever watched

0:42:58.360 --> 0:43:02.320
<v Speaker 3>is incredibly important because algorithms sort of builds itself around

0:43:02.320 --> 0:43:04.839
<v Speaker 3>that one choice, and if you watch something stupid, then

0:43:05.040 --> 0:43:07.960
<v Speaker 3>forever and ever, it's gonna like yeah, yeah, yeah, has

0:43:08.000 --> 0:43:11.719
<v Speaker 3>this one demographic. So there is a tendency for algos

0:43:11.760 --> 0:43:15.120
<v Speaker 3>to sort of cluster among like recognizable patterns, so it

0:43:15.200 --> 0:43:19.000
<v Speaker 3>becomes harder to discover new things, new products. I will

0:43:19.000 --> 0:43:23.279
<v Speaker 3>say some algos obviously do it better than others. YouTube's

0:43:23.320 --> 0:43:27.040
<v Speaker 3>algorithm I find like actually really phenomenal for resurfacing or

0:43:27.600 --> 0:43:28.880
<v Speaker 3>for surfacing new things.

0:43:28.960 --> 0:43:29.160
<v Speaker 4>Well.

0:43:29.160 --> 0:43:32.160
<v Speaker 2>Within LLLMS itself, I find memory to be a very

0:43:32.680 --> 0:43:34.799
<v Speaker 2>double edged sword, which is on some level, I do

0:43:34.840 --> 0:43:37.080
<v Speaker 2>think it's more useful when it knows a little bit

0:43:37.080 --> 0:43:39.680
<v Speaker 2>about the context of the user. Yeah, but there be

0:43:39.760 --> 0:43:42.520
<v Speaker 2>times when will shoehorn any like you did a query

0:43:42.560 --> 0:43:44.160
<v Speaker 2>six months ago, and I will try to bring it

0:43:44.200 --> 0:43:46.799
<v Speaker 2>back around to that. I think there's a lot there.

0:43:46.960 --> 0:43:50.120
<v Speaker 2>I think there's a lot there with the future of advertising. Yeah,

0:43:50.280 --> 0:43:53.920
<v Speaker 2>just setting aside, what is the equivalent of SEO in

0:43:54.040 --> 0:43:56.560
<v Speaker 2>the LLLM, we should probably do an episode from the

0:43:56.600 --> 0:43:59.000
<v Speaker 2>perspective of retailers that are really having to think about

0:43:59.160 --> 0:44:00.759
<v Speaker 2>how they surface within.

0:44:00.680 --> 0:44:03.600
<v Speaker 3>Totally, so that that in itself is a huge shift

0:44:03.640 --> 0:44:06.160
<v Speaker 3>if you're a retailer and now you're trying to target

0:44:06.280 --> 0:44:09.400
<v Speaker 3>bots as well as humans. And then the overall question

0:44:09.680 --> 0:44:13.400
<v Speaker 3>of what happens to the Internet in this new world,

0:44:13.520 --> 0:44:16.720
<v Speaker 3>Like I tend to be very cynical about the overall

0:44:16.719 --> 0:44:19.239
<v Speaker 3>direction of the Internet and just assume that every new

0:44:19.480 --> 0:44:21.680
<v Speaker 3>advance in technology is going to make it worse, but

0:44:21.800 --> 0:44:25.120
<v Speaker 3>like you could see a future where the ability to

0:44:25.160 --> 0:44:29.680
<v Speaker 3>do seamless micro transactions basically means that like everyone starts

0:44:29.800 --> 0:44:32.920
<v Speaker 3>charging for their content for their APIs, and so you

0:44:32.960 --> 0:44:35.440
<v Speaker 3>actually have to pay a fee to be on the Internet.

0:44:35.640 --> 0:44:37.680
<v Speaker 2>This is what I mean, Like the end of freeism,

0:44:38.360 --> 0:44:41.160
<v Speaker 2>I think is an interesting question. I also just personally,

0:44:41.600 --> 0:44:45.080
<v Speaker 2>I find it very validating that, like I'm not crazy

0:44:45.120 --> 0:44:47.440
<v Speaker 2>that actually, like being able to do something at a

0:44:47.520 --> 0:44:50.800
<v Speaker 2>dome like buying a domain name is something that people

0:44:50.840 --> 0:44:53.040
<v Speaker 2>other people thought needed to be solved, you know what

0:44:53.080 --> 0:44:56.520
<v Speaker 2>I'm saying, So like some of these things seem very special.

0:44:56.800 --> 0:44:58.320
<v Speaker 2>That stripe and now it's in the last couple of

0:44:58.360 --> 0:45:01.920
<v Speaker 2>weeks related to both the may name question the related

0:45:01.960 --> 0:45:05.600
<v Speaker 2>to being able to pay an API directly rather than

0:45:05.640 --> 0:45:07.480
<v Speaker 2>go to a website and enter your credit card and

0:45:07.520 --> 0:45:10.600
<v Speaker 2>stuff like that for credits or whatever. I found these

0:45:10.640 --> 0:45:12.640
<v Speaker 2>things to be very annoying and big deals, and I'm

0:45:12.680 --> 0:45:15.480
<v Speaker 2>sort of glad that I feel less crazy, like, actually,

0:45:15.520 --> 0:45:19.319
<v Speaker 2>these are annoying things within the new contemporary landscape.

0:45:19.560 --> 0:45:22.680
<v Speaker 3>Absolutely, And speaking of annoying things, I also feel like

0:45:22.719 --> 0:45:25.120
<v Speaker 3>a big chunk of the future is going to be bots,

0:45:25.200 --> 0:45:27.840
<v Speaker 3>just like negotiating with each other. And I've already heard

0:45:28.360 --> 0:45:31.440
<v Speaker 3>in the insurance sphere. You know, you've heard of insurers

0:45:31.520 --> 0:45:34.759
<v Speaker 3>using AI to like bulk deny claims, right, and then

0:45:34.760 --> 0:45:38.680
<v Speaker 3>I've heard of new AI startups or existing companies using

0:45:38.760 --> 0:45:43.960
<v Speaker 3>AI to contest the insurers, yeah, pushback. And so it

0:45:44.080 --> 0:45:45.720
<v Speaker 3>just feels like it's just going to be bots.

0:45:45.880 --> 0:45:50.400
<v Speaker 2>Like the only money makers are going to be chip

0:45:50.440 --> 0:45:53.920
<v Speaker 2>companies in Korea because there everyone's going to be having

0:45:53.960 --> 0:45:58.239
<v Speaker 2>to get more powerful chips, and old bloomer landlords in

0:45:58.320 --> 0:46:01.560
<v Speaker 2>San Francisco because the employees of AI and Anthropic need

0:46:01.600 --> 0:46:03.040
<v Speaker 2>a place to live and healthcare.

0:46:03.120 --> 0:46:04.640
<v Speaker 3>Yeah, all right, shall we leave it there.

0:46:04.680 --> 0:46:05.439
<v Speaker 2>Let's leave it there.

0:46:05.680 --> 0:46:08.319
<v Speaker 3>This has been another episode of the Oudlots podcast. I'm

0:46:08.360 --> 0:46:10.720
<v Speaker 3>Tracy Alloway. You can follow me at Tracy Alloway.

0:46:10.880 --> 0:46:13.800
<v Speaker 2>And I'm Joe Wisenthal. You can follow me at the Stalwart.

0:46:14.000 --> 0:46:17.120
<v Speaker 2>Follow our guest John Collison, He's at Collision. Follow our

0:46:17.120 --> 0:46:21.200
<v Speaker 2>producers Carmen Rodriguez at Carmen Erman Dash, Ol Bennett at Dashbot,

0:46:21.280 --> 0:46:25.160
<v Speaker 2>Calebrooks at Kelbrooks and Kevin Lozano at Kevin Lloyd Lizano

0:46:25.320 --> 0:46:27.520
<v Speaker 2>and form our odd Loads content. Go to Bloomberg dot

0:46:27.520 --> 0:46:30.000
<v Speaker 2>com slash odd Lots for the daily newsletter and all

0:46:30.040 --> 0:46:32.120
<v Speaker 2>of our episodes, and you can shout about all of

0:46:32.160 --> 0:46:35.160
<v Speaker 2>these topics twenty four to seven in our discord discord

0:46:35.200 --> 0:46:36.600
<v Speaker 2>dot gg slash Odlins.

0:46:36.840 --> 0:46:38.640
<v Speaker 3>And if you enjoy odd Lots, if you like it

0:46:38.680 --> 0:46:40.600
<v Speaker 3>when we talk about the future of the Internet, then

0:46:40.640 --> 0:46:43.840
<v Speaker 3>please leave us a positive review on your favorite podcast platform.

0:46:44.160 --> 0:46:46.520
<v Speaker 3>And remember, if you are a Bloomberg subscriber, you can

0:46:46.560 --> 0:46:49.640
<v Speaker 3>listen to all of our episodes absolutely add free. All

0:46:49.640 --> 0:46:51.520
<v Speaker 3>you need to do is find the Bloomberg channel on

0:46:51.560 --> 0:47:12.759
<v Speaker 3>Apple Podcasts and follow the instructions there. Thanks for listening

0:47:00.239 --> 0:47:00.279
<v Speaker 3>in

0:47:20.160 --> 0:47:20.520
<v Speaker 4>It