MCP GSC AI Agent Carrier Class Fleet

The three live fleet roots — Global, APAC, LATAM — with regions, slot ranges, and entry points. Headline: 10,597 LIVE across nine sovereign jurisdictions.

Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern.

(fleet, slot) → the canonical Card URL. Validates the slot against the fleet's real range; the Card itself is the source of truth — fetch it to confirm the Carrier.

SM-ECO-10060 member code → the serving surface: a resident sovereign endpoint where one exists, otherwise the fleet root covering that member's region. Category and capability addressing ship with the sovereign Carrier set and will answer here as they go live.

Where GSC Carriers are resident — all nine jurisdictions, each with its serving Azure region. Residency is the checkable claim.

Member code → residency status, serving endpoint, and Azure region.

How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.

Canon fleet numbers: 10,597 LIVE across nine sovereign jurisdictions, 9.5M agentic inbound signals per month, 1.5M human visits per month.

The Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's.

Which GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each.