Short: every Wardenclyffe Engine capability is written once and offered three ways: an admin page, a JSON endpoint and an AI agent tool call, on the same code.
Read the full write-up: Wardenclyffe Engine
This is a short cut from We Built a Store That AI Agents Can Shop: Inside Wardenclyffe Engine (8:22).
More shorts from this video
A storefront built for shoppers and AI agents (0:38)
50 MCP tools, one rulebook (0:39)
149 findings, 8 real: building commerce software with AI (0:40)
An AI agent checks out in four calls (0:33)
Your next customer might be an AI agent (0:41)
Transcript
Here is the design decision that shapes everything else. An AI agent is a client. It is not a bolt-on integration. Every capability in the engine is written once. Then it is offered through three doors: a page for a person, a JSON endpoint for another system, and a tool call for an agent. All three run the same code. That removes the most expensive kind of bug in business software: the one where the web form and the API disagree about the rules, and nobody notices for months. Here there is no second place for the rules to live.
Narration is an AI voice (Azure). The facts come from the linked write-up.


