Choose an agent checkout path

Start hosted buyer checkout through HTTP, use advertised Tempo MPP, or connect directly to remote MCP.

Agents can use Orderboost today through the public HTTPS API or the hosted remote Model Context Protocol (MCP) resource. Orderboost does not publish an agent SDK or local MCP helper.

Choose the control level

Need	Start with	Payment owner
Buy one known product	Public buyer-checkout API	Buyer on hosted checkout
Share a checkout link from MCP	Anonymous `create_buy_link`	Buyer on hosted checkout
Pay one hosted checkout by wallet	Returned `mpp.endpoint`	Tempo wallet policy
Control cart and checkout state	Remote Orderboost MCP	Agent after exact human approval
Pay another protected resource	Its own advertised MPP or x402 contract	Agent payment policy

Use Tempo MPP only when the buyer-checkout response includes mpp.endpoint. Orderboost does not ship built-in x402 checkout settlement.

Open hosted buyer checkout

Post the exact registered product URL to the public API:

const response = await fetch("https://capi.orderboost.org/api/v1/buyer-checkouts", {
	body: JSON.stringify({
		productUrl: "https://store.orderboost.org/product/acme-mug",
		quantity: 1,
	}),
	headers: { "content-type": "application/json" },
	method: "POST",
});

if (!response.ok) throw new Error(`Checkout creation failed (${response.status}).`);
const { checkoutUrl } = (await response.json()) as { checkoutUrl: string };

Give checkoutUrl to the buyer or open it in a browser. The buyer enters required personal and payment information on the hosted page. The agent does not call complete_checkout for this path.

Connect directly to remote MCP

The live Streamable HTTP resource is:

https://mcp.checkout.orderboost.org/mcp

The endpoint uses the MCP TypeScript SDK 2.0 stateless handler, supports the 2026-07-28 protocol, and keeps stateless compatibility for initialize-based clients. It does not issue transport session IDs or require a sticky connection to one server replica.

Catalog connection, the three catalog tools and create_buy_link are anonymous. A host needs remote MCP OAuth only for protected cart, checkout or handoff operations. The first protected call starts the host’s native OAuth flow.

Orderboost does not publish an orderboost-mcp command, stdio bridge, or six-digit chat authorization tool. A host without remote MCP OAuth cannot use protected Orderboost tools today.

When a buyer asks for a purchase link, call create_buy_link with the exact canonical variant URL and return its checkout_url. Do not attempt a protected cart or report checkout as unavailable because OAuth is absent.

Run direct checkout through MCP

Follow the protected checkout lifecycle:

Find the product

Call search_catalog, lookup_catalog, or get_product. Use the canonical variant URL returned by Orderboost.

Authenticate protected tools

Attempt create_cart or create_checkout, then use the MCP host’s native OAuth action when Orderboost returns the authorization challenge.

Create checkout

Treat the returned items, total, revision, and status as authoritative.

Request human approval

Open the exact continue_url when checkout returns requires_escalation.

Complete once

Refresh with get_checkout, then call complete_checkout with the current purchase grant and one stable idempotency key.

Never ask for passwords, OAuth tokens, payment credentials, or a handoff code for a new purchase.

Pay the hosted URL with Tempo MPP

When buyer-checkout creation includes mpp.endpoint, an authorized machine wallet can post the exact checkoutUrl there. Orderboost first returns any missing buyer, billing, fulfillment, and shipping-option paths without requesting payment. The qualified request uses one Idempotency-Key; Orderboost requotes before returning a Tempo charge challenge.

The paid retry must use the identical endpoint, body, and key. Require Payment-Receipt, completed checkout state, and orderId.

Follow Pay a hosted checkout with Tempo MPP for the client flow. Read Authenticate an MCP client for remote connection setup.