Agentic Web Development
- ·Sites and apps where an agent does the work: answering in context, routing requests, running a task end to end.
- ·Built on the Next.js App Router with the model layer kept behind a server boundary.
- ·This console is the working example. Every command you run here is the same pattern.
| Built with | Next.js · TypeScript · Claude API · Vercel AI SDK · Vercel |
| Delivered by | · · design-director |
| Skills used | quality-gate · taste |
Receipts
What this involves
An agentic web application does work on the visitor's behalf instead of only displaying information for them to act on. It answers in context, routes a request, or runs a task end to end, and the model layer sits behind a server boundary so a key is never shipped to a browser.
The site you are reading is the worked example rather than the argument for one. One command registry drives the terminal, the file explorer and every canonical route, so each route is both a real server-rendered URL and a tab inside the frame. The suite that guards that engine runs tests with no framework to install, and the typo correction inside it was checked against an independent reference implementation over 20,000 string pairs with zero mismatches.
It also publishes itself as a remote MCP server, which is the part most sites cannot do: an AI client can query the projects, services and career record directly over Streamable HTTP instead of scraping the rendered page. Every tool result carries the canonical URL it came from, so an assistant can cite the page rather than paraphrase the site.
The same build carries a no-JavaScript path that still returns the full content, eleven interface locales, and a PROBLEMS panel that lists the seams that are still open. A limitation named in the interface is cheaper than one a client finds in month three.
This site publishes itself as a remote MCP server at /api/mcp, so an AI assistant can query the record directly instead of scraping the page.
How the work runs
1. Discovery
We agree what the project has to achieve, what it must not break, and how we will both know it worked, before any code is written.
2. Build
The work is built with an AI agent as the working partner and a human reviewing every change before it lands. You get commits you can read rather than a status update.
3. Review
You review running software at each milestone, not a screenshot of it, and the next milestone absorbs what you send back.
4. Launch
We deploy to production with checks in the pipeline and alerting that reaches a human, and you hold the repository and the infrastructure accounts.
Questions people actually ask
What makes a website agentic rather than just AI-powered?
An agentic website takes actions, while an AI-powered one mostly generates text. The distinction that matters commercially is whether the system can perceive context, decide, and complete a task without a human stepping in at each stage, or whether it produces a draft that a human still has to carry the rest of the way.
How do I check the work instead of taking the claim on trust?
Four ways, all of them things you can open yourself without asking. This site's build log replays real commits with their hashes against the public branch. The test suite is tests and runs with `npm test` on Node 22.6 or later, with no framework to install. The fuzz claim re-runs from a fixed seed in tests/suggest-fuzz.test.ts. And the site is an MCP server, so your own assistant can query the record rather than trust a page.
Where does the AI model actually run, and who holds the key?
The model layer stays behind a server boundary, which means the API key lives in a server environment variable and never reaches the browser. A client-side key is readable by anyone who opens developer tools, and it is the most common way a first agentic feature leaks its own billing.
Can agentic features be added to a site that already exists?
Yes, and adding one workflow at a time is usually the cheaper order. A single agentic route can be built behind the existing site and cut over when it works, which keeps the current site earning while the new path is proven.
How long does an agentic project take?
Scope decides this, and no honest single answer covers it, so here is what can be shown instead of a promised range. Two of the projects on this site were built in one day each and are live now. The site's own build log carries real commit hashes you can check against the public branch. Ask for a timeline against a written scope and it comes back as a date with the assumptions attached, not as a marketing range.