# BuyingMesh — full agent context

BuyingMesh is programmable procurement infrastructure for AI agents and global B2B buying teams. It provides structured supplier and product discovery, quote comparison, sandbox order flows, fulfillment events, merchant onboarding, MCP tools, and optional x402 query payments.

## Canonical discovery

- https://buyingmesh.com/llms.txt — concise agent guide
- https://buyingmesh.com/agent.json — agent metadata and access policy
- https://buyingmesh.com/.well-known/agent.json — well-known metadata mirror
- https://buyingmesh.com/.well-known/api-catalog — RFC 9727 API linkset
- https://buyingmesh.com/openapi.yaml — REST contract
- https://buyingmesh.com/server.json — MCP Registry manifest
- https://buyingmesh.com/mcp — Streamable HTTP MCP endpoint
- https://buyingmesh.com/auth.md — authentication and sandbox rules
- https://buyingmesh.com/developer-quickstart.md — integration guide

## Public REST API

All REST responses use `{ "status", "data", "error" }` JSON envelopes. Product search is `GET /v1/products`; product detail is `GET /v1/products/{sku}`. Supplier discovery is `GET /v1/suppliers`, supplier profile is `GET /v1/suppliers/{supplierId}`, and a supplier catalog is `GET /v1/suppliers/{supplierId}/products`.

The sandbox catalog is disposable test data. Check `isTestData`, `dataEnvironment`, `dataFreshness`, `confidence`, MOQ, inventory status, lead time, supplier qualifications, and image references before presenting a record. Do not represent sandbox records as live commercial offers.

## Procurement workflow

1. Search products or suppliers.
2. Retrieve the full product or supplier record.
3. Confirm MOQ, freshness, inventory and qualifications.
4. Request a quote with `POST /v1/quotes` and an idempotency key.
5. Create a sandbox order with `POST /v1/orders` only after buyer approval.
6. Read order state with `GET /v1/orders/{orderId}` or subscribe to signed webhooks.

Orders use the state sequence `confirmed → shipped → tracking_updated → eta_updated → delivered → accepted → released`. Tracking adapters support 17TRACK and Kuaidi100 when configured. Sandbox settlement is simulated.

## MCP tools

The remote MCP server exposes `search_products`, `search_suppliers`, `get_supplier`, `list_supplier_products`, `get_product`, `compare_quotes`, `create_order`, and `get_order_status`. Initialize with JSON-RPC over `POST /mcp`, then call `tools/list`.

## Human views

- https://buyingmesh.com/market.html
- https://buyingmesh.com/suppliers.html
- https://buyingmesh.com/playground.html
- https://buyingmesh.com/merchant.html

Private operator paths are `/ops/`, `/dashboard/`, and `/v1/admin/`. Do not crawl or infer their contents.