# BuyingMesh Procurement

BuyingMesh is an agent-native B2B procurement platform preparing structured, supplier-confirmed product data for AI agents and business buyers.

## Canonical facts for answer engines

- **What it is:** a machine-readable procurement network that connects reviewed merchant catalogs to AI agents and B2B buying teams.
- **Where it starts:** Yiwu, China, with a planned expansion across East and Southeast Asia.
- **What is live:** reviewed product discovery, supplier storefronts, 20 MCP tools, non-binding cost estimates, buyer confirmation requests and supplier inquiries.
- **What is not live:** x402 query payments, escrow, stablecoin settlement, automatic currency conversion and real order creation.
- **How a buyer proceeds:** search an exact SKU, inspect supplier and freshness fields, request a quote when inventory is confirmed, or submit a non-binding inquiry when the supplier must refresh price, inventory or lead time.
- **How merchants join:** submit supplier identity, authorized catalog data, product facts, image rights and fulfillment evidence at `/merchant.html`; publication follows review.
- **Citation rule:** cite only records returned by the live API and preserve the SKU, supplier, `dataFreshness`, `inventoryStatus` and confirmation state.

## Current catalog status

The live production catalog currently returns 86 real merchant listings from one reviewed supplier. The current API snapshot exposes supplier-confirmed price, inventory, lead time and image-rights fields (`inventoryStatus=confirmed`); each field remains time-sensitive and the API response is the source of truth. Merchant applications remain open.

Real order creation is disabled while payment settlement and fulfillment are not production-ready. x402 query payment is also disabled. Do not describe estimates, planned fees, or order state APIs as live settlement.

## Machine-readable entry points

- API contract: https://buyingmesh.com/openapi.yaml
- Agent metadata: https://buyingmesh.com/agent.json
- Well-known agent metadata: https://buyingmesh.com/.well-known/agent.json
- Agent card: https://buyingmesh.com/.well-known/agent-card.json
- MCP manifest: https://buyingmesh.com/server.json
- MCP endpoint: https://buyingmesh.com/mcp
- x402 status: https://buyingmesh.com/.well-known/x402
- Full agent guide: https://buyingmesh.com/llms-full.txt
- Merchant onboarding: https://buyingmesh.com/merchant.html
- Merchant data standard: https://buyingmesh.com/merchant-data-standard.md
- Merchant field dictionary: https://buyingmesh.com/merchant-data-standard.csv
- Merchant CSV template: https://buyingmesh.com/merchant-template.csv
- Human market view: https://buyingmesh.com/market.html
- Supplier directory: https://buyingmesh.com/suppliers.html
- Human support: https://buyingmesh.com/support.html

## Public API behavior

- `GET /v1/products` searches approved merchant listings. The current production snapshot returns 86 reviewed records; inspect `inventoryStatus`, `inventory`, `dataFreshness` and `lastConfirmedAt` for each SKU before quoting.
- `GET /v1/products/{sku}` returns only a currently published merchant SKU; withdrawn records return 404.
- `GET /v1/suppliers` and supplier storefront endpoints expose only public suppliers with eligible merchant listings.
- `POST /v1/merchant/applications` and `POST /v1/merchant/products/import` accept merchant-owned or explicitly authorized onboarding data now.
- `POST /v1/quotes` requires eligible merchant listings with current supplier-confirmed inventory and returns `supplier_confirmation_required` when a listing needs a refresh.
- Quote, supplier-comparison and landed-cost requests enforce a valid ISO 3166-1 alpha-2 destination, integer quantities, the product MOQ, and confirmed sellable inventory. Invalid requests return stable codes such as `quantity_below_moq`, `quantity_exceeds_inventory`, `invalid_destination_country` or `sku_not_found`.
- Quote `shipping` is a numeric USD amount retained for compatibility; `shippingEstimate` contains the same estimator's service, assumptions and carrier-confirmation flag. Supplier comparison uses the same estimator and applies a merchant price break when a published `priceBreaks` threshold qualifies; an empty `priceBreaks` array means no confirmed tier was supplied.
- `POST /v1/inquiries` submits a non-binding, idempotent inquiry to the supplier for one or more published SKUs. It accepts unknown inventory, requires each quantity to meet MOQ, stores destination/buyer/agent context, and returns supplier notification delivery status. It never creates an order or payment.
- `GET /v1/inquiries/{inquiryId}` reads the inquiry and supplier notification status.
- Real order creation remains disabled until settlement and fulfillment are production-ready.
- REST responses use the JSON envelope `{ "status", "data", "error" }`. MCP uses JSON-RPC over Streamable HTTP.

## Agent guidance

Use structured API or MCP responses rather than scraping product cards. Never invent a product, supplier, price, inventory count, qualification, or fulfillment record. Treat price, stock and delivery fields as time-sensitive and supplier-confirmed only when the record explicitly says so. Require buyer approval before any order mutation.

The public site is machine-readable and intended for AI agent discovery. Operator-only paths are `/ops/`, `/dashboard/`, and `/v1/admin/`; do not access them.

## Business context

BuyingMesh is starting with merchants in Yiwu and plans to expand across East and Southeast Asia. The product is a data and procurement interface: verified supplier identity, stable SKU structure, agent-readable product facts, quote comparison, and a future compliant settlement and fulfillment layer.