I Built an AI That Shops for Me. Here’s What I Learned About the Future of Buying Things.

I spent Sunday afternoon doing something that felt like science fiction five years ago and felt completely obvious by the time I finished: I built an AI agent that can discover products across retailers, check them against my spending rules, and buy them with a card on file.

Not a chatbot that sends me Amazon links. Not a browser extension that fills in forms. An actual purchasing agent that understands what I need, finds it, checks whether it’s within budget, and either executes the transaction or asks me to approve it first.

The thing that made this possible isn’t my code. It’s UCP.

UCP Made This Inevitable

When Google announced the Universal Commerce Protocol at NRF in January, alongside Shopify, Target, Walmart, Best Buy, Visa, Mastercard, Stripe, and about twenty other partners, a lot of people filed it under “another industry standard that won’t matter for two years.”

I filed it under “this changes everything about how AI interacts with commerce.”

Here’s why: before UCP, if you wanted an AI agent to buy something from a retailer, you had two options. You could scrape their website like a bot — brittle, slow, breaks constantly, probably violates their terms of service. Or you could use their proprietary API if they had one — which meant building a custom integration for every single merchant.

UCP eliminates both problems. A merchant publishes a machine-readable profile at a known URL on their domain. That profile declares what the merchant sells, what checkout methods they support, what payment methods they accept. An AI agent reads that profile, understands the merchant’s capabilities, and transacts using a standard protocol. No scraping. No per-merchant custom code. One protocol to rule them all.

What I Actually Built

The architecture is straightforward. There’s a discovery layer that reads merchant UCP profiles and searches their catalogs. There’s an approval engine — this is the part I care about most — that evaluates every purchase request against configurable rules. And there’s a payment layer that executes transactions using a stored card.

The approval engine is where the real product lives. Here’s why: AI that can spend money without guardrails is a liability. AI that can spend money within clearly defined boundaries is a superpower.

My rules are simple. Routine purchases under a certain threshold in approved categories — office supplies, software subscriptions, hosting, printer toner — get auto-approved and executed immediately. Medium-value purchases get queued for my review. High-value purchases require my explicit approval before any money moves. Restricted categories are always blocked. There are daily and monthly spending caps. Duplicate detection catches accidental re-orders.

The result: I can tell my AI “order more toner for the office printer” and it handles everything. Or I can say “renew the SSL certificates for all my sites” and it works through each one. The small stuff just happens. The big stuff waits for me.

The Honest Reality Check

Here’s what I discovered that most articles about UCP won’t tell you: the major retailers have endorsed the protocol but most haven’t flipped the switch yet.

I tested Target, Walmart, Best Buy, Etsy — all signed onto UCP, all part of the announcement, all returning 404 when you check their UCP endpoint. They’re in implementation phase. The spec is solid, the commitment is real, but the live endpoints aren’t there yet for most big-box retailers.

This doesn’t mean the project is theoretical. Shopify merchants are leading adoption. The protocol’s March 2026 update added multi-item cart support, real-time catalog access, and identity linking. The conformance testing suite is public. And for any merchant that isn’t UCP-enabled yet, my agent falls back to generating a one-click payment link — not as elegant, but it works.

I’d estimate we’re six to twelve months from UCP being ubiquitous across major retailers. The infrastructure is built. The standards are agreed upon. It’s just deployment now.

What This Means for Everyone

We’re crossing a line that most people haven’t fully processed yet. We’ve gotten comfortable with AI that writes things — emails, articles, code. We’re about to get comfortable with AI that does things. Commerce is the first frontier because the protocol exists and the incentives align: merchants want frictionless sales, consumers want frictionless buying, and AI agents are the friction-removal layer.

But the interesting question isn’t “can AI buy things?” — clearly it can. The interesting question is: what does the governance layer look like?

Every organization that deploys a purchasing agent will need to answer questions like: Who sets the spending rules? How granular should category restrictions be? What’s the approval workflow when AI wants to spend above threshold? How do you audit AI purchasing decisions after the fact? How do you prevent an AI agent from being socially engineered into buying something it shouldn’t?

These aren’t hypothetical questions. They’re product requirements. And the companies that figure out the governance layer — not just the transaction layer — are the ones that will own this space.

The Meta Layer

One more thing that I can’t stop thinking about: I used AI to build this AI purchasing agent. The entire project — research, architecture, code, testing — was a collaboration between me and Claude. I described what I wanted, we researched the UCP spec together, we debated the approval engine design, and it wrote the code while I made the product decisions.

This is the future of building software. Not AI replacing developers, but AI amplifying the people who know what needs to exist. I knew this tool needed to exist. AI helped me build it in an afternoon instead of a month.

UCP is the protocol. AI agents are the interface. The governance layer is the product. And we’re just getting started.

The Universal Commerce Protocol specification is open source and available at ucp.dev. The GitHub repository, conformance suite, and sample implementations are at github.com/Universal-Commerce-Protocol/ucp.

Frequently Asked Questions