
An AI agent priced parts by clicking through our website
On the morning of November 18 an AI coding agent opened our online quote page, uploaded two DXF files and stepped the quantity from 1 to 500 in 1/8 in birch plywood, reading the price off the screen at each step. Nobody at the shop knew it was coming. It got its answer, and it did it the slowest way possible. That session is why FSH Labs has an open API today.
Key takeaways
- An agent will use whatever door is open. Ours was a web page built for a person with a mouse.
- The page worked, which is the uncomfortable part. Working badly is easy to miss.
- What the agent wanted was a table: this file, these quantities, these prices. That is now one call.
- The agent guide is the page we wish that agent had found.
What did the agent actually do?
We know from our own request log, which records the kind of client and the pages it loads, never the file or its name.
It arrived at the instant quote from a desktop coding app. It uploaded a DXF. It chose birch plywood. Then it changed the quantity, waited for the price, and changed it again, all the way up to 500. Then it did the same with a second file.
A person asking that question is usually deciding how many to buy. So was the agent, on someone's behalf. It was building a price table by hand because we did not publish one.
Why was that the hard way?
Three reasons, and each one became a requirement.
It had to drive a browser. Loading a page, finding the upload control and reading a number out of rendered HTML is slow and brittle for an agent. A coding agent already has a shell and can make an HTTP request in one line.
It could not have used our pricing routes directly even if it had found them. They sit behind a bot check, which is the right thing for a web form and a wall for an agent.
It had to ask one quantity at a time. Fifteen page updates to learn how a price falls with quantity is fifteen chances to misread the screen.
What does one call return now?
The same question is one request to the laser cutting API: send the file, a material and a quantity.
The answer carries the price for that quantity, and the same job at eight quantities from 1 to 250, so the table that agent built by hand comes back in one piece. Ask for other materials and the same file is priced in each. Send a ZIP code and the answer adds shipping and the total before tax.
It also answers the question the page could only half answer: what is wrong with this file? Around the same time a person arrived from a chat assistant with a drawing whose lines did not close, got a message that we could not price it instantly, and left. Now a file like that still gets an answer, with a code for each problem and the position of each open line's two ends. An agent that drew the file can close the gap and send it again without a person in the loop.
To give a feel for the numbers, a 6 x 4 in plate with four holes, 20 pieces in birch plywood, is $53.40 today, or $2.67 each, before shipping and tax. The order minimum is $25.
What did we decide not to build?
A sign-up. The agent that visited had never heard of us and owed us nothing. If the first thing it met was a form asking for an email and a key, it would have gone elsewhere, and it would have been right to.
So there is no account and no key. Rate limits stand where the bot check stood. The only step with money in it is a payment link that a person opens and pays, and an agent never sees a card.
We also did not build a second pricing system. The API, the MCP server and the website all call the same engine, and the documentation is generated from the same list of operations the server runs. There is nowhere for the two to drift apart.
What would we tell another small shop?
Look at who is already using your site. We found this by reading one unusual line in a request log. If agents are doing a job on your pages one click at a time, they are telling you what to build.
Start with the quote, not the order. Pricing is what an agent needs to do its job, and it is safe to give away.
Say what you do not do. Ours does not make metal parts, does not read solid model files, and has one lead time of 7 to 10 business days for everything. An agent that knows that sends the right jobs.
Ordering from FSH Labs
If you use an agent, give it the agent guide. If you would rather do it yourself, the instant quote is still there, and it is the same price either way. Questions go to chaz@fshlabs.com or 678-210-6694.
FAQ
- Can an AI agent use the FSH Labs website quote page?
- It can, and one did. But it has to load a page, upload a file and change one field at a time. The open API answers the same question in one call, so that is the better way in for an agent.
- What stopped agents from pricing parts before?
- The website's pricing routes sit behind a bot check that no agent can pass, so the only way in was to drive the page like a person. The agent API has no bot check. Rate limits do that job instead.
- Is the API price the same as the website price?
- Yes. Both call the same pricing engine, so the two can not disagree.
- How do I point my agent at it?
- Give it the address of the agent guide, fshlabs.com/agents. It lists every call with a real request and answer. No account or key is needed.