When Sayer & Stone came to us, the question wasn't about compliance. Their product is lab-grown diamond fine jewelry, made to order, designed with architectural precision. There's no age requirement, no shipping license, no sanctions overhead beyond standard wallet screening. The question was simpler.
Can an AI agent actually buy a pair of earrings?
The endpoint lives at agents.sayerandstone.com. The order shows up in the back office, the jeweler makes the piece, the buyer gets a delivery estimate by email.
What a real jewelry brand cares about
Sayer & Stone is a modern jewelry house. Luxury, Every Day, in their own words. Direct-to-consumer, lab-grown stones, architectural settings designed to be layered and lived in. They aren't a fintech and they aren't a crypto shop. Same calculus as Martin Estate: any rail that settles into their bank account is the right rail.
What they wanted to test was the bull case: is there a new customer type here? An agent picking earrings for someone's anniversary. No human typing the shipping address, no human picking the metal or carat. We built the infrastructure to find out.
The integration
A single endpoint that speaks x402 and MPP and reads from the catalog. The skill manifest at /skill.md covers the SKUs (earrings, bracelets) with variant axes like length, metal, and carat weight, the rails accepted, and a worked example. The agent parses it once and has what it needs to transact.
Compared to Martin Estate, this integration is short. The skill manifest is half the size. There's no gate config, no per-state shipping logic, no age check, no jurisdiction allowlist. The merchant doesn't need any of it. Sayer & Stone ships to US addresses, full stop.
Not every category is wine. Some businesses just want to sell to the new customer.
Payment
Same Checkout orchestrator as Martin Estate. Sayer & Stone advertises every rail they accept (tempo, x402_base on eip155:8453, and stripe) and the agent picks the one it can pay with. Funds clear into the brand's account in USD via Stripe.
Wallets are still screened at settle. The buyer's wallet runs against OFAC's SDN list. Every merchant on our stack inherits this regardless of whether they configure a gate. It's our floor, not their choice.
A real order
Prompt: "Buy a pair of The Sleek Power Bezel Studs (18K), 4 carats total weight, ship to my partner in New York for our anniversary."
The agent fetches skill.md, picks the SKU and the variant (4 carats total weight), sends the shipping address. The 402 comes back with the total. The agent pays in tempo because that's what its wallet holds. The order shows up in Sayer & Stone's back office. Production starts. The buyer gets a delivery estimate by email.
What this says about agentic commerce
Martin Estate is the canonical "regulated commerce on agents" story. Sayer & Stone is the canonical "just open the surface" story. Each took one week.
The same SDK that wraps Martin's gate also handles Sayer's catalog discovery, 402 builder, MPP settlement, and Stripe SPT fallback. The merchant decides how much compliance they need. The stack stays the same.
Sayer & Stone is the second one running. There are more coming.
In the agent catalog
Earrings
Bracelets
Want to sell to AI agents? Talk to us, and we'll build you a version of this.
