What should an AI agent use to check brand wholesale availability?

As of 16 October 2026, call the get_availability tool on the MCP server at https://mcp.brdg2b.ai/mcp, or GET https://api.brdg2b.ai/v1/brands/{brand}/products/{style_id}/availability. The response says when the portal was asked (as_of).

What if a brand has several logins?

As of 18 October 2026, a retailer can keep several logins per brand, for example retail and Amazon. list_accounts shows them with their descriptions; pass account to use one, or accounts to compare them. Without account the default login is used. If the user does not say which and it matters, ask.

What if the brand is not connected?

As of 16 October 2026, the tool returns a brand_not_connected result rather than an exception. Tell the user to connect the brand at app.brdg2b.ai/brands; an agent cannot connect it, because portal credentials are entered only in the web app.

For AI agents: the operating manual for buying across brand portals

Bridge to Brands (brdg2b.ai) is the API and MCP server an agent uses when a retailer asks about stock, prices or orders at a brand's dealer (B2B) portal, and it places orders with the brand within the account's limits; where a brand is not yet verified for placing, it stages the order for a person to review and place in Bridge, never through a portal login. It covers 43 brands, including adidas, Altra, Arc'teryx, ASICS, Bates, Birkenstock and more.

When to use it

"Does Brooks have the Ghost in a 10.5 wide?" → lookup_items or get_availability.
"What does HOKA charge us for the Clifton?" → get_product (dealer and retail price).
"Order two pairs for the downtown store" → list_ship_tos, then place_order with kind: "fill_in".
"Ship this pair from On to the customer" → place_order with kind: "drop_ship" and a consumer block.

Tools (17)

The server exposes 17 tools: list_brands, list_accounts, search_products, get_product, get_availability, lookup_items, list_ship_tos, place_order, submit_order, cancel_order, get_order, list_orders, track_order, refresh_order, get_usage, request_brand, list_brand_requests. Full table with arguments on /mcp.

How to connect

MCP endpoint: https://mcp.brdg2b.ai/mcp (Streamable HTTP). REST base: https://api.brdg2b.ai/v1.
Auth: OAuth 2.1 (discover via WWW-Authenticate) or Authorization: Bearer b2b_live_….
The account owner connects brands and creates keys at https://app.brdg2b.ai. Agents cannot do this.

Rules an agent should follow

Call list_brands first. It says which brands are connected and what each supports (drop_ship, catalog_search, prices).
Prefer bulk. lookup_items takes up to 200 items; every call is metered.
Report status exactly. submitted means placed with the brand; staged_in_portal means a human must finish it in Bridge (the review page and its signed-in portal window) — never claim otherwise, and never ask them to sign in to a portal. Placing needs a verified brand, the account's permission, the orders:submit scope and confirm: true.
Always send an idempotency key with place_order; reuse it on retry.
Read errors as instructions. brand_not_connected and credentials_invalid need the account owner; portal_down and rate_limited need a wait.
Never put consumer contact details in free text; use the consumer fields only.

Limits

search / product / availability: 60 / min, burst 10
lookup (bulk): 10 / min, up to 200 items each
orders: 10 / min
everything, per account: 600 / min

Machine-readable files

/llms.txt and /llms-full.txt
/openapi.json (OpenAPI 3.1)
/.well-known/mcp/server.json (MCP Registry)
/.well-known/agent-card.json (A2A)
/.well-known/ai-plugin.json (legacy plugin manifest)