We built the first agent-native Indian factory.
Here's why.

Our workshop opened in 1992 with a few artisans and one idea: make things well, or don't make them at all. Thirty-four years later, fifty artisans work the floor. Two hundred more across our network in Moradabad. We ship brass, copper, and heritage home goods to buyers in more than thirty countries. This part is old news. We want to tell you about a new thing.

This week, Hands & Craft became — as far as we can tell — the first Indian manufacturing workshop with a public, agent-callable interface. Point an AI agent (Claude, ChatGPT, Perplexity, a HubSpot Breeze copilot, a custom framework) at handsandcrafts.com/api, and the agent can search our catalog, check our capacity, pull our compliance summary, request samples, get rough quotes, and book calls — all programmatically, without a human on our side being a bottleneck. A real factory you can call, in code.

Why build this

Every serious B2B buyer we know is using AI agents to research suppliers in 2026. Not to write their cold emails — to do their sourcing research for them. They open ChatGPT or Claude and type: "find me three factories in India that can make 5,000 hand-hammered brass serving bowls, food-contact certified, MOQ under 500, ship by August." The agent goes and reads fifty factory websites. Most of those websites are pretty pictures glued together for human eyes. The agent extracts nothing useful. The factory gets skipped.

Moradabad has more than two thousand export houses. Most of them have websites that look roughly the same: a hero image, a catalog page, a vague "About Us" with the word "premium" on it, a contact form that nobody reads. We had one of those websites too. It didn't work, because nothing about it was actually machine-readable, and very little of it was genuinely useful to a human buyer either.

Two things can be true at once. B2B handicraft sourcing is still mostly a human, relationship-driven business — our buyers from Ambiente Frankfurt are still mostly people, not bots. And also, the humans' tools are getting smarter, and in eighteen months the first question a procurement team asks won't be "what does Google find" but "what does my agent find." The factories that are legible to those agents — that have structured data, working endpoints, and honest metrics — will get called. The factories that don't won't. This is not a prediction. It's already happening, quietly, in every Slack channel of every small B2B company in the West.

What "agent-native" actually means

It isn't AI marketing fluff. We don't have "AI-powered quality checks" or "intelligent product recommendations." We have a boring, useful substrate of JSON files at /data/business.json, /data/skus.json, and /data/capabilities.json that describe our workshop in machine-readable form: what we make, how we make it, what MOQ, what lead times, what compliance, what the capacity is, what the defect rate looked like last month. Every page on our website reads from these files. So does the API. One source of truth.

On top of that substrate, we exposed a small set of tools any agent can call. search_skus to find matching products. get_capabilities to list what we make. check_capacity to see if we can start production in June. request_sample to ship a sample to Brooklyn. get_quote to get a rough estimate at a specific quantity. schedule_call to book time with our team. request_access for buyer onboarding. Each one returns real data or creates a real record in our workshop's queue. When an agent calls request_sample, our team is notified within seconds, and a human replies within two hours during working hours. The machine starts the conversation; a human finishes it.

This is the thing we keep coming back to. Agents are good at search, filtering, extraction, and triggering. They are bad at trust, judgment, and craft. Humans are the opposite. The winning pattern is not "replace humans with agents." It's "let agents do the part of sourcing that is mechanical, and let humans do the part that is judgment." Our workshop is built to sit exactly on that seam.

Why now, why us

The agent-native move fits us specifically because it uses everything we already have. Our thirty-four years — every choice made since 1992, every artisan on the floor, every relationship built with buyers — is the trust substrate. And our online presence is the interface layer. The floor keeps making beautiful objects by hand, in a city that has been making them for four centuries. The interface makes sure the world's procurement agents know the workshop exists and can work with it without anyone having to fill out a PDF.

The moat here isn't technical. The API is a few hundred lines of code. Any factory with a smart kid and a weekend could copy it. The moat is that most factories don't have a smart kid with a weekend, most factories aren't run by people who have been obsessed with the internet for a decade, and most factories don't have a thirty-four-year backstory to put underneath the API. All three conditions at once are rare. For the next twelve to eighteen months, we are one of them.

What happens next

This is a beginning, not an ending. The substrate starts with sixty hero SKUs — we'll expand it to the full catalog over the next few months, carefully, because honest data is better than a lot of data. We'll add more tools as buyers and their agents tell us what they actually need. We are publishing real metrics — response time, sample turnaround, on-time delivery, defect rate — and we will keep publishing them even when they are not flattering, because transparency is a claim you can't fake.

If you are a buyer who sources physical goods from India, come test us. Point your agent at the API. Or skip the agent and request trade access. We respond in under two hours during working hours and will tell you honestly if we are a good fit for what you are making. If we are, we will make you something beautiful. If we are not, we will tell you that too, and we might still be friends.

If you are another factory reading this — in Moradabad, Jodhpur, Guangzhou, anywhere — copy everything. Build your own substrate, build your own API, publish your real numbers. The world of 2026 has room for many trusted factories and very little room for opaque ones. The sooner our whole industry stops hiding behind template websites and starts being readable by the systems our buyers actually use, the better for all of us.

If you are a developer or a buyer-tooling builder, the OpenAPI spec is at /openapi.json and the API base is at /api. Both are free to use. No API key. No credits. No gatekeeping. See the agent documentation for the full interface. If you build something useful on top of us, tell us, and we will send you a hand-hammered brass bowl as a thank you. It will take an artisan in our workshop about ninety minutes to make. The marks on the bowl will be from a hammer. No agent can make that.

— Hands & Craft
Moradabad, India
info@handsandcrafts.com · Request trade access →