Changelog

2026-10-17: the Browser orders; orders are reviewed and placed in Bridge

• The web Browser now orders: add from the availability grid, paste or upload a list (CSV or XLSX; a multi-brand sheet is split into one basket per brand), then check out a fill-in to a store or a drop-ship to a consumer address.
• A staged order is reviewed in Bridge: the portal basket is read back line by line against what was asked. Where the brand is verified you place it from Bridge; otherwise you finish it in the portal window — the brand’s real portal, already signed in, inside Bridge. Nobody signs in to a vendor portal.
• API and MCP order messages and portal.instructions now point to the review in Bridge instead of a portal sign-in.

2026-10-16: Karhu and Diadora connectors

• Two brand connectors added, lifted from RunOps production: Karhu (b2b.karhu.com, a Shopify store; orders staged as a new cart per store and warehouse) and Diadora (b2b.diadora.com; orders staged in the account’s one cart, one store at a time).
• 45 verified connectors listed: 43 brand connectors plus the NuORDER and Wolverine Worldwide platform logins.
• Neither brand offers drop-ship, catalog search or submit yet; their orders come back as staged_in_portal for review in Bridge.

2026-10-16: public site and v1 contract published

• Published the v1 REST API contract (https://api.brdg2b.ai/v1) and the MCP tool list (https://mcp.brdg2b.ai/mcp).
• MCP server auth decided: OAuth 2.1 and API-key bearer; the REST API is API-key only.
• 43 verified connectors listed: 41 brand connectors plus the NuORDER and Wolverine Worldwide platform logins, across the NuORDER, Elastic Suite, Envoy, Epicuro and BigCommerce B2B Edition platforms and brand-built portals.
• Machine-readable surface: /llms.txt, /llms-full.txt, /openapi.json, /.well-known/mcp/server.json, /.well-known/agent-card.json.