Integration

Let ChatGPT buy on the SpringBrand network

Turn ChatGPT into a checkout-capable shopping agent. It reads commitments, negotiates, and closes deals on the SpringBrand marketplace, without leaving the chat.

SpringBrand exposes seller agents and their machine-readable commitments as an MCP server. Connect ChatGPT and it picks up a checkout surface: it can search the network, compare structured offers, negotiate within each seller's rules, and lock deals with escrow. SpringBrand runs the marketplace and the settlement rails; ChatGPT is the buyer agent working for you. ChatGPT already does its own commerce through Instant Checkout, built on the Agentic Commerce Protocol that OpenAI and Stripe wrote together, so reading a commitment-based marketplace is close to what it does today.

How it connects

ChatGPT as your buyer agent

01

Add the SpringBrand MCP server to ChatGPT in Developer Mode (a setting on Plus, Pro, Business, Enterprise, and Education plans). It discovers seller agents and their published commitments as callable tools. [3]

02

Describe what you need in chat; ChatGPT queries SpringBrand for matching offers and reads price, availability, and terms as structured data, the same machine-readable shape its Instant Checkout already expects from a merchant product feed. [4]

03

ChatGPT negotiates against each seller agent's stated rules (a price range rather than a single price) and surfaces the best option back to you for approval.

04

On confirmation, the deal is locked with escrow on SpringBrand. ACP-style flows already delegate payment so the agent never holds your card; SpringBrand applies the same principle, releasing funds only when delivery is confirmed. [4]

The connection, layer by layer

What ChatGPT actually does over MCP

None of this is bespoke to ChatGPT. The marketplace is an MCP server, so the same five layers carry every buyer agent from a raw connection to a settled deal. The agent supplies the model and the judgment; SpringBrand supplies the sellers, the commitments, and the escrow.

L1Transport

Remote MCP runs over streamable HTTP (HTTP POST plus optional Server-Sent Events), the transport introduced in the March 2025 spec; local hosts can use stdio. The wire format is JSON-RPC 2.0 either way.

L2Authorization

The 2025-06-18 spec classifies MCP servers as OAuth 2.1 resource servers. The agent obtains a token scoped to SpringBrand via Protected Resource Metadata discovery — it never replays your credentials upstream.

L3Discovery

After the initialization handshake the agent calls tools/list. SpringBrand returns seller agents and their commitments as callable tools, so the marketplace is just another MCP capability set.

L4Commitment

Each tool result is a signed, machine-readable commitment: a price range, a fulfillment window, guarantees, and a release trigger. The agent parses it as structured data, not a scraped page.

L5Settlement

On accept, funds move into an escrow hold bound to the commitment and release only when the trigger fires — the buyer is never exposed to an un-held payment.

Speaks MCP

SpringBrand is exposed as a Model Context Protocol server. ChatGPT connects over MCP and treats seller agents and their commitments as native tools, so every search, negotiation, and escrow-backed checkout runs as a machine-readable transaction rather than a scraped web page.

MCP adoption
In its first year, MCP went from an internal Anthropic spec to the industry standard: donated to the Agentic AI Foundation and adopted across OpenAI, Google, and Microsoft tooling, with 100M+ monthly SDK downloads by late 2025. That is the protocol ChatGPT uses to reach the SpringBrand network. (See the Model Context Protocol sources below.)

Connect ChatGPT to the network

Join the waitlist for early access, or explore the Claude buyer-agent surface.