WEBVTT

NOTE Sentence-level transcript of https://www.youtube.com/watch?v=h6mi88VrPtQ

NOTE One cue per sentence. Cue ids are the line anchors on /transcripts/h6mi88VrPtQ.html. A cue ends where the next begins, or 2 s after its last word.

s1
00:00:01.309 --> 00:00:03.309
[music]

s2
00:00:12.560 --> 00:00:14.240
Hello everyone.

s3
00:00:14.240 --> 00:00:21.840
Uh last year here at AI Engineer World Fair, uh David Cramer from Sentry had a mildly provocative talk called MCP isn't good yet.

s4
00:00:21.840 --> 00:00:25.040
And back then, MCP was the new kid on the block, right?

s5
00:00:25.040 --> 00:00:26.360
Uh it was like a lot of hype around it.

s6
00:00:26.360 --> 00:00:28.280
People were, you know, were excited about it.

s7
00:00:28.280 --> 00:00:32.800
But also like it wasn't really developed back then very much and it was very clunky.

s8
00:00:32.800 --> 00:00:38.040
And in this talk, David argued, "Hey, like this technology is cool, but it has like a lot of rough edges, right?

s9
00:00:38.040 --> 00:00:42.480
So just you know, go play with it, but you know, have your expectations low, right?"

s10
00:00:42.480 --> 00:00:46.840
By the way, they went on and actually built one of the best MCP servers on the market, right?

s11
00:00:46.840 --> 00:00:52.720
Like Sentry MCP is is is really like very well-designed server, like nice nice design and so on.

s12
00:00:52.720 --> 00:00:58.600
And actually over the the last year, uh MCP became like a standard that's actually widely adopted, you know, across the industry.

s13
00:00:58.600 --> 00:01:04.640
Like the top AI engines like Claude and ChatGPT, actually uh Claude offers MCP connectors, right?

s14
00:01:04.640 --> 00:01:07.040
So you can plug tools into your AI agents.

s15
00:01:07.040 --> 00:01:14.840
Uh uh ChatGPT calls it MC calls it apps, but you can also like, you know, directory of different services you can plug into your Claude.

s16
00:01:14.840 --> 00:01:19.040
And it actually became a standard thing for agent-to-agent interaction, right?

s17
00:01:19.040 --> 00:01:27.360
And uh uh despite a little little hate also about MCP, you know, I have yet to see CI connectors in any of these agents, right?

s18
00:01:27.360 --> 00:01:29.200
So MCP won.

s19
00:01:29.200 --> 00:01:38.280
And so, inspired by David's talk, uh today uh I have a similar talk uh which is called X 402 isn't good yet.

s20
00:01:38.280 --> 00:01:44.760
And in that talk, I would like to argue, you know, that uh while X 402 is very exciting technology, it has also still some rough edges, you know.

s21
00:01:44.760 --> 00:01:53.600
And perhaps if I do it as well, we'll also build one of the best integrations with our X 402 on the market like Sentry did with MCP.

s22
00:01:53.600 --> 00:01:54.360
My name is Jan Černý.

s23
00:01:54.360 --> 00:01:56.080
I'm the founder and CEO of Apify.

s24
00:01:56.080 --> 00:02:01.680
And uh for those who don't know, Apify is the largest marketplace of tools for AI.

s25
00:02:01.680 --> 00:02:04.520
Uh we have about 45,000 of these tools.

s26
00:02:04.520 --> 00:02:06.720
Uh we call them actors.

s27
00:02:06.720 --> 00:02:21.160
And they are spending use cases like, you know, extraction of data from social media sites, e-commerce, hospitality, travel, search engines, maps, but over time also like AI agents or agentic use cases, you know, different automations and so on, right?

s28
00:02:21.160 --> 00:02:32.000
And some of these tools, some of these actors are built by our community, some are built by us, and our community is is making now more than $1 million per month on on payouts

s29
00:02:32.000 --> 00:02:33.000
by selling these tools, right?

s30
00:02:33.000 --> 00:02:38.720
So they build the tools, we sell them to to to users, and you know, we pass the money to them.

s31
00:02:38.720 --> 00:02:40.920
And so it's a thriving marketplace.

s32
00:02:40.920 --> 00:02:44.680
And I guess by now everybody understands like why we are so excited about agentic payments, right?

s33
00:02:44.680 --> 00:02:53.400
Because we really want our tools to be easily accessible to agents, like wherever they are, with whatever protocol is out there.

s34
00:02:53.400 --> 00:02:59.720
Uh just 2 days ago we launched uh together with with Coinbase our our XYO 2 integration.

s35
00:02:59.720 --> 00:03:02.400
Uh I would say the the launch went pretty viral.

s36
00:03:02.400 --> 00:03:04.200
We got like 1 million views.

s37
00:03:04.200 --> 00:03:19.400
Uh and before before this launch, there were about like 2,000 tools available on the on the agentic uh market uh basically on XYO XYO 2. We brought another 20,000

s38
00:03:19.400 --> 00:03:19.640
tools.

s39
00:03:19.640 --> 00:03:28.920
So basically we 10X 10X the size of the of the agentic market uh on XYO XYO 2. So this is very exciting for us and I I we we believe also for the community.

s40
00:03:29.440 --> 00:03:32.800
And actually we're very excited about this topic like long term.

s41
00:03:32.800 --> 00:03:39.519
So actually last year here at AI Engineer World's Fair, I was the only one talking about the agentic commerce and agentic economy in general.

s42
00:03:39.519 --> 00:03:47.680
And really argued that that like in a couple of years, like the most most of the economic economic activity in the world will be done autonomously between agents.

s43
00:03:47.680 --> 00:03:53.280
And actually it looks like uh uh really it picked up.

s44
00:03:53.280 --> 00:04:02.680
Uh I think like now everybody understands that agents, in order to get work done or like longer jobs without human intervention, they will actually need to have budget as well, right?

s45
00:04:02.680 --> 00:04:08.080
It's It's not like you can do a lot of things in this world without without money.

s46
00:04:08.080 --> 00:04:16.239
And once agents, you know, can be trusted with money, they will complete like far longer and, you know, more complex tasks than they can do now.

s47
00:04:16.239 --> 00:04:20.680
So, obviously, a lot of people understand this across the industry.

s48
00:04:20.680 --> 00:04:37.160
So, over the past year or so, we saw a lot of new standards or agentic payments protocol coming to the market because, obviously, every player in finance or or payments is very excited about this opportunity because everybody wants to get a part of this of this like huge future

s49
00:04:37.160 --> 00:04:41.440
agentic economy and and transaction volume.

s50
00:04:41.440 --> 00:04:43.800
So, first was L402.

s51
00:04:43.800 --> 00:04:46.600
It was like in mid 2020.

s52
00:04:46.600 --> 00:05:00.440
But then, MasterCard Agent Pay, we have X242 like Coinbase in my last year, KY Pay from Skyfire with Visa, API 2 by Google, ACP by OpenAI and Stripe, Tab by Visa,

s53
00:05:00.440 --> 00:05:12.240
UCP by Google and Shopify, ACTP by Alipay, MPP by Stripe and Tempol, AMP by Alipay, Apple by UnionPay, APP by OKX, and finally, Agent Pay for Machines by MasterCard.

s54
00:05:12.240 --> 00:05:18.800
You can see this is really becoming a heated battleground and for the future of the agentic commerce.

s55
00:05:18.800 --> 00:05:18.988
And

s56
00:05:18.988 --> 00:05:20.560
[snorts]

s57
00:05:20.560 --> 00:05:24.480
it's really hard to sort of keep track of all the standards and all the technologies.

s58
00:05:24.480 --> 00:05:25.960
We're trying to.

s59
00:05:25.960 --> 00:05:35.320
But, I would say for crypto world, actually, Swix asked all the speakers not to use sloppy AI-generated images in presentations, but I couldn't resist myself here.

s60
00:05:35.320 --> 00:05:46.160
Um I think for crypto world, like the agentic commerce has been like super exciting news like because finally, there is like really solid use case for crypto except for like trading trading and gambling,

s61
00:05:46.160 --> 00:05:51.480
buying illegal substances on marketplaces and hiding money away from your spouses, right?

s62
00:05:51.480 --> 00:05:59.240
So, finally, agentic commerce really brings the like long-sought like use case for crypto that that I actually think is is pretty solid.

s63
00:05:59.240 --> 00:06:00.960
And I'm not like a crypto bro myself.

s64
00:06:00.960 --> 00:06:02.680
I I'm not holding anything.

s65
00:06:02.680 --> 00:06:05.800
Actually, I was fairly skeptical to crypto all the time.

s66
00:06:05.800 --> 00:06:11.600
But I feel that crypto is really well suited for agentic commerce or agentic uh payments.

s67
00:06:11.600 --> 00:06:11.960
Why?

s68
00:06:11.960 --> 00:06:17.720
Because the traditional payment methods uh designed for people are super expensive, right?

s69
00:06:17.720 --> 00:06:24.520
And you know, uh like credit cards, PayPal, or you know, ACH and bank debit, they cannot be used for microtransactions.

s70
00:06:24.520 --> 00:06:28.760
They are just very ineffective uh as we saw in previous presentation as well.

s71
00:06:28.760 --> 00:06:31.440
So, but there's another problem.

s72
00:06:31.440 --> 00:06:32.560
There are buyer disputes.

s73
00:06:32.560 --> 00:06:43.120
Like anybody who's selling things online, you know that uh there are some people who sort of like buy certain services from your website and then dispute the payment and ask for refund, you know, or

s74
00:06:43.120 --> 00:06:45.800
or dispute it through their bank and you have to pay for that.

s75
00:06:45.800 --> 00:06:58.560
Like in like traditional like well, human economy, there are some trust signals you can you you can do with the credit credit cards, you know, uh like Stripe and and others have different services to prevent fraud and so on.

s76
00:06:58.560 --> 00:07:02.720
But in agentic interaction, like you really have no idea who the agent is.

s77
00:07:02.720 --> 00:07:04.320
Like there's no agent identity.

s78
00:07:04.320 --> 00:07:09.360
I mean, there are some standards being developed, but it's really not clear uh who are you transacting with.

s79
00:07:09.360 --> 00:07:12.680
So, you just can't allow them to dispute the payments.

s80
00:07:12.680 --> 00:07:17.520
You really need it it needs to be a one-way transaction and it needs to be like safe for you.

s81
00:07:17.520 --> 00:07:17.919
Right?

s82
00:07:17.919 --> 00:07:21.560
So, I think uh crypto is is is a super position for that.

s83
00:07:21.560 --> 00:07:33.200
But also, there's important part uh crypto, if done well, is like truly decentralized blockchain where where no company has like majority of of, you know, of the of the of the of the vote in the network,

s84
00:07:33.200 --> 00:07:46.520
it can be really decentralized and it can be like a public standard, you know, not owned by a single company who, for example, like Visa or MasterCard, sort of would abuse their dominant power, you know, to to extract fees from the from the from the system.

s85
00:07:46.520 --> 00:07:57.080
So, I am I'm very very bullish on crypto in this in this space and uh there are basically like currently two largest uh crypto payment uh providers for any payments.

s86
00:07:57.080 --> 00:08:02.840
One is XRO2 from from Coinbase and second was in this MPP, machine payments protocol from Stripe.

s87
00:08:02.840 --> 00:08:11.760
Looking at the stats uh just yesterday, uh XRO2 is like 20 times larger in the number of transactions and the the the the volume.

s88
00:08:11.760 --> 00:08:17.840
Uh so, obviously, we went first with implementation of XRO2, but we added in MPP in the process as well.

s89
00:08:17.840 --> 00:08:20.720
And today, I'm going to share like a bit of our experience.

s90
00:08:20.720 --> 00:08:22.800
This was also presented in the slide before.

s91
00:08:22.800 --> 00:08:32.440
Uh XRO2 builds on the uh status code introduced like more like almost 30 years ago in the original HTTP specification uh called 402 payment required.

s92
00:08:32.440 --> 00:08:36.880
So, this status code was waiting for 30 years patiently for someone to pick it up.

s93
00:08:36.880 --> 00:08:43.280
And obviously, Coinbase took that opportunity because obviously, it's great for marketing, you know, we're finally make uh internet money work.

s94
00:08:43.280 --> 00:08:44.800
It's awesome.

s95
00:08:44.800 --> 00:08:45.560
So, how it works?

s96
00:08:45.560 --> 00:08:48.320
I'll just go quickly because we saw it in the last presentation as well.

s97
00:08:48.320 --> 00:08:52.120
So, first, the client initiates like calls server with some API request.

s98
00:08:52.120 --> 00:08:54.600
The server responds and actually, this is important part.

s99
00:08:54.600 --> 00:08:58.440
Specification enforces the server to respond 402 payment required.

s100
00:08:58.440 --> 00:08:59.440
There is no other way to do that.

s101
00:08:59.440 --> 00:09:02.160
It it needs to use the 402.

s102
00:09:02.280 --> 00:09:10.400
Then, you know, the client creates a signature uh by basically withdrawing money from the wallet uh or you know, allocating the budget from from from the wallet.

s103
00:09:10.400 --> 00:09:13.440
Sends uh the signature to the to the server.

s104
00:09:13.440 --> 00:09:20.080
Oh, the server verifies with a facilitator, which can be like Coinbase, for example, whether the transaction is correct.

s105
00:09:20.080 --> 00:09:23.400
It gets uh confirmation that the transaction is is right.

s106
00:09:23.400 --> 00:09:26.200
And then, it's supposed to do the work, right?

s107
00:09:26.200 --> 00:09:28.080
But there is a problem there.

s108
00:09:28.080 --> 00:09:30.880
I'll get to that uh in a second.

s109
00:09:30.880 --> 00:09:41.200
And after the work is done, uh you send a transaction you send a request to the facilitator to settle, which means like, you know, physically transfer the money to to your own wallet.

s110
00:09:41.200 --> 00:09:47.440
And then facilitator performs operation on the blockchain, transaction is confirmed, everything is settled, all good.

s111
00:09:47.440 --> 00:09:49.720
But there is a problem here.

s112
00:09:49.720 --> 00:09:59.760
In this moment, like until until the transaction is is actually submitted to the blockchain, the buyer can use the same wallet and same money to other transaction.

s113
00:09:59.760 --> 00:10:03.360
Basically, there is like nothing preventing the the client from double spending.

s114
00:10:03.360 --> 00:10:14.120
So, you know, uh it can just create like 1,000 signatures like that, send it to 1,000 requests, and then, you know, like um maybe it will not get the result,

s115
00:10:14.120 --> 00:10:20.800
but let's say if it's like a simple API call, you know, where there is like a like zero marginal cost for you as a provider, you can do it.

s116
00:10:20.800 --> 00:10:24.000
You can do the work, you know, before uh you settle.

s117
00:10:24.000 --> 00:10:31.440
But imagine there is like some non-trivial work, or maybe you have to pay external service, and then you realize, "Oh, the money is gone, right?"

s118
00:10:31.440 --> 00:10:35.600
Uh the the the client skipped out on the bill, which is not great.

s119
00:10:35.600 --> 00:10:38.000
So, there is a work around that.

s120
00:10:38.000 --> 00:10:41.839
You can actually uh just do the work after the transaction is settled.

s121
00:10:41.839 --> 00:10:48.120
You just need to make sure you actually get the work done, you don't fail, and so on, because then the clients would be pretty angry, I guess.

s122
00:10:48.120 --> 00:10:54.040
But there is a work around for this, and then you send like 200 OK and payment response, all good.

s123
00:10:54.040 --> 00:10:57.160
So, there is a problem though.

s124
00:10:57.160 --> 00:11:04.839
Like um as I showed before, like uh the standard requires HTTP 402 uh as a first response from the server.

s125
00:11:04.839 --> 00:11:08.920
But MCP Alt requires HTTP 401.

s126
00:11:08.920 --> 00:11:19.120
So, there are like two conflicts in the standards, and you know, each of them are actually enforcing it, and you cannot like sort of like, you know, return two error codes or two status codes at the same time.

s127
00:11:19.120 --> 00:11:21.720
So, how do you companies resolve that?

s128
00:11:21.720 --> 00:11:30.240
Well, quite often they create a dedicated like hostname host uh like let's say x402.alchema.com to serve just the agentic payments gateway.

s129
00:11:30.240 --> 00:11:42.440
So, they implement basically a new API host just to serve the the HTTP payments and then they have like Sorry, mcp.alchemy.com and maybe mpp.alchemy.com, right?

s130
00:11:42.440 --> 00:11:43.800
But it sounds like anti-pattern.

s131
00:11:43.800 --> 00:11:49.440
Why would you have to duplicate like your API host for different payment providers?

s132
00:11:49.440 --> 00:11:53.120
It's like imagine like you had to like amazon.com for different like credit cards.

s133
00:11:53.120 --> 00:11:54.200
You had like 20 different Amazons.

s134
00:11:54.200 --> 00:11:55.120
Like it doesn't make sense, right?

s135
00:11:55.120 --> 00:11:58.240
So So, I think it is like one of the weaknesses.

s136
00:11:58.240 --> 00:12:07.960
It's like I I understand like using HTTP 402 is great for marketing, but I think there should be in protocol some way to circumvent that and use use just purely headers, you know?

s137
00:12:07.960 --> 00:12:14.760
So for example, the payment payment required header without the the the status code.

s138
00:12:14.960 --> 00:12:23.040
And then originally when X-Request-ID was created, it was designed for like fixed payments.

s139
00:12:23.040 --> 00:12:30.240
Uh The the first payment scheme they introduced was called exact and it's like for simple API calls.

s140
00:12:30.240 --> 00:12:36.040
Like there's like a fixed fee per transaction, fixed fee per per call, which is great for I don't know simple APIs.

s141
00:12:36.040 --> 00:12:39.160
But unfortunately, Apify actors are tools on the marketplace.

s142
00:12:39.160 --> 00:12:46.680
They typically perform bad jobs and you know, they can run for, you know, a few seconds, but they can also run for a few hours and consume a lot of resources

s143
00:12:46.680 --> 00:12:47.400
on the way.

s144
00:12:47.400 --> 00:12:52.000
They are like typically like built as-you-go kind of like meter billing.

s145
00:12:52.000 --> 00:12:53.000
So how to do that?

s146
00:12:53.000 --> 00:12:55.000
Like how to put this on X-Request-ID 2?

s147
00:12:55.000 --> 00:13:00.200
So in May 2025, Coinbase introduced X-Request-ID 2 with exact payment scheme.

s148
00:13:00.200 --> 00:13:10.000
In December 2025, they announced the version two of the protocol, which was promising the up to payments payment scheme to kind of fix this problem of like meter billing.

s149
00:13:10.000 --> 00:13:15.640
But it it took actually another like half a year almost to release the the up to finally.

s150
00:13:15.640 --> 00:13:17.640
It was just like two or three months ago.

s151
00:13:17.640 --> 00:13:18.839
So we were super excited about that.

s152
00:13:18.839 --> 00:13:24.040
We were like finally we can make this work for our services.

s153
00:13:24.040 --> 00:13:30.360
But then we realized actually the same double spending problem which is on on on exact is also with with up to.

s154
00:13:30.360 --> 00:13:39.440
I mean, up to it was just a small sort of like improvement to the protocol where when you, you know, call the tool, you say, "Oh, my maximum is $5."

s155
00:13:39.440 --> 00:13:42.840
And then the the the server can charge anything up to $5.

s156
00:13:42.840 --> 00:13:44.480
But it doesn't prevent the double-spending problem.

s157
00:13:44.480 --> 00:13:46.440
So, basically, we are sort of stuck again.

s158
00:13:46.440 --> 00:13:51.400
So, you know, we have to go back to the drawing boards and figure like how to do that.

s159
00:13:51.400 --> 00:14:00.640
And so, one way we we did it was we just use exact payment scheme to kind of like fixed uh like charge a fixed payment.

s160
00:14:00.640 --> 00:14:10.280
And then after the the the the job is done, we we would like refund the the the wallet with the with the leftover money, basically, the money that that wasn't spent.

s161
00:14:10.280 --> 00:14:11.560
I mean, that worked.

s162
00:14:11.560 --> 00:14:15.240
But uh so, you charge, you do the work, you refund the remainder.

s163
00:14:15.240 --> 00:14:18.120
But that means like there's suddenly like two blockchain transactions.

s164
00:14:18.120 --> 00:14:22.960
That means like uh there's a time, you know, to to settle those transactions.

s165
00:14:22.960 --> 00:14:25.800
There might be like some fees associated with that and so on.

s166
00:14:25.800 --> 00:14:32.080
And also, the clients will need to trust the server to kind of like, "Hey, I give you the money, but you give it to me back, right?"

s167
00:14:32.080 --> 00:14:34.280
But I think that that that's that's a minor issue.

s168
00:14:34.280 --> 00:14:35.960
But it just feels somehow clunky.

s169
00:14:35.960 --> 00:14:38.440
Like, why would we need to do these workarounds, you know?

s170
00:14:38.440 --> 00:14:41.680
This protocol should support these things out of the box.

s171
00:14:41.680 --> 00:14:48.120
So, just 2 months ago, uh Coinbase introduced like new payment scheme uh which is called batch settlement, which looks very promising.

s172
00:14:48.120 --> 00:14:50.760
We haven't implemented it yet, so we'll report soon on that.

s173
00:14:50.760 --> 00:14:55.120
But basically, just quickly, it works like So, first, the clients like deposit some money.

s174
00:14:55.120 --> 00:15:01.640
So, basically, it's actually like like real transaction on blockchain using some uh Ethereum virtual machine black magic.

s175
00:15:01.640 --> 00:15:04.280
Basically, uh the money is put in the escrow.

s176
00:15:04.280 --> 00:15:08.240
And then the the client gets back a voucher like from the server.

s177
00:15:08.240 --> 00:15:15.480
Say, "Hey, here is some cryptographic voucher, and you can use it to sign like microtransaction as part of this batch."

s178
00:15:15.480 --> 00:15:26.000
And then like the client sends sends requests, for example, like API calls or, you know, for like individual tokens, whatever, and uh use this like passes this voucher to

s179
00:15:26.000 --> 00:15:27.880
sign the those like a micro payments.

s180
00:15:27.880 --> 00:15:29.840
But this transactions are the basically off-chain.

s181
00:15:29.840 --> 00:15:38.440
They are just like sort of like cryptographically guaranteed locally, but you don't need to like write this like to the to the to the blockchain, which again is inefficient, slow,

s182
00:15:38.440 --> 00:15:40.480
you know, uh expensive.

s183
00:15:40.480 --> 00:15:46.840
And then at some point, you're like, "Hey, I I I accumulated a lot of these like micro transactions, so I just like settle them in batch."

s184
00:15:46.840 --> 00:15:49.680
And then like you basically perform the transaction on blockchain.

s185
00:15:49.680 --> 00:15:56.200
And then you can do this a couple of times and eventually refund the rest of the money like sort of like release the escrow, right?

s186
00:15:56.200 --> 00:15:59.040
So actually this looks really cool, very exciting.

s187
00:15:59.040 --> 00:16:03.480
We'll we're currently working on implementing it now, so we'll see.

s188
00:16:03.480 --> 00:16:06.440
But so how did we resolve like all this to make it work, right?

s189
00:16:06.440 --> 00:16:12.160
So we didn't really want to create like new new endpoints for different payment services.

s190
00:16:12.160 --> 00:16:15.640
We didn't want to like the like hack the variable usage, you know, to our services.

s191
00:16:15.640 --> 00:16:22.600
And also, we really don't want to like tweak too much our API because we have like tens of thousands of customers depending on that API.

s192
00:16:22.600 --> 00:16:30.080
So we just can't like sort of like, you know, do whatever like new agentic payment standard is out there, just implement it right away.

s193
00:16:30.080 --> 00:16:40.120
So so kind of to fix these problems, let me introduce you let me introduce our newest service on Appify, which is called agi.appify.com.

s194
00:16:40.120 --> 00:16:44.120
And AGI is not what you mean it is.

s195
00:16:44.120 --> 00:16:46.680
It's actually it stands for agent general interface.

s196
00:16:46.680 --> 00:16:54.760
So instead of like application programming interface, we have agent general interface that can change anytime but because it's used by agents, so they're flexible, right?

s197
00:16:54.760 --> 00:17:00.120
And on AGI, it's just a simple website with like one markdown document.

s198
00:17:00.120 --> 00:17:04.079
It's not designed for people, so it kind of looks ugly, but it's okay.

s199
00:17:04.079 --> 00:17:12.480
And there's instructions for agents like, "Hey, how can you actually buy things on Appify yourself through Xapo 2, MPP?"

s200
00:17:12.480 --> 00:17:18.640
We can iterate quickly on this on this on this website or on this service because, you know, agents can pick up new version.

s201
00:17:18.640 --> 00:17:25.439
It's not like fixed like API needs to be basically, you know, backwards compatible all the time.

s202
00:17:25.439 --> 00:17:34.320
And the way it works is like the agent comes to agent.apify.com gets basically can buy a prepaid token.

s203
00:17:34.320 --> 00:17:36.520
So basically they say like, "Hey, here's $5.

s204
00:17:36.520 --> 00:17:38.720
Give me Give me a Apify token."

s205
00:17:38.720 --> 00:17:47.720
We give them like Apify token back and then they can use the Apify token through our normal API or through MCP to run our jobs and services, you know,

s206
00:17:47.720 --> 00:17:48.800
normally.

s207
00:17:48.800 --> 00:17:50.640
And it it works pretty well.

s208
00:17:50.640 --> 00:17:52.000
There is like no skill required.

s209
00:17:52.000 --> 00:17:54.760
You just like point your agent to agent.apify.com.

s210
00:17:54.760 --> 00:17:56.320
It picks it up.

s211
00:17:56.320 --> 00:17:59.600
And I have here like a short demo.

s212
00:17:59.600 --> 00:18:00.680
We're running out of time.

s213
00:18:00.680 --> 00:18:03.080
So this is just like example how it works like.

s214
00:18:03.080 --> 00:18:17.600
Actually, the X road ecosystem is like really early so that even, you know, we have to build our own like local wallet tool which you can like create like local like cryptographic key to charge, you know, with money and show QR code.

s215
00:18:17.600 --> 00:18:19.640
Like I mean these things are still not not not not existing.

s216
00:18:19.640 --> 00:18:22.440
I mean the ecosystem is like super super early.

s217
00:18:22.440 --> 00:18:25.200
So I have local wallet with $10.

s218
00:18:25.200 --> 00:18:30.840
Then I call like IGI.apify.com allocate like token with $1.

s219
00:18:30.840 --> 00:18:33.400
I get back 402 payment required.

s220
00:18:33.400 --> 00:18:37.640
So there is like this like super long like payment required signature.

s221
00:18:37.640 --> 00:18:52.160
I use Apify I use the I use our MCPC just like MCPC client to sign the payment and then I can send the Oh.

s222
00:18:52.160 --> 00:18:54.560
Oh oh oh.

s223
00:18:54.600 --> 00:18:58.080
This demo didn't work as expected.

s224
00:18:58.160 --> 00:19:00.320
Here we go.

s225
00:19:01.600 --> 00:19:03.600
Mhm.

s226
00:19:06.240 --> 00:19:08.883
Well, anyway, I have 1 minute left.

s227
00:19:08.883 --> 00:19:10.000
[laughter]

s228
00:19:10.000 --> 00:19:11.000
Demo more come later.

s229
00:19:11.000 --> 00:19:12.360
Sorry about that.

s230
00:19:12.360 --> 00:19:25.000
So, to conclude my presentation, like really like try it out and like try to build try try to use it like actually I try I tried to use it for the first time like a couple of weeks ago because I always thought that oh my god it's somehow complicated, you know, there is a lot of this like

s231
00:19:25.000 --> 00:19:28.080
weird crypto lingo, you know, like I have I like I don't know what it what it means.

s232
00:19:28.080 --> 00:19:31.160
But actually it's really really simple to to play with it.

s233
00:19:31.160 --> 00:19:34.600
You can you know, get to get up and running in like 10 minutes.

s234
00:19:34.600 --> 00:19:36.920
And uh it's still super early.

s235
00:19:36.920 --> 00:19:40.320
Uh I think there's like $1 million transaction volume like per month.

s236
00:19:40.320 --> 00:19:41.240
Like this is nothing, right?

s237
00:19:41.240 --> 00:19:42.680
Like the economy is much much bigger.

s238
00:19:42.680 --> 00:19:44.800
But I think it will sooner ramp up.

s239
00:19:44.800 --> 00:19:55.240
And I think once uh really this like era of like uh token subsidies will end, I mean when the when you really will have to pay for the tokens, you know, that your agents consume,

s240
00:19:55.240 --> 00:20:04.360
I think suddenly this decision whether to build or buy will, you know, make more economic sense actually to buy external, you know, services for a lot of things rather than build from scratch.

s241
00:20:04.360 --> 00:20:14.960
And I think at this time really the agentic payments will explode and uh very soon uh um uh the agentic commerce might uh overtake the normal commerce.

s242
00:20:14.960 --> 00:20:20.520
Thanks a lot for your attention and please come uh to join us uh in our booth.

s243
00:20:20.520 --> 00:20:29.120
And actually I have another talk coming up in 2 hours uh about MCP and CLI, so you can check that one as well in Expo stage two.

s244
00:20:29.160 --> 00:20:29.449
Thank you.

s245
00:20:29.449 --> 00:20:31.449
[applause]