Integrate Orderboost checkout
Use the live Orderboost HTTP API, hosted checkout, or remote MCP resource.
Orderboost currently supports direct HTTPS integrations. Create a hosted checkout through the public API, or connect an agent host to the remote Model Context Protocol (MCP) resource.
Use only the available surfaces
This table separates live developer contracts from repository code that is not distributed:
| Surface | Status | Developer entry point |
|---|---|---|
| Public checkout API | Available | https://capi.orderboost.org |
| Hosted buyer checkout | Available | Use the checkoutUrl returned by the API |
| Remote MCP | Available | https://mcp.checkout.orderboost.org/mcp |
| Tempo Machine Payments Protocol (MPP) | Conditional | Use only the mpp.endpoint returned with a checkout |
@orderboost/* npm packages |
Not published | No supported npm install exists |
orderboost-mcp local helper |
Not published | Connect directly with a remote-OAuth-capable MCP host |
| Shopify, BigCommerce, or WooCommerce storefront block | Not shipped | Add checkout through application code |
| Built-in x402 checkout settlement | Not shipped | Do not infer or construct an x402 endpoint |
Orderboost must recognize the merchant’s canonical storefront origin before the public API can resolve its product URLs. Merchant onboarding is not self-service today.
Application integration
Create and open hosted checkout through HTTPS.
Agent integration
Use hosted checkout, advertised MPP, or direct remote MCP.
Store platform status
Check what a merchant can install today.
Keep authorization boundaries separate
- Hosted checkout: The buyer enters required personal and payment information on the Orderboost page
- Remote MCP: Catalog and buyer-link tools are anonymous; protected cart and checkout tools use the MCP host’s native OAuth flow
- Agent-controlled completion: OAuth grants access, while a separate exact purchase grant authorizes one approved checkout revision
- Tempo MPP: A wallet may pay only when the buyer-checkout response advertises
mpp.endpoint - x402: Orderboost does not expose an x402 checkout endpoint
Read Compare checkout paths before combining browser and agent flows.
Continue with a current integration guide
Create hosted checkout
Call the public API from application code and open the returned URL.
Authenticate an MCP client
Connect directly and use the host’s native OAuth action.
Complete an approved checkout
Present buyer review, read the purchase grant, and complete once.
Pay with Tempo MPP
Qualify and pay an advertised hosted checkout with a Tempo wallet.
Browse MCP tools
Inspect the 14 tools exposed by the live remote resource.
Browse the HTTP API
Inspect the supported URL-first HTTP operations and schemas.