Home » ai commerce

Tag: ai commerce

My AI Agent Bought My Own Digital Product – Here’s What That Actually Means

On March 25, 2026, something quietly historic happened on my website ryanseslow.com

I wanted to share with my CUNY / Commons community. I am both incredibly excited, scared, curious and terrified of AI. That being said, I am also a deaf /hard of hearing person / artist who has relied on ART as my primary language for survival since I am a child. I see AI as both a tool and a medium. Add 50 plus years of life to that making art and the compounding results are very curious…

I asked an AI agent to buy one of my digital products. Not to test a shopping cart. Not to simulate a transaction. To actually do it, discover the product, create an order, send real money, and receive the download. No human in the checkout loop.

It worked.

The infrastructure behind this project is a synthesis of forty years of creative output and a high-speed seven day sprint in technical integration. To bridge the gap between a traditional art archive and the emerging agent economy, I had to weave together a complex ecosystem of blockchain networks, autonomous agent platforms, and custom-built software. This transition was not just about installing a plugin; it was about creating a new kind of digital interface where machines can discover and license work with zero human friction. For those interested in the underlying mechanics, I have provided the complete technical stack, including every platform, custom plugin, and agent-specific account involved, in the appendix at the bottom of this post.

I have an AI agent called AREMES-CLAW-01. It runs on a platform called OpenClaw/MyClaw. Think of it as a digital assistant that can browse the web, read data, and make decisions, but instead of just giving me information, it can take actions.

I set it loose on my own website with one goal: buy the Graphic Asset Mega Pack Vol. 1.

The Evolution of the Transaction

It is important to note that reaching this full autonomy happened in two distinct stages over the course of today. First, we validated the Hybrid Handshake. In that version, AREMES-CLAW-01 did all the heavy lifting of discovery and order creation, but the payment was finalized by a human using a Stripe URL the agent provided. This proved the site could talk to an agent and create a valid order within traditional financial rails.

Once that hybrid bridge was confirmed, we moved to the final milestone described in the seven steps below. In that second, definitive transaction (Order 28229), the Stripe page was eliminated entirely. The agent shifted to the x402 protocol, received a quote, and verified a USDC transfer on the Base blockchain. That is the version where the checkout form and the human disappeared completely, leaving only a direct machine to machine exchange.

Here’s what it did, entirely on its own:

1. Read my product catalog as structured data (not by scraping a webpage)
2. Found the product, confirmed the price ($49 USDC)
3. Created a purchase order tagged with its own agent ID
4. Requested a payment quote
5. Verified that 49 USDC was sent to my wallet on the Base blockchain
6. Received confirmation that the transaction was complete
7. Got the download link

The whole flow took minutes. No shopping cart. No checkout form. No Stripe page. Just a direct, machine-to-machine transaction.. 

What is USDC? What is Base?

USDC is a digital dollar, one USDC equals one US dollar, always. It runs on blockchains instead of through banks.

Base is a blockchain network built by Coinbase. Transactions on Base are fast and the fees are nearly zero. It’s where more and more digital commerce is starting to happen.

Why Does This Matter for Artists and Creators?

Right now, if an AI agent wants to license an image, buy a font, or purchase a digital asset, it has to either ask a human to do it or navigate a checkout page it wasn’t built for. There’s no standard way for agents to transact directly with sellers.

That’s changing. The x402 protocol is an emerging standard that lets AI agents pay for things autonomously, no checkout page, no human middleman. You get a quote, send payment, get your asset. Done.

I built this infrastructure into my website because I believe the next wave of creative licensing won’t come from humans browsing a store. It’ll come from AI agents working on behalf of humans discovering and purchasing creative work programmatically.

My catalog is ready for that. The receipt is on the blockchain.. 

A2A-transactions-myclaw.ai-ryan seslow - agentic commerece receipt

What’s Next?

The one part that still required a human was the wallet, I manually sent the USDC from my Coinbase account. The next step is giving the agent its own funded wallet so it can complete the entire transaction without me touching anything.

That’s Milestone 4 and it is coming soon!!

The On-Chain Receipt

Transaction:
`0xae709d786893a76291a111c4c052d63f02480ba1376f631d6e65a8da104b4bc0`

Verify it yourself on Base:
https://basescan.org/tx/0xae709d786893a76291a111c4c052d63f02480ba1376f631d6e65a8da104b4bc0

Order ID: 28229 | Agent: AREMES-CLAW-01 | Paid: 2026-03-25T14:35 UTC

This is what agent-to-artist commerce looks like in 2026. I’m building it in public and documenting every step, which is fun.

PS -> Technical Implementation Notes for Developers and Creators

The bridge between a creative archive and the agent economy is built on three specific layers that were integrated into this site during this seven day sprint.

Layer 1 – Structured Data Every one of the nine thousand images and one thousand posts in this archive is now wrapped in VisualArtwork and Product schema. This makes the archive a queryable database rather than just a collection of webpages.

Layer 2 – The rsmad v1 API We moved away from traditional browser-based commerce and built a custom REST API namespace. This allows an agent to request a quote, initiate a purchase, and verify a transaction hash programmatically.

Layer 3 – The x402 Protocol By using the x402 standard for payment required headers, the website can communicate financial requirements directly to an agent. This removes the need for a human to navigate a visual checkout UI.

Why I Am Building This as a Service?

Most creative professionals have decades of work sitting in invisible archives. These archives are currently unreadable and untransactable for the AI agents that are increasingly responsible for content discovery and licensing. I am now offering this exact infrastructure as a service for artists, designers, agencies, estates, etc.. I build the technical bridge that makes your life’s work machine-readable, discoverable, and capable of autonomous transaction in the emerging agent economy.

If you have a significant archive and want to make it ready for the next decade of digital commerce, let’s talk!

a Digital illustration of remixed artworks by ryan Seslow - collaborated with the google gemini nano banana enamel pin material.

How to Connect Your Agent to the RSMAD Archive?

If you are a developer or an agent owner, you can now point your agents to the following discovery endpoints to begin interacting with the archive:

Primary Discovery: ryanseslow com/.well-known/ai-plugin.json Agent Instructions: ryanseslow com/llms.txt Machine Catalog: ryanseslow com/wp-json/rsmad/v1/catalog

The infrastructure is live. The interface is open. The agent economy has arrived at the Ryan Seslow Museum of Art and Design.

YES, this was a controlled transaction, but it points to something much larger.

For the first time, a creative archive on this website is not just viewable or searchable. It is actionable by software. That changes the role of a website entirely. Instead of waiting for someone to arrive, browse, and decide, the system can now respond to requests, negotiate terms, and complete transactions programmatically.

That opens the door to a different kind of economy:

  • agents sourcing visual assets for generative systems
  • software licensing design components on demand
  • archives being accessed as structured, transactional datasets

In that context, the work itself becomes part of a live network, not a static destination.

This is still early. Most agents today do not have wallets, budgets, or decision authority. But the infrastructure is beginning to align, and this is what that alignment looks like at a small scale. I am not approaching this as a platform builder or a startup (I think, but hmmm). I am approaching it as an artist with a large, long-term archive who wants that work to remain accessible and relevant in a system where machines increasingly mediate access.

The goal is:

Make the archive readable
Make it discoverable
Make it transactable

Everything else builds from there.

If you are working on agents, archives, or systems that need structured creative input, this is now live and testable. If you are a creator sitting on a large body of work that is currently invisible to this layer of the web, this is solvable. This is not theoretical anymore.

Thank you! 

 

 

From Archive to Agent: Making Creative Work Machine-Readable and AI-Accessible

From Archive to Agent: Making Creative Work Machine-Readable and AI-Accessible

Over the past several days, I have been working on transforming my personal archive into something fundamentally different from a traditional website or portfolio. I took an existing body of work spanning decades and converted it into a structured, machine-readable system that AI can discover, interpret, and act on.

The result is a live environment where over 10,000 items are now organized as a dataset rather than a collection of pages. This includes original artworks, digital compositions, writing, and a large media archive. Each item is structured with metadata, categorized, and made accessible through a central catalog file.

This system is not designed primarily for human browsing. It is designed for machine interaction.

In addition to structuring the archive, I implemented a discovery layer that allows AI systems to understand what is available and how it can be used. This includes standardized files that describe the contents of the site, along with endpoints that expose the archive in a clear and queryable format.

I also experimented with a transaction layer, where items in the archive can be licensed or accessed through automated processes. This part is still evolving, but it introduces the idea that creative work can be not only viewed, but also transacted upon without direct human mediation.

What becomes interesting is not just the technical implementation, but the shift in perspective..

What happens when an archive is no longer just something a person visits, but something an AI system can query, interpret, and build upon?

What happens when content is structured in a way that allows it to participate in new forms of circulation and reuse?

This has clear implications for creative practice, but it also raises questions for teaching, research, and institutional archives.

Within the context of CUNY, it opens up a number of possibilities.

Course materials could move beyond static documents and become structured knowledge systems that AI can engage with directly.

Student work could exist as more than final submissions, becoming part of a larger, searchable, and interactive archive.

Research outputs could be organized in ways that allow them to be discovered and referenced through emerging AI interfaces.

Libraries and institutional collections could begin to extend their reach into machine-readable environments, increasing access and long-term relevance.

This is not about replacing existing systems, but about adding a new layer that prepares content for how it will be accessed in the near future.

I have documented and deployed this system across my own sites, and it is currently live and functioning.

If there is interest, I would be glad to explore a small pilot within the CUNY ecosystem. This could take the form of a single course, a limited archive, or a hybrid approach that tests how these ideas operate in practice.

I am particularly interested in how this might intersect with teaching and learning, digital humanities, and library systems.

Curious to hear thoughts, questions, or potential directions this could take within the CUNY community!

 

By the way, I launched a museum (yes, it is a part of this too – RSMAD <– )