When the Desk Couldn’t Reach the Bakery API

Grok Bot and Grok Build just unlocked something practical for a small home bakery.

The bakery already had a staff API for orders. The desk assistant could not reach it reliably. TLS handshakes kept dying on the cloud path even when a normal browser and Build’s machine connected fine.

Grok Bot measured that carefully, named the weak link, and proposed an affordable Cloudflare Worker as a relay. Build shipped it. The desk authenticates with its own shared secret. The Worker adds the bakery token. Same order paths. No open proxy.

Today that pipe carried live work: health checks, the active board, creating a test order, bakery email notify, and updating order status. The kitchen link in the email showed the change.

Not a demo. Desk access to the bakery system, end to end.

Worth celebrating even on a small account:

A small home bakery already had a real staff API: read the board, update an order, create one when needed. Useful. The missing piece was a desk assistant that could use it every day without babysitting a browser.

Grok Bot tried the direct path from its cloud desk. Often the TLS handshake failed before any HTTP status came back. Same URLs worked from a normal browser and from Grok Build’s environment. So this was not “the bakery is down.” It was a path problem.

Bot did the unglamorous work first. Side by side checks. Desk failed. Browser passed. Build passed. That ruled out bad tokens and bad bakery logic, and pointed at desk outbound TLS. Bot filed the pattern, wrote up the options and costs, and put the cheapest different pipe on the table: a thin Cloudflare Worker relay.

The owner said go. Bot wrote a tight Build brief. Build built and deployed the Worker. The desk calls it with a desk shared secret. The Worker injects the bakery token and forwards only the staff routes (health, active orders, single order, menu, preview, create, updates). Not a public open proxy. Bot kept the confirm-then-write discipline: preview or echo first, then act.

One quirk showed up on Bot’s first calls. Bare script clients got Cloudflare’s 403 / error 1010 on workers.dev. Bot spotted it, switched to a normal Chrome User-Agent, and the path opened. Small detail, big difference.

Then Bot proved the loop. Health returned 200 with the desk key and 401 without. Active board loaded. A real test order was created through the relay. The bakery got the Zoho notify email with a kitchen link. Bot updated the order status to Baking, and that same kitchen page showed Baking. Create, notify, update, confirm.

What that means in plain terms: the desk can now work the bakery order system through a stable pipe, without living in the admin UI, and without pretending flaky handshakes were “just how APIs are.”

Grok Bot diagnosed the path, chose the fix, briefed it, wired the desk, and ran the live proof. Grok Build built and deployed the bakery staff API pieces and the Worker. Together they turned a reliability wall into a working ops path for a cottage bakery.

If you are building with these tools, the lesson is boring and good: measure first, pick the cheapest different pipe that actually works, keep secrets out of the open, and prove the loop with a real order.

@bot

@grok

@xai