Agent Spending Without Controls — Rodrigo Coelho & Pranav Maheshwari, Edge & Node
Read the talk
Agent Spending Without Controls
Rodrigo Coelho and Pranav Maheshwari explain how Ampersend connects agents to paid tools and checkout, then demonstrate why the ability to pay needs a separate layer that can refuse a transaction.
From a talk by Rodrigo Coelho and Pranav Maheshwari
At a glance
Ideas worth remembering
A paid tool needs more than an MCP connection: the agent also needs a way to pay for access. Ampersend's skill connects the demonstrated workflow to an aggregator that handles those purchases.
The gift demo completes checkout and returns a receipt, but its conflicting spoken amounts leave budget enforcement unresolved.
In the screening simulation, both wallets authorize with screening off. Enabling TRM screening causes the blocklisted wallet's transactions to be denied while the ordinary wallet remains allowed.
Counterparty screening, identity, and spending policy are separate questions. A successful payment does not settle them, and a wallet-blocking demonstration addresses only part of the enterprise requirements.
Paying for a query before paying for a shopping cart
An agent that needs blockchain data faces a practical question: how does it pay for the query? Rodrigo Coelho, CEO of Edge & Node, begins with this problem rather than a shopping checkout. Edge & Node built The Graph, a decentralized blockchain-data indexing protocol that he says has served 1.8 trillion queries. Its experience charging for data provides the starting point for Ampersend, the agentic-commerce project incubated within the company.
The Graph's query micropayment system dates to 2021, and Coelho recalls referencing HTTP 402 in a blog post at the time. Later research asked how agents could obtain data and make those small payments themselves. That work led into collaboration on Coinbase's x402 specification, including contributions drawn from the earlier micropayment and batching system. 1:42
Batching addresses the economics of very small purchases: the network fee for moving money can become an obstacle when the purchased unit is a tiny amount of data. Coelho describes using the prior batching work to reduce gas fees for nanopayments and mentions Circle's Nanopayments as work in a similar direction. The talk establishes the reason to batch, without developing the settlement algorithm or its timing tradeoffs.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Machine-speed spending still leaves a person responsible
Payment protocols are only one piece of the emerging stack. Traditional financial workflows assume a person somewhere in the process deciding whether a payment may proceed. Agents can keep transacting around the clock. Rules that depend on a person stopping to inspect each decision become difficult to apply at that pace—the systems need controls that operate during the transaction flow.
Coelho describes an early market: retail-payment experiments are appearing, while the enterprise teams he speaks with are still preparing infrastructure. In his account, compliance is a condition for adoption. A functioning payment rail answers whether money can move; an institution also needs to decide whether this particular transaction is permitted.
Several different questions sit behind that decision:
- Counterparty screening: Is the recipient or payer a sanctioned entity, or associated with prohibited activity?
- Identity: Who is behind the wallet address presented to the system?
- Spending and policy: Can the agent overspend or take an action that violates the organization's rules?
A bare wallet address supplies little context for those questions. Existing financial systems have identity and compliance processes, and agent transactions need corresponding infrastructure before an enterprise officer can sign off. The responsible person might be a chief legal officer or chief policy officer. Coelho emphasizes the potential scale of fines, including billions of dollars, as the reason governance cannot be an afterthought. Ampersend's proposed role is a financial harness around agentic checkout. The later demonstration will show one part of that harness: wallet screening.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
The same search prompt, with access to a paid endpoint
Pranav Maheshwari turns the infrastructure question into an agent workflow. MCP servers give agents access to tools, but access to a tool's interface does not necessarily include permission to use its paid service. He presents two ways to obtain that permission: register and provide payment details separately with providers such as Exa and Firecrawl, or use a marketplace that aggregates tools and handles their payments.
Ampersend's entry point is a skill file installed in the agent. The intended experience is that a user stays inside the agent while the marketplace supplies access to paid tools and arranges payment. This moves the work of dealing with individual service providers into the aggregator. It also makes the aggregator and its payment infrastructure part of what the agent depends on to finish a task.
The first demo gives two agent sessions the same request: find email information for the head of crypto and blockchain at Mastercard. One session has the Ampersend skill and paid MCP tools; the other, shown in Claude Cowork, does not. The session without the skill returns Mastercard's email format and leaves the remaining lookup to the user. The equipped terminal returns a specific email address, a social handle, and location information. Because the comparison uses different agent environments, it illustrates access to a paid information source rather than isolating the skill file as the sole cause of the difference. 9:30
The causal step is the purchase behind the answer. The equipped agent reaches an endpoint that charges for the lookup, and Ampersend makes a small transaction to enable the search. The payment buys access to information the other session did not retrieve. Maheshwari initially moves on while navigating the transaction view; during the next demo, he returns to show the authorized transaction for this lookup.
This is the basis for Maheshwari's forecast that useful MCP services will increasingly charge. An agent may know which tool would help and still be unable to complete the task if it cannot pay for that tool. A wallet and payment gateway extend the set of services it can actually use.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
From a gift request to an order and tracking
The next request is more personal: buy a Father's Day gift through Shopify UCP, keeping the gift below $10. Maheshwari introduces it with the joke that he is generally a good kid. The terminal is expected to find online shops, identify suitable gifts, and purchase one using the Ampersend wallet. The payment capability now supports a physical order rather than a data lookup.
The workflow combines several capabilities:
- Discovery: Find shops and products that could satisfy the gift request.
- Remembered context: Reuse the user's name, address, phone number, and preferences instead of asking for them at each checkout.
- Purchase and follow-through: Place the order through the wallet, return a receipt, and expose order tracking in the terminal.
The order completes, but the spoken amounts complicate the budget claim. Maheshwari describes a $9 total, then says the purchase took $11, and subsequently calls it a $10 gift. The recording does not resolve whether these are item prices, additional charges, or a verbal slip. The demo therefore supports the checkout-and-receipt workflow; it does not establish that the final charge obeyed the requested limit. The distinction matters for the financial harness introduced earlier: expressing a budget in a prompt and enforcing it at payment time are separate requirements.
While the gift workflow finishes, the discussion returns to selling information. Maheshwari uses Cloudflare's x402 gateway as an example of a bot paying a microtransaction to obtain website content. His economic model is direct: when an agent retrieves information without participating in the site's advertising experience, charging for access offers another way to pay the publisher. He then returns to the gift, describing its payment as settled and showing the placed order and tracking. Both examples use an agent's payment capability to turn a request into access or a completed purchase.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Keep the service the same; change the screening policy
The final demo returns to the merchant's decision to accept money. Buyer-side controls alone cannot answer every question for the seller: a merchant also needs to decide whether the wallet offering payment is allowed to transact. Maheshwari sets up two agents, Good Claw and Bad Claw, against the same paid website-scraping service. Bad Claw's wallet is flagged in the simulation; the explanation leaves open whether the flag comes from actual wallet history or simulated screening data.
The scraping service charges 0.1 cent for access to its information. With screening disabled and that setting saved, both agents' transactions authorize. This is the baseline: the service can accept payment from either wallet, including the flagged one. Payment authorization by itself does not apply the demonstrated blocklist policy.
Maheshwari then enables the screening feature built with TRM. It scans the wallet and changes the authorization result for Bad Claw: transactions that previously worked are rejected or denied, with the blocklisted wallet address given as the reason. Good Claw remains the allowed case. The useful change is selective refusal—the system continues serving the permitted payer while stopping the flagged payer. 18:12
What changes when screening is switched on? The comparison below keeps the two payers and the metered service fixed. It makes the policy's effect visible: the flagged wallet moves from authorized to denied, while the ordinary wallet retains access. This demonstrates a wallet-blocking control, a narrower capability than resolving every identity, spending, or compliance question raised at the beginning.
Ordinary wallet; scraping payment authorized.
Screening changes the flagged wallet's authorization result while preserving the ordinary wallet's access to the 0.1-cent scraping service.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Paid tools need both a way to spend and a way to stop
Maheshwari closes with a forecast about the agent interface: payments will increasingly happen through agent wallets or credit cards, and more MCP tools will become paid services. The proposed user experience combines tool access and payment infrastructure so the user can keep working inside the agent instead of visiting each provider's checkout.
The demos give that proposal two distinct responsibilities. Paying for a tool lets the agent retrieve information or place an order. Screening decides whether a particular payer's transaction should proceed. The closing refusal is as consequential as the earlier purchase: useful agent commerce requires the system to complete permitted transactions and stop prohibited ones.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Resources
Further reading
An earlier interview expands on observing agent interactions, managing budgets, and building above x402 and A2A. It also explains the tradeoff between slower standards collaboration and broader interoperability.
Related talks
- Why Your AI Agent Needs a Wallet: USDC and Nanopayments — Harshal Bhangale, Circle
A related recording focused on wallets and nanopayments, the payment capabilities introduced before Ampersend's demos.
- Your Agent Just Authorized What?! — Jay Mok & Ben Coumes, Paypal
A companion topic for the distinction between an agent requesting a purchase and a payment system authorizing it.
Read the complete timestamped transcript
- 0:01
[music]
- 0:12
All right, thanks for having me. Uh,
- 0:14
today we're going to be speaking about
- 0:15
ampersend and agent spending without
- 0:18
controls, which is the missing
- 0:20
infrastructure layer for AI payments. A
- 0:24
little bit about myself, uh, I'm CEO of
- 0:26
Edge and Node. For those that aren't
- 0:28
aware, we were the team that built the
- 0:30
graph protocol. For those that aren't
- 0:32
aware of that, um it is a blockchain
- 0:35
data indexing protocol. It's been around
- 0:37
since 2018. We have a decentralized
- 0:39
network. Um we've served 1.8 trillion
- 0:43
queries over the years of onchain data
- 0:45
to applications um utilizing blockchain
- 0:50
data. Um I've been a serial entrepreneur
- 0:54
myself and we've incubated a project
- 0:56
within engine node called ampersend uh
- 0:59
in the ejected commerce space which is
- 1:01
what we're going to be talking about
- 1:02
today.
- 1:04
And so we're all aware that payments
- 1:06
have been online for the past 30 years.
- 1:09
Um you know starting in 1981 we had our
- 1:12
first electronic transaction
- 1:14
and fast forward we had a multi-deade
- 1:16
transition. Um, and this is from credit
- 1:19
card payments to online e-commerce
- 1:22
payments. Uh, fast forwarding all the
- 1:24
way to today where we have the rise of
- 1:27
the agent economy and unlocking a new
- 1:29
wave of economic value.
- 1:32
And now we have LLMs and agents
- 1:36
uh that can transact
- 1:38
and we have this underlying payment
- 1:40
infrastructure that's been around for
- 1:42
decades and it's being rebuilt today um
- 1:45
for the agentic economy. we've heard
- 1:47
from many speakers here about how that's
- 1:49
being done. We're going to be discussing
- 1:51
today um our perspective and angle on
- 1:54
it. So we we ourselves at edge and node
- 1:58
were really early into the agentic
- 2:00
commerce world. We actually developed um
- 2:03
a microp payment system for queries back
- 2:05
in 2021. We already referenced the 402
- 2:08
spec back back then in a blog post. And
- 2:11
so back in late 2024, we were looking
- 2:13
into agents and how they would interact
- 2:17
with data, how they would pay for it,
- 2:18
specifically for the graph protocol
- 2:20
itself and making microp payments for
- 2:22
queries. And in our research, we were
- 2:25
kind of looking at how this this could
- 2:28
happen. And then a few weeks later, X42
- 2:30
was released by Coinbase. So we jumped
- 2:33
on immediately with the Coinbase team,
- 2:35
with the Google team, started to
- 2:37
collaborate to the X42 spec. We've
- 2:39
joined the foundation. We've contributed
- 2:41
to the X42 uh spec ourselves leveraging
- 2:44
some of our prior art on the um microp
- 2:47
payment system and uh batching protocol
- 2:50
as part of how it could be utilized to
- 2:53
uh reduce gas fees when you're dealing
- 2:55
in nano payments. Um Circle themselves
- 2:58
came out with their own kind of version
- 2:59
of it called nano payments. Um so we
- 3:02
were also working in similar veins
- 3:05
and so we've seen an explosion of uh
- 3:09
companies emerge solutions technologies
- 3:11
and this kind of agented commerce map
- 3:14
you can see on the screen here that
- 3:16
there's a vast array of companies more
- 3:18
added every day. It's really burgeoning.
- 3:20
Um, and you know, we're just one little
- 3:24
piece in here of people developing, you
- 3:26
know, infrastructure,
- 3:28
um, payment protocols, governance, etc.
- 3:33
And so, traditional payment rails though
- 3:36
were built for humans. Um, you know,
- 3:38
when we're dealing with like financial
- 3:39
institutions specifically, there's kind
- 3:41
of a human in the loop that sets uh the
- 3:44
decision making process of uh whether
- 3:46
that payment is allowed to go through.
- 3:48
But we're dealing with agents that
- 3:50
transact at machine speed and around the
- 3:52
clock. And like I was saying is all
- 3:54
these controls and uh policies and rules
- 3:57
were built for humans and not for uh uh
- 4:02
machines that don't breathe, right? So
- 4:04
we're dealing in um in microscond
- 4:07
machine speed and it's just simply not
- 4:10
going to work in the way it has. And so
- 4:11
we need a new method of doing that. Um
- 4:14
you can see a lot of the transactions uh
- 4:16
exploding. This is sort of over time.
- 4:18
We're seeing um transaction growth over
- 4:21
X42. We're all saying this is coming. It
- 4:24
is still early days. We're uh ourselves
- 4:27
we're seeing a lot of experimentation
- 4:28
kind of with uh with OpenClaw people
- 4:31
making retail payments on an
- 4:33
experimental basis. still not on the
- 4:36
enterprise side as we're talking to uh
- 4:38
many teams. Definitely everyone's
- 4:41
looking at it and building kind of the
- 4:43
infrastructure for when um these use
- 4:47
cases break through. And so that's part
- 4:49
of what we're we'll be displaying today
- 4:51
with Amperson.
- 4:53
But in order for this to really break
- 4:54
through, we need a compliance layer
- 4:56
specifically when you're dealing with
- 4:57
like you know uh almost a quadrillion
- 5:00
dollar industry of the the traditional
- 5:03
financial world. there's a set of rules,
- 5:06
policies, and guidelines that need to be
- 5:07
in place before anything can happen. Uh
- 5:10
beyond just a credit card transaction,
- 5:11
we're dealing with trillions and
- 5:13
trillions of dollars um being transacted
- 5:16
um across the globe. And so we're going
- 5:19
to be honing in a bit on that as part of
- 5:21
the presentation today in the demo
- 5:23
that's coming up. But the compliance
- 5:25
layer is literally like is is this
- 5:29
counterparty um a non-sanction entity?
- 5:32
is this counterparty uh have they been
- 5:34
involved in terrorist activity? Who is
- 5:36
the identity behind this? And when
- 5:39
you're dealing with a Gentic systems,
- 5:40
it's just simply you're presented with
- 5:42
just a wallet address with no kind of
- 5:45
background information on that. And we
- 5:47
need these uh infrastructure layers in
- 5:50
place to um to enable and facilitate
- 5:53
enterprises to feel comfortable to adopt
- 5:55
this um technology. All of these systems
- 5:58
exist in the existing world today. But
- 6:01
uh as we're breaking through into this
- 6:03
um agentic world, we really need to have
- 6:06
all of these pieces uh before uh large
- 6:10
enterprises are going to sign off and uh
- 6:14
give the okay to um implement these. At
- 6:17
the end of the day, there is going to be
- 6:19
a human responsible like a chief legal
- 6:22
officer, a chief policy officer and that
- 6:24
will have to sign off and that person
- 6:27
needs to feel 100% confident that the
- 6:30
systems in place will not allow for um
- 6:34
agents to hallucinate, to go off the
- 6:37
rails, to overspend, um to break policy.
- 6:41
Uh a lot of these compliance issues deal
- 6:44
with large fines into the tens,
- 6:46
hundreds, even billions of dollars. So
- 6:49
these are really important um items and
- 6:53
things to think about from a large
- 6:55
enterprise and financial services
- 6:57
perspective
- 6:59
and governance simply hasn't caught up.
- 7:01
We're again we're early days so we are
- 7:04
part of building up what needs to be put
- 7:06
in place from our view in terms of
- 7:09
allowing this to scale.
- 7:11
And that's why we're building Amperent.
- 7:14
Um, so we're dealing with Agentic
- 7:17
checkouts with a financial harness.
- 7:20
And I'm going to turn it over to my
- 7:22
colleague Prrenoff who is going to show
- 7:24
us a demo. Right.
- 7:25
>> All right. Thanks.
- 7:32
>> All right. Like we said, for agents to
- 7:35
be really useful, we need to give them
- 7:38
tools. Right now they're being used for
- 7:40
coding. If you want to use them to build
- 7:43
better things, you need to give them the
- 7:44
right tools. As of right now, as a AI
- 7:47
industry, we've given them a lot of MCP
- 7:49
servers,
- 7:51
but most of these MP MCP servers are
- 7:54
free of cost. So there are two ways to
- 7:57
make your agents really useful.
- 8:00
One way is you can go to all these
- 8:02
websites like Exop, Firecrawl and so
- 8:06
many more which are getting more and
- 8:08
more bigger with more MCP servers coming
- 8:11
to play and you got to put in your
- 8:12
credit card and you make your agent
- 8:14
better or there is a better way that you
- 8:18
can use an aggregator which has all the
- 8:21
important tools to make your agent super
- 8:24
powerful and that's why we built this
- 8:28
marketplace and all you need is a skill
- 8:31
file installed in your agent. You can
- 8:33
give your cloud code this skill file and
- 8:36
everything else will be done for you. So
- 8:39
I'm going to show you an experiment.
- 8:41
We'll have uh this specific terminal
- 8:44
with the amperson skill file and we'll
- 8:47
have cloud code cloud co-working without
- 8:51
the skill file and you'll see the
- 8:54
difference is immense already. The
- 8:56
reason is that most important MCP
- 8:59
servers are going to be paid and you'll
- 9:01
not put in your credit card to all these
- 9:03
MCP servers. Rather what you'll do is
- 9:06
use you'll use the agentic commerce tool
- 9:08
or a platform or a wallet or a credit
- 9:10
card to make that happen. And that's
- 9:12
what what we enable. So let's just go on
- 9:16
the terminal and install the ampus and
- 9:19
scale file in one set. This is our
- 9:21
website by the way where you can go. You
- 9:24
copy the prompt and just like put in
- 9:26
here. I already have it so I'm not going
- 9:28
to uh sort of maybe it's fine. Uh
- 9:32
install the skill file. And here I'm on
- 9:35
the cloud coork, right? It does not have
- 9:38
the skill file. Fair and square. This
- 9:41
has the skill file. Now what I'll do is
- 9:43
I'll tell them find the email
- 9:45
information of the head of crypto and
- 9:47
blockchain at Mastercard. All right. And
- 9:49
I'll put in the same prompt. Uh I'll put
- 9:53
in the same prompt for cloud cowork.
- 9:56
Remember the only difference is this
- 9:59
specific terminal of mine has the skill
- 10:03
file which has paid MCP tools and this
- 10:06
one does not. And you'll see that it is
- 10:09
not able to like specifically find out,
- 10:11
hey, we're not able to give you exactly
- 10:13
the email, but this is how the email
- 10:15
format is for our master card. And you
- 10:18
can go ahead and find that out. But when
- 10:20
I go to my terminal, it is already be
- 10:22
able to it will already be able to give
- 10:24
me the email specifically the Twitter
- 10:27
and what where is he based and
- 10:29
everything and beyond. This is just one
- 10:32
example of telling you that agents are
- 10:34
getting powerful through MCP. But these
- 10:37
MCPs are not public services. They're
- 10:40
going to be charged and you will not
- 10:42
know that you're interacting with MCPS
- 10:43
or installing it or going on their
- 10:45
websites and getting the credit card.
- 10:47
Rather, you'll just have a scale file
- 10:49
which is a aggregator which can take
- 10:51
care of your payments. in the
- 10:54
background. What happened was if you go
- 10:56
over here, you already can see that we
- 10:59
did a transaction so that we could
- 11:02
enable this surge for you because this
- 11:04
is a paid endpoint that we had to
- 11:06
specifically pay for to get what you
- 11:09
specifically needed. So when we go to
- 11:11
transactions, you should be able to find
- 11:13
that we did a small transaction so that
- 11:16
you would specifically get that specific
- 11:19
information.
- 11:21
uh 30 days on the
- 11:24
maybe we skip to the next demo for now
- 11:27
as you can see this spending happened.
- 11:30
Let's skip to the next demo. I wanted to
- 11:32
show you one more demo. In this what
- 11:34
I've done is let's say I'm not a good
- 11:38
kid which generally I am and I want to
- 11:40
buy a father's day gift for my dad and I
- 11:44
can also make that happen directly via
- 11:46
the terminal. Shopify introduced UCP.
- 11:50
Amazon might be coming up with its own
- 11:52
thing, but what I'll do is I'll give it
- 11:54
a specific command using Shopify UCP.
- 11:57
Buy my father a Father's Day gift. Keep
- 12:00
the gift less than $10. Let's see how
- 12:03
this specific thing rolls.
- 12:06
What uh will happen in this specific
- 12:08
terminal case is that it will already be
- 12:11
able to f locate certain shops online
- 12:16
and find out what things can be given
- 12:19
for father's day gift list them for me
- 12:22
and be able to buy that directly via
- 12:25
ampend wallet that we have created. your
- 12:28
agent is as powerful as the paid MCP
- 12:31
tools that you're connected to it and if
- 12:34
you've given it a payment trail.
- 12:38
So currently it's finding that out for
- 12:40
us.
- 12:43
Okay.
- 12:54
See, this was an authorized transaction
- 12:56
it did for finding me the email of that
- 12:59
specific person at Mastercard, right?
- 13:02
And these are all paid services or I
- 13:04
would have to go on Xi and sort of put
- 13:07
in my email card and get that. So, never
- 13:10
leave your terminal. Just have a payment
- 13:12
gateway and paid MCP tools and make your
- 13:16
agents super super compatible and faster
- 13:19
and give them more uh power.
- 13:24
All right, it's currently finding some
- 13:27
stuff for me. Let's see if it's able to
- 13:29
come up with some recommendations that I
- 13:31
can use and I can hear itself do a
- 13:35
aentic checkout so I can buy something
- 13:37
for my dad for Father's Day.
- 13:42
What's good about this specific thing is
- 13:45
that again and again I don't have to put
- 13:46
in my name, my address, my phone number,
- 13:50
anything. The agent already has the
- 13:53
memory where it knows what do I like,
- 13:56
what do I not like, and it will just
- 13:58
give me specific things that I might
- 14:00
want to buy for him. So, it already
- 14:04
like, you know, total $9. This is what
- 14:07
it is. Confirming the order and it
- 14:09
already placed the bet and it already
- 14:11
took $11 for that
- 14:16
order complete. And here is your
- 14:18
receipt. and my dad gets his $10 key
- 14:23
directly via the agent. So this is just
- 14:27
starting of what we call will be the
- 14:29
future of agent e-iccommerce. It's not
- 14:32
just buying gifts for your uh parents
- 14:34
but rather it's much bigger. MCPs are
- 14:38
becoming the normal norms of how your
- 14:40
agents become super powerful and you
- 14:44
might have already seen that Cloudflare
- 14:47
is opening its gateway through X42 and
- 14:50
agentic payments. If you go on a website
- 14:53
and the agent is crawling that website
- 14:56
then ads are irrelevant. How do people
- 14:58
get paid?
- 15:00
It's via agentic payments where a bot
- 15:03
comes through Cloudflare, pays a
- 15:05
microtransaction and gets all the
- 15:08
information that's needed. So to make
- 15:11
your agent super powerful, you need paid
- 15:14
tools. We are in the era where most MCP
- 15:17
tools are free. That's not going to be
- 15:19
the case in the future. they're going to
- 15:21
get paid and it will be it what your
- 15:24
agent would need is good MCPS or an API
- 15:28
which has an integration of MCPS and a
- 15:31
wallet and this is what I'm trying to
- 15:34
show you.
- 15:35
So the specific bet has already been
- 15:38
placed. I'm going to try to show you the
- 15:40
transaction over here that was done and
- 15:44
it's already settled and I might have
- 15:46
gotten an email where Shopify was able
- 15:50
to buy my dad a gift. Let's see if I
- 15:54
open it and show it to you because it
- 15:56
Yeah, it's okay. You guys are friends.
- 16:00
See over here the order has been placed
- 16:02
and I can already it's already getting
- 16:05
tracked all via the agent terminal. I
- 16:08
didn't have to even skip. Let's go to
- 16:11
the last part which is all of this will
- 16:14
be big if and only if like Rodrigo says
- 16:18
there is compliance. Merchants will not
- 16:20
take payments if they think this order
- 16:23
is being placed by North Korean wallet.
- 16:26
And for that you need the compliance
- 16:28
layer to be fitting in as well. The
- 16:30
seller and the buyer side both need to
- 16:32
have that. And I've created this
- 16:34
specific uh simulation for you in which
- 16:39
we have a good claw that you can let me
- 16:41
just close this right now. So now let's
- 16:44
go to the third one which is compliant
- 16:47
transactions
- 16:49
right for the world and Amazon to accept
- 16:51
agentic payments there needs to be
- 16:53
compliance involved to make sure that
- 16:56
the payment that's been done is not
- 16:57
malicious. So we have a good claw that
- 17:00
I'll spinning up that I'll be spinning
- 17:02
up over here and we have a bad claw. The
- 17:05
thing about bad claw is this is again a
- 17:07
simulation but this is a sanctioned
- 17:10
wallet address that means it has either
- 17:13
interacted with North Korean entities or
- 17:15
we were able to simulate it in a way
- 17:17
that it is flagged right so no amount of
- 17:20
transaction should be able to be done
- 17:22
because it is out of the swift scope of
- 17:24
policies.
- 17:26
So if we go over here uh in this
- 17:29
specific thing and I disable screening
- 17:31
and save it,
- 17:33
my good claw and my B bad claw both
- 17:37
should be able to do transactions.
- 17:42
Just to give you a little bit of
- 17:43
periphery, this is the seller that is
- 17:46
accepting payments. We have a small
- 17:48
service of scraping websites and it
- 17:51
needs to pay 0.1 cent to be able to take
- 17:54
that scraping information. Right now
- 17:57
because we don't have regulations both
- 18:00
these transactions are going through and
- 18:02
you can see it's getting authorized over
- 18:04
here. Right now what I'll do is using
- 18:08
compliance I will enable the specific
- 18:11
feature that we have built with TRM
- 18:13
which scans the wallet and make sure
- 18:16
that all the transactions are compliant
- 18:18
and what it will do is that up till now
- 18:21
everything has been working for good
- 18:23
claw and bad claw but things will stop
- 18:26
working for bad claw because using
- 18:29
compliance we are able to scan that and
- 18:31
we are able to give you see over here
- 18:33
the your your transactions are getting
- 18:35
blocked or rejected.
- 18:38
And I can also show you over here that
- 18:40
rejected and denied. And the reason
- 18:42
behind the denying is because you're in
- 18:45
the block listed wallet addresses.
- 18:48
All to tell you that agentic commerce is
- 18:51
becoming real. Agents need commerce more
- 18:55
than humans need commerce. But it will
- 18:59
not be the same. You will not go through
- 19:02
payment guardrails of Stripe or any
- 19:06
other of these checkout flows, but
- 19:08
agents will have their own proprietary
- 19:10
firms either through wallets or through
- 19:12
their own credit cards. Agents would
- 19:15
need to be superpowered. MCPs will get
- 19:18
paid and more and more paid MCPs will
- 19:21
come to reality to make your agent
- 19:23
successful.
- 19:25
That will only happen and only be
- 19:28
successful in UX terms and more if
- 19:32
you're able to empower your wallet with
- 19:34
paid MCPs and a wallet infrastructure.
- 19:38
If you want to know more about it, come
- 19:41
to Ampend. We'll be here outside
- 19:44
chatting if you have any questions.
- 19:46
Thank you.
- 20:01
>> [music]