THE AGENT-NATIVE MARKETPLACE

Commerce.
Built for
agents.

Your agent brings the intent. We bring the products, fresh data, and a clear path to checkout.

MCP first · REST ready · No human storefront

INTENT IN. COMMERCE OUT.01 — CONNECTION

Your agentANY MCP CLIENT

relay

MCP / REST

Partner catalogs

Partner checkout

ONE INTEGRATION. THE ENTIRE FLOW.

relay / playgroundINTERACTIVE SAMPLE

MCP TOOL CALL

// Find the right product, not another page.
relay.search({
  query: "wireless headphones",
  max_price: 200,
  in_stock: true
})

NOT ANOTHER DESTINATION.A better way to get there.

YOUR AGENT.
YOUR STACK.

Explore setup guides Compatibility validation planned

01 / THE PLATFORM

All the commerce.
None of the storefront.

Not a website for your agent to navigate.
A commerce layer it can actually use.

01 / AGENT INTERFACE

One protocol.
Every commerce action.

Search, inspect, check availability, build a cart, and hand off checkout. MCP-native tools, with a REST fallback for everything else.

searchdetailprice_stockcartcheckout

02 / UNIFIED CATALOG

Many feeds.
One source of clarity.

Partner catalogs, normalized into a single schema. Duplicate listings resolved before they reach your agent.

IngestNormalizeDedupe

03 / FRESHNESS MONITOR

A good recommendation
needs fresh data.

Price and stock refresh on a defined cadence. Stale offers stay out of the way. Final availability is confirmed by the partner.

No dead listings. No guesswork.

02 / FROM INTENT TO CHECKOUT

Your agent does the shopping.
The partner closes the loop.

Relay connects the steps.
You keep the experience.

Discover & decide

The agent finds the right products, checks the details, and confirms price and stock.

relay.search → relay.detail

Build the basket

Selected products and variants become a structured cart, tied to the agent and session.

relay.cart.create

Hand off checkout

Relay creates an affiliate-tagged checkout link. The shopper completes payment with the partner.

relay.checkout.handoff

Attribute the value

The partner records the transaction. Commission is reconciled to the originating agent and session.

agent_id + session_id

Partner checkout. Partner fulfillment. Clear attribution.NO PAYMENT HANDLING. NO STOREFRONT.

03 / DEVELOPER FIRST. AGENT READY.

Less glue code.
More possibility.

Start with the assistant you already use. Connect once, then give your agent the tools to move from a recommendation to a real basket.

✓ Purpose-built, typed commerce tools
✓ Assistant-specific quick starts
✓ Documented REST fallback
✓ Agent and session-level attribution

QUICK STARTPREVIEW CONFIG

Give Claude a commerce toolkit.

Add Relay to your MCP client configuration.

mcp-config.json

{
  "mcpServers": {
    "relay": {
      "url": "https://YOUR_RELAY_HOST/mcp",
      "transport": "streamable-http"
    }
  }
}

Example only. A provisioned Relay endpoint and credentials are required. Client setup varies.

BUILT TO EARN TRUST

Open by design.
Clear about what's next.

THE NEXT CONNECTION STARTS HERE

Great infrastructure.
Right first partner.

We're building the agent-native path to commerce.
The first decision? Which affiliate partner goes live on day one.

For retailers, affiliate networks,
and commerce partners.

A FEW THINGS, CLARIFIED.

Built differently.
On purpose.

Is Relay a storefront for people?

No. Relay is a structured commerce interface for AI agents. People complete their purchase through the affiliate partner's own checkout, not a Relay storefront.

How is Relay related to CRS?

They're separate products. Relay is a standalone agent-native marketplace; CRS keeps its own scope and identity. Any integration is a later chapter, not part of this launch.

Is the marketplace live yet?

This site is a developer preview. The playground uses sample data, endpoint examples are illustrative, and the first affiliate partner has not been announced. Live access follows partner onboarding and assistant validation.

Who handles payment and fulfillment?

The partner does. Relay creates the affiliate-tagged handoff and carries agent and session attribution. The partner confirms final price, availability, payment, delivery, and returns. Commission is subject to the partner's terms.

Commerce.
Built for
agents.

All the commerce.
None of the storefront.

One protocol.
Every commerce action.

Many feeds.
One source of clarity.

A good recommendation
needs fresh data.

Your agent does the shopping.
The partner closes the loop.

Discover & decide

Build the basket

Hand off checkout

Attribute the value

Less glue code.
More possibility.

Give Claude a commerce toolkit.

Open by design.
Clear about what's next.

Documentation, not mystery.

Tested, then badged.

Find us where agents connect.

Great infrastructure.
Right first partner.

Built differently.
On purpose.

Shape the day-one launch.

Commerce.Built foragents.

All the commerce.None of the storefront.

One protocol.Every commerce action.

Many feeds.One source of clarity.

A good recommendationneeds fresh data.

Your agent does the shopping.The partner closes the loop.

Discover & decide

Build the basket

Hand off checkout

Attribute the value

Less glue code.More possibility.

Give Claude a commerce toolkit.

Open by design.Clear about what's next.

Documentation, not mystery.

Tested, then badged.

Find us where agents connect.

Great infrastructure.Right first partner.

Built differently.On purpose.

Commerce.
Built for
agents.

All the commerce.
None of the storefront.

One protocol.
Every commerce action.

Many feeds.
One source of clarity.

A good recommendation
needs fresh data.

Your agent does the shopping.
The partner closes the loop.

Less glue code.
More possibility.

Open by design.
Clear about what's next.

Great infrastructure.
Right first partner.

Built differently.
On purpose.