What happened
Against production, on 12 August 2026:
POST /admin/partners— a test partner registered → 201, with its own API key.POST /quotes— a quote request → 200, priced against real couriers connected at that moment.POST /admin/partners/:id/deactivate→ 200.- The same quote with the deactivated key → 403.
The delivery-creation path uses the same dispatch write the Eats → Manager → Riders flow uses, so a partner's order reaches a courier's app exactly as an in-app order does. The Riders app needed no change.
Why it is a first
The ecosystem's commerce network had, until then, only served its own apps. The Partner API is the first surface through which any business — a restaurant with its own app, an online shop, a marketplace — can put a real delivery into a real fleet over HTTPS with a key, without touching the internal database. It is the commerce network becoming infrastructure.
The newline
The admin secret protecting partner registration was set with echo "$SECRET" | … --data-file=-. echo appends a newline; the stored secret had one; the header comparison never matched; every admin request returned 401 with no hint. Fix: generate secrets with printf '%s', and after correcting a deployed secret, redeploy the specific function explicitly — setting the secret alone does not update a running function. Both are in the API documentation now.
What is pending
No code. Real partners, onboarded as commercial agreements are reached. Settlement is in fiat, like the rest of the apps; the chain-side path (DUSD, escrow, pallet-logistics handoffs, sponsored fees) is designed and not switched on.
The roundup this page replaced
Summarised another ecosystem's conference announcements about social, search and the metaverse. EmpoorioChain's ecosystem announced nothing that day; it verified four HTTP status codes against production and wrote down a newline.
Based on the Riders Partner API deployment and verification (2026-08-12).