Build for the Agentic Economy With USDC on Arc | Blessing Adesiji at ETHOnline 2026

It's very nice to be here . Thank you all. Um, my name is Blessing, and I work in the developer relations team at Seku. I'm focusing on Arc and our agent payment product. So today I'm going to talk about creating an agent economy on Arc.

The goal of this workshop is to help you prepare for the hackathon, explaining in detail why Arc was created to pay agents. Also show some examples. I'll walk you through one of our core products for agents, called the Seku Agent Stack called the Seku Agent Stack . I'll just briefly talk about how the product works and what it offers. I'll then show you an example of what's possible on the testnet, and also give you an idea of ​​where you can bring this product, considering that most of us here will be deploying it for the mainnet, which will also be announced this month.

So you can understand everything you need to start developing now, and deploy when you're ready. So again, we'll look at the theoretical understanding of why Arc is designed to pay agents. I'll show you a code example, a sample application - a repository that we've prepared to give you an understanding of how this works, to see it in real-world use, and then give you an idea of ​​the Circle agent stack, and give you time for questions. So, if you have any questions you have any questions , I can address them as we prepare for this hackathon. So, to start with, why is Arc built for agency payments, or more specifically, how is Arc positioned for agency payments, right?

To make it easy for you to create payment scenarios for AI agents. You can be a trading application trading application , a data mining application. This can be anything that requires an agent to be present in the workflow to set up a payment set up a payment , perform a statement , perform a statement , pay for data, pay for services, or to perform some work. I'm sure a few of us here on Discord are familiar with the X402 protocol, which is an HTTP protocol that requires the requester to encounter a payment and reconciliation gateway when sending a request. And until they complete these payment reconciliations, they won't be able to get the data back.

Right? So, the agent payments use case leverages X forward 2 and a Circle product called Circle Gateway to make it very easy to build AI agent use cases . Why is Arc designed for this? Why him? How is it easier to create it with Arc?

Uh, let's imagine a trading app. Right? Let's say I'm building a trading app. And for this trading application, I need workflows that I would like to create. I want the application to receive some data, and with that data I want to be able to make decisions, right make decisions, right ?

Uh, to carry out decisions, to respond to decisions. And now, these solutions, uh, these solutions, I want to be able to use this solution to perform certain actions. Uh, certain actions. So this workflow example is a typical workflow for, uh, a commerce application. Now, it would make sense to me to do this with an AI agent, because AI agents can automate all of these processes, right?

Very fast, faster than any human, right? They can get the data, they can make decisions based on the available data, and then they can take action. Uh, actually, we can even add something like a check here. I 'm going to put an end to it , okay? And I'll say, "Okay, some conditions."

There are some conditions. There are some conditions that are necessary to perform certain actions. So, this is an example of a trading application trading application . Now, for all these, for all these to happen, for all these to happen, right? They have to happen very quickly, right?

An AI engine needs to access data quickly, make decisions quickly, and then take action within a second, right? Let's say this is a live trading app. For this you need access to a fast network, right? On the blockchain. A perfect example is Arc.

Why? Because Arc payments are processed in less than a second. For example second. For example , you are already executing your deal and you need to perform all these workflows very easily. Up does it in less than a second.

Another reason Up is built for agency payments is that network fees are settled in USDC. So Up has USDC as its own gas fee. If I'm building this trading app, this agent trading app, I don't want my user or the app user or the workflow user to have to look for another similar token before executing a transaction, before executing this particular action. Therefore, it would make sense to use USDC, which is native to Up, to complete this transaction. So it just becomes the logic of deducting transaction costs transaction costs , whereas these workflows actually get a certain amount, right?

And it's perfect for developers because you can create payment for services in real time. Uh, USDC accounting is much simpler, and then you get faster request cycles because it all happens in less than a second, and it happens on Arc, where the user doesn't have to go through the extra step of looking up any other natural gas payment before natural gas before doing the trade-off before making the payment, right? So, all of this is explained with this specific example specific example , and this is how Arc is positioned for agency payments. So, you want your agent to be able to pay your agent to be able to pay while they are working, and this should continue without interrupting the flow of users. This is kind of like the ideal agent payment experience, and I'll show you as I walk you through an example of nanopayment in action in the nanopayment workflow in action, and I'll also explain nanopayments, right?

So, this is what you need, right ? The agent must have access to data or APIs, perform inference, and also pay for services. So, this is how the agent workflow is structured. Arc is the payment infrastructure for this, as JST is the native gas fee on Arc. Uh, it takes about 0.

48 seconds to execute a specific transaction, a sample transaction, and Arc is a deterministic final payment on the order of a second, meaning the payment is made on the order of a second. There is no other separate volatile gas token that a user would likely need to stop a certain action, search for that gas token before continuing the process. Arc continuing the process. Arc is a great stablecoin, and it gives developers what they need to build fast apps built for the agent economy agent economy , where they can make payments for services in real time and have access to simple USDC accounting. They also have access to faster request cycles and can also receive receipts receive receipts , logs, which provides greater auditability, transparency, and actual knowledge of what your agent paid for while it was all happening.

Right? And this simplifies payment. So, I'll take a break, check the chat, see if there are any questions directly in the chat. Yes, yes . So, I see one question: “For an agent wallet on the testnet app, does the CLI-managed agent wallet use a transfer account using the Circle agent stack at an agent- based cost, or do you expect the project to use a specific starter kit, a specific starter kit, or any API flow or any API flow ?

” That's great, isn't it? So I like this question because there are multiple ways to build with a Circle agent to build with a Circle agent. You can use the CLI, create a wrapper around the CLI, and to simplify all of this, we have something called a starter kit, and it was all linked on the ETH Global Hackathon page. You will see all the resources there. So you can use the CLI, right?

If it's easier for you, right? Or you can use a starter kit to simply show a specific agent workflow. It could be a trading app, it could be the first payment, and since you're building on Arc Testnet, right? Arc Testnet does not yet have access to the trading platform, as most of the XRO marketplace services are performed on the mainnet. So mainnet.

So , you would be limited to only certain products in the Circle agent stack because you are building on the Arc testnet. But you can keep that in mind when you're building for the main network, right? So, you can update your workflows when you build for the main network. Right? So, that's what Right?

So, that's what I answered the question, but I'll continue the rest of the presentation and take the second question: "Can Uniswap V2 be deployed on the Arc mainnet?" If so, which pool will have available liquidity? "So, that's the question, right? I'll take that question. I'll take it into consideration and then I'll get your email from the organizers and I'll give you a very detailed answer because I need to confirm need to confirm before I can give you an answer.

But I'll confirm it with the team and then I'll give you a detailed answer later. Yes, thank you. Yes, I see Yes, thank you. Yes, I see , that's great. Also, thank you for translating the Circle CI wallet output into JSON.

What exactly is the channel we should rely on for the transaction hash, and does the CLI expect an on- chain confirmation or just a send? If you can give me a specific workflow, I can go over it at the end of the session. Just because there's an example that I need to show you by the end of the workshop. So if you can give me an example of something that you're trying to build trying to build , that will help me answer the question in context. Okay, so let's move on.

Um. So for those of us who may not be familiar with everything I just talked about, "That's why I want to talk about Agent Circle." stack. So, for those of us who may not be familiar with the question you just asked in the chat, we have the Circle Agent Stack , and I want you to think of the Circle Agent Stack as a set of developer products built to make it easier for you to create scenarios using agent synchronization. So, in the Circle agent stack, we have several products that are part of the agent stack.

We have an agent wallet, we have an agent marketplace, we have nanopayment, we have the Circle command line interface and Circle skills. Yes, the agent wallet provides agents with funds and policies. So, imagine an agent wallet as your agent who has access to USDC, stores USDC in real time to be able to trade to trade , to make transactions, right? And they do all this with certain equipment, in certain agent equipment. It could be cloud code could be cloud code , it could be COSO, it could be a wrapper around a command line interface, right?

Because the command line interface powers the agent loop, it gives you a way to actually interact with the agent loop. So, the market provides services that you can discover for yourself. So, in the agent marketplace, if you go to the agent's site, you'll go to...In the agent marketplace, you'll be able to see all the services that you can interact with. Since this is an actual transaction on the mainnet and Arc is currently on the testnet, you will not be able to access some , if not all, services until we move to the mainnet with Arc.

So remember that all your Arc agent usage workflows are limited to the testnet for now before we move to the mainnet. So mainnet. So , you can build maybe a trading application based on the Circle CLI with an agent wallet that exposes this particular logic, this particular workflow, and you can also combine multiple use cases where you have an agent that maybe gets data maybe gets data , and you use it to execute trades on Arc or maybe settle all your payments on Arc. This is an example of something you can create too. So, going back to my chart, this is an agent's market.

The agent marketplace provides services that you can discover, that your agents can discover, and that they can interact with. Now nanopayments. Nanopayments help you make small toll calls, right? Imagine what you need...Imagine an agent who the agent has to pay for the conclusion, right?

This can be in cents or in thousands of cents. Payment in a tiny fraction, for example, 0.001 USDC. Doing this on a large scale on a traditional blockchain would be uneconomical. But the reason you can do this on Arc is because of Circle's nanopayments, which are an infrastructure that allows you to pay for tiny transactions for almost free.

And the reason it's almost free is because all these tiny transactions, all these tiny...Imagine they're multiple tiny transactions. I just came up with this tiny diagram, right? So, imagine we have a few tiny transactions. But all these tiny transactions are not carried out on the blockchain.

They are carried out outside the blockchain, and eventually they are all combined into a single transaction, which is now settled on the blockchain. So you're actually paying for everything that happens for almost free because when all these tiny transactions happen, they don't happen on the blockchain. They take place outside the blockchain. But later they are combined later they are combined . And since you can build it on Arc, right?

Because it allows you to test it on a test network. You can create a sample project, or rather an Arc Account project, where you show how nanopayments work in real time, where an AI agent can pay for data. They can pay for the API. They may charge for opinions or various services. But they do it, they do it in tiny USDC.

0.001 USDC, 0.003 USDC. And all of this is combined and regulated in much more detail later on the blockchain. So, all I just explained is the Circle Agent Stack explained is the Circle Agent Stack , in a nutshell.

So you have the agent wallet you have the agent wallet , you have the agent marketplace, you have the agent nanopayments, and you have the Circle CLI and Circle Skills. Each of these elements, or these primitives, come together to create the Circle Agent Stack. And building it on Arc is much easier when you use the Circle Agent Stack. Isn't that right? Because you have access to all the tools you need.

You have access to the wallet, you have access to the marketplace, nanopayments, CLI, skills, everything you need to bring these actions to life in a group of agents life in a group of agents . The agent group could be your cloud code or your code at the edge, or it could be a wrapper, a production wrapper that you build around all of the Circle CLI and the Circle warps. And that's exactly what the starter kit is designed for. So, you can think of the starter kit as a wrapper around the CLI so you can build production-grade applications. What is especially important for this hackathon.

So I'll pause, see if this all makes sense, and then check the chat for questions. Good. Yeah, I see, I see, they say "oh, oh, great say "oh, oh, great ." Thank you. Also regarding Circle wallet transfer.

Okay, that was different. That was a different question here. For example, an agent schedules a payment, such as USDC, calling an external risk decision API. Uh risk decision API. Uh , first it calls the external API for risk decision, then, only if the local policy says " policy says " continue", it calls the wallet transfer.

Okay, that makes sense. Uh, connect it in a chain. testnet outputs JSON from the CLI in test mode. We print the command in real time. We want to pass the result to the CLI to pass the result to the CLI , show the hash and transaction status, and avoid double spending if something runs out.

What JSON feed or any state values should we rely on for this? Okay, no, that makes sense. So, I will note that as well and then reproduce it locally on my end and then get back to you with a response. So let me just take a screenshot of this. Take a screenshot of this.

So that I can also test this in my own agent, uh, honestly, in the testnet, and then I'll give you a detailed answer. I will also mention this other question. Good. Okay, great. Thank you.

Um, I am, and if you can specify in the chat can specify in the chat , this is your specific hackathon application, right? Did you just indicate the answer to this in the chat? Okay, yes. Okay, great. Yes, I will, and I'm also on Discord.

So if you can help me, I think that would be much better. If you can help me leave this question in Discord, tag me, my nickname is Blessing Circle, okay? So tag me if I have, I can answer in much more detail. Also for Maxim, please, if you can tag me with the full question in Discord, I will provide answers to them . Thank you very much .

Thank you very much . So I think I have about 10 minutes left before the end of the seminar. Let me show you an example to make all this a little clearer. If this is your first time dealing with agent stuff, you'll be faced with creating an agent application on Arc. If all of this is still very new to you and you're trying to put all of this knowledge together to be able to create for a hackathon, I'll show you an example right here you an example right here .

So, I have this diagram to explain how it works, but I don't think I have time to actually go through each of these workflows. So I'll just go straight to...the code to the repository. Uh, and if you want to access the repository I'm working on, I'll copy the link and leave it in the chat. Okay, so I'll leave you in the chat.

Perfectly. So, this is a sample program. Yes, oh, thank you. Thank you. I'm looking forward to it.

So, this is a sample application we created to demonstrate gas-free USDC payment using second and nano payment. Yes, and this repository has a LangChain agent that acts as a buyer, autonomously paying for paid resources , yes, while the Next.js web application acts as a seller, exposing the X world to a secure endpoint and providing the seller with a merchant dashboard to monitor payments and withdraw earnings. So this is a real-life example, right? Seller and buyer.

Now, seller, you can think of seller as a web seller as a web application, right? This is a seller. Now, the buyer, we have a LangChain agent who is the buyer. Now the buyer's goal is to try to make a request to a paid resource and be able to and be able to ... to access the paid resource, right?

They need to make a payment. They need to make a payment. So, we have a buyer who is an agent. We have a seller who actually sells access to a paid resource. Now, for the buyer to have access to what the seller is selling, they need to make a tiny payment.

He needs to pay maybe 0.01 USDC or 0.03 USDC. How will they do it? They do this using Circle nano payment in the app.

And Circle nano payment works with Circle Gateway. And it works so that when a buyer makes a payment to a seller, it all happens offline. And after a certain period of time, all transactions, right? All transactions are combined into a single transaction and executed on the network. So, Circle Gateway aggregates many signed off- network authorizations.

So, when a buyer places an order with a seller, they are effectively just signing an authorization signing an authorization . Right? They... . Right?

They... signing the authorization. And on my diagram, that's where I explained it, right? They sign off-chain authorization, off-chain EIP-712 authorization, right? And they move on from the request step.

They receive a 402 response stating that a payment is required. They sign an off-chain transaction authorization and then repeat the request they made here they made here , which was fulfilled in a 402 payment required response. They repeat this with the payment signature in the header, and then verify that the payment is validated and settled using the Circle gateway, which is a fast API which is a fast API intermediary. And then the resource they are looking to access is delivered after that. So, this is how Circle's nanopayment works to make this workflow simple and easier.

Now, I've created this example program so that you can actually test it in a real program where there 's some, uh, user interface, and this is the user interface. By the way, this is the seller's dashboard. So, there is a seller dashboard. There's a merchant dashboard with all of the... endpoint, payment, and amount, right?

And then there is the agent, that is, the seller, right? APIs. So, let me run this. What I'm going to do is, uh, I'm going to finish. One second going to finish.

One second . And then I'll restart the program. So what I'm going to do is, uh, I want to show you, uh, why is it stuck? Yes. Uh, I want to show you how it works in real life, okay?

Run this program. So if you clone this repository and load it like your cloud code and configure it, you will configure the database. We have a superbase. You are setting up a database. You can actually test it.

So, if I'm going to test it, I'm going to test it with a limit of $0.5 . So what I'm doing here is I want the doing here is I want the buyer, i.e. the agent, to make a payment with a spending limit of $0.

5. So he's going to pay for a bunch of things, right? He's going to pay for a bunch of things, and we're going to start to see where he's really starting to understand because it's going to be really fast, and he's going to do it with Tekno Nano payment, which works in the app. Tested. So, he deposited a certain amount of funds into the gateway so that he could work with it.

I do n't know why the payment is failing. You probably need to check the repository. But, let me just... So what I was trying to explain is that when I ran this before the workshop, you could see the agent making a payment for the data, trying to get the dataset, trying to access the computation, trying to do the agent's task, which is the inference task, right? Trying to access a paid quote example.

And all of these transactions are happening in tiny amounts of USDC, tiny amounts of USDC, using the second payment nano. And you can see all of this on the dashboard dashboard , by the way. Where is the dashboard? Yes, it's all on the dashboard dashboard , by the way. So, that's how the agency payment works in Arc, right?

And you'll state the amount of gas bill required for this...almost as insignificant. It's like going without fuel, because if you use, for example, nanopayment, you're actually even paying off- grid. Right? But if you were creating an actual agent payment on the Arc mainnet, you would settle the transaction in USDC, which is the transaction fee.

But it's not even that difficult not even that difficult , because USDC is the native fuel fee on the Arc testnet. So I'll pause again, check the chat for such a question. Hmm, can you please go back to the go back to the flowchart for a screenshot? Okay, yeah, great. Yes, great.

One second. Let me come back to that. Forgot where it was. Yes. Yeah, and if there 's a way I can send this to Discord, I'll actually export the image.

Let me even see if I can add this to the chat. Let me see if I can export the image. Hmm, copy to clipboard. Hmm, I don't think I can paste this into the chats. If not, I'll just paste it into Discord.

Good. Perfectly. Yes, I threw an image for each of you in the chat. Yes. Yes, no, please.

Yes, please please. Yes, please . So, uh, I have 3 more minutes. So I'll use these 3 more minutes to answer the questions. Uh, I think I've covered a lot of things.

Even for this, it would Even for this, it would probably take me about 2 hours to figure out each component, explain the code, open some files, maybe configure it. I'll show you some of these things, but we did it all in literally a couple of minutes. So don't worry if you have any questions. Uh have any questions. Uh , I'll be on Discord.

You can ping me. I can give you an answer, right? And that's how I came up with this diagram, to break it down so you can understand what it means to build a universal payment product on the Arc testnet to start with, and then on the mainnet when you're ready to when you're ready to deploy it. Uh, I'm waiting for...questions.

Yes, thank you, guys Yes, thank you, guys . Thank you for inviting me. Uh, if there are no questions, I think I'll hand the floor over to Nicolas, uh, Pascal. Sorry. Do n't worry.

You're leaving, thank you very much. It was a really, really good, really insightful seminar. Uh, as you mentioned earlier, the Arc/Circle team is available on Discord where you can ask your questions. I think there are a few more that haven't been considered, but Blessing will definitely be involved in this. And so, uh, in general, just one note about the hackathon: don't ask for questions, just ask the questions directly.

This way, the Arc team, as well as the EthGlobal team, will be able to unblock you much, much faster. And yes, thank you very much for the seminar. Thank you all for your time. We are very excited to see what you are going to create for EthOnline. Uh, remember, submissions are due on Sunday at 12:00 PM Eastern Time, so you still have plenty of time.

Be sure to send at least once. Uh, yes. And Again, Blessing, thank you so much for your...Yeah, just a second before you go, there's a question in the chat that I'd like to quickly, uh, answer. Of course.

Right. Yeah, so, uh, it says it's only Arc, the only, uh, it's Agent, I think it says it's only, one second. Uh, will Al be looking for a draft agency fee? No, we are not only looking for an agency payment project. I limited the work, uh, scope of this seminar to the agency payments project.

So, we are looking for a decentralized finance app for online financing , right? We are looking for, uh, people to launch a new project from scratch on the Alch Alch testnet Alch Alch testnet , and also push it to the mainnet it to the mainnet . Uh, and of course, the best agent economy app with the Circle agent stack with the Circle agent stack . So I just thought . So I just thought that, uh, most of us here are probably familiar with building DeFi building DeFi applications.

So, instead of looking at that, let me look at the agency economy, because that's kind of a new niche, right? Or a new request, right? That's why I looked into...All of this at the seminar. So, uh, to say all that, uh to say all that, uh , check out the project prize builder page , right?

On the Ethereum Global website. And we have provided a detailed description of each project and what counts for a valid application. So, there is the best DeFi financial app on the web. There is the best agent economy app with Circle Agent Stack. So, for that you need to use the Circle Agent Stack, and the Circle Agent Stack part is everything I covered in this seminar.

Agent Wallet, Nano Payment, Circle CLI. We understand that you CLI. We understand that you may not be able to create with the marketplace right now because it requires transactions on the mainnet, right? But you can build on the next one, which will be the best DeFi or agent app. You can run an app on a testnet with the intention of publishing to the mainnet, and then run on an app testnet or something similar with the intention of publishing to the mainnet, as I said.

So, that's probably all the reward in detail. You can check the Ethereum Global website again for reference. I hope this answered the question. Believe. Surprisingly.

Thank you very much Surprisingly. Thank you very much .