Sourcing tools and AI assistants can now read the catalog through a documented interface instead of scraping pages. /api/ exposes nine endpoints: the model list and one model by code, the categories, the feature tags, the factory facts, the FAQ, the topic pages, and an RFQ preparation endpoint that turns a buyer's requirements into the fields the factory needs. The machine-readable description of all of them is published at /ai/openapi.json.
An MCP server at /mcp answers the same questions over JSON-RPC 2.0 with eight tools: search_models, get_model, list_categories, list_feature_tags, get_factory_facts, search_faq, list_topic_pages and prepare_rfq. A GET request returns the server card, so an agent can discover what is available before calling anything.
For buyers who want one file to circulate internally, the catalog is also published as a printable 15-page PDF at /catalog/, and the static machine layer under /ai/ (products.json, products.csv, topics.json, faq.json, ningboware-facts.json, changelog.json) is unchanged and still the fastest way to read the whole catalog in one request.