Free Trial
Free
Read-only catalog access for evaluation. Capped to product + category browsing.
- Approval
- Instant
- Channels
- REST
- Delegated access
- Yes
- Direct GraphQL access
- Yes
- Freshness
- 1h
- Completeness
- 99%
- Accuracy
- 99%
Released · May 31, 2026
Real-time European aftermarket catalog with structured product data, multi-currency pricing, and live stock levels.
Fed from the same backbone that powers ACME's own commerce surface, so your subscribers see the catalog before end-customers do.
Plans
Same governance on every plan: caller policy, audit row per call, rate limits — across every channel. SDK access over GraphQL is always included. Plans differ in which channels you open (REST, MCP, NLQ), how much volume you sell, and which capabilities you unlock.
Free
Read-only catalog access for evaluation. Capped to product + category browsing.
$199.00/mo
14-day free trialFull catalog + commerce access for production B2B integrations. REST + MCP for AI agent workflows.
Capabilities & data
$999.00/mo
30-day free trialHigh-volume access with direct Apollo Router for sub-50ms tail latency, custom SLA, and dedicated support.
Capabilities & data
Free
Read-only catalog access for evaluation. Capped to product + category browsing.
$199.00/mo
Full catalog + commerce access for production B2B integrations. REST + MCP for AI agent workflows.
$999.00/mo
High-volume access with direct Apollo Router for sub-50ms tail latency, custom SLA, and dedicated support.
Release timeline · stable
Each release freezes the contract — SLOs, permissions, exposed entities. Yanked versions are excluded; deprecated versions surface their sunset deadline.
| Version | Status | Released | Sunset | Notes |
|---|---|---|---|---|
| v1.0.0current | Released | May 31, 2026 | — | — |
Ask this DataProduct
Every entity, every field, every sensitivity flag — straight from the provider's published version. No PDF, no spreadsheet, no email exchange.
Domain · catalog
A product brand or manufacturer. Groups products by their source company.
Context·Brands are the primary organizational unit for product catalogs. Combined with MPN (Manufacturer Part Number), a Brand uniquely identifies a product across systems.
| Field | Business meaning | Sensitivity | Shape | Example |
|---|---|---|---|---|
| name | Official brand or manufacturer name. | INTERNAL | DESCRIPTIVE | Acme |
| logoUrl | URL to the brand logo image. | PUBLIC | OTHER | https://cdn.example.com/brands/acme/logo.svg |
Other entities this product references. Use them as breadcrumbs when you map the product against your own data model.
| Relationship | Target entity | Cardinality | Description |
|---|---|---|---|
| manufactures | Product | many | All products manufactured by this brand. |
Domain · catalog
A hierarchical product classification. Categories form a tree structure for organizing products.
Context·Categories are the taxonomy layer of the catalog. They can be nested (parent-child) to form deep hierarchies like "Electronics > Sensors > Temperature". Products can belong to multiple categories. Categories often mirror an industry-standard classification (e.g. ECLASS, ETIM, GS1, UNSPSC, TecDoc article groups, GMDN/UDI).
| Field | Business meaning | Sensitivity | Shape | Example |
|---|---|---|---|---|
| name | Category name at this level of the hierarchy. | INTERNAL | DESCRIPTIVE | Sensors |
| path | Materialized path showing the full hierarchy from root to this category, separated by " > ". | INTERNAL | OTHER | Electronics > Sensors > Temperature |
| parentId | ID of the parent category. Null for root-level categories. | INTERNAL | RELATIONAL | 019314c2-7e2e-7c91-9a7d-4b6e5e9b1a23 |
Other entities this product references. Use them as breadcrumbs when you map the product against your own data model.
| Relationship | Target entity | Cardinality | Description |
|---|---|---|---|
| parent_of | Category | many | Child categories nested under this category. |
| contains | Product | many | Products classified under this category. |
Domain · commerce
A B2B customer account with contact info, credit terms, and purchase history.
Context·Customers are the buyer side of the business. They place orders, receive invoices, own assets, and can be assigned to sales reps. Credit limits and payment terms govern B2B trade.
| Field | Business meaning | Sensitivity | Shape | Example |
|---|---|---|---|---|
| customerNumber | Provider-assigned customer identifier. | INTERNAL | IDENTIFIER | CUST-10042 |
| companyName | Legal company name. | INTERNAL | DESCRIPTIVE | Acme GmbH |
| type | Customer classification. | INTERNAL | DESCRIPTIVE | COMPANY |
| status | Account status. | INTERNAL | DESCRIPTIVE | ACTIVE |
| paymentTermsDays | Net payment terms in days (e.g. 30 = Net 30). | INTERNAL | TEMPORAL | 30 |
| creditLimit | Maximum outstanding credit allowed. | INTERNAL | TRANSACTIONAL | 25000.00 |
| creditUsed | Current outstanding credit amount. | INTERNAL | TRANSACTIONAL | 4820.00 |
| totalSpent | Lifetime purchase total. | INTERNAL | TRANSACTIONAL | 128450.75 |
Other entities this product references. Use them as breadcrumbs when you map the product against your own data model.
| Relationship | Target entity | Cardinality | Description |
|---|---|---|---|
| places | Order | many | Orders placed by this customer. |
| owns | Asset | many | Assets (machines, vehicles, devices, units) owned or operated by the customer. |
| billed_via | Invoice | many | Invoices issued to this customer. |
Domain · commerce
A sales order with line items, fulfillment tracking, and payment status.
Context·Orders are the core transaction entity. They link customers to products, track fulfillment (picking, shipping, delivery), and drive invoicing. Order status progression: PENDING → CONFIRMED → PROCESSING → SHIPPED → DELIVERED.
| Field | Business meaning | Sensitivity | Shape | Example |
|---|---|---|---|---|
| orderNumber | Human-readable order reference number. | INTERNAL | IDENTIFIER | ORD-2025-08742 |
| status | Order lifecycle status. | INTERNAL | DESCRIPTIVE | PROCESSING |
| fulfillmentStatus | Physical fulfillment progress. | INTERNAL | DESCRIPTIVE | PARTIALLY_FULFILLED |
| paymentStatus | Payment collection status. | INTERNAL | DESCRIPTIVE | PAID |
| totalAmount | Total order value including tax. | INTERNAL | TRANSACTIONAL | 1487.50 |
| currency | ISO 4217 currency code. | INTERNAL | TRANSACTIONAL | EUR |
| customerReference | Customer-provided PO or reference number. | INTERNAL | IDENTIFIER | PO-4711-AC |
| trackingCode | Shipping tracking number. | INTERNAL | IDENTIFIER | 1Z999AA10123456784 |
Other entities this product references. Use them as breadcrumbs when you map the product against your own data model.
| Relationship | Target entity | Cardinality | Description |
|---|---|---|---|
| placed_by | Customer | one | The customer who placed this order. |
| contains | Product | many | Products ordered (via OrderItem line items). |
Domain · catalog
A physical or digital product in the catalog with pricing, stock levels, and (where applicable) compatibility metadata.
Context·Core entity for any product-centric business. Products belong to a Brand, are organized in Categories, and have StockLevels across Warehouses. They can be linked to Assets via compatibility relationships and to other products via cross-references (equivalents, replacements, OE/aftermarket pairs in the relevant industries).
| Field | Business meaning | Sensitivity | Shape | Example |
|---|---|---|---|---|
| sku | Stock Keeping Unit -- the provider's internal product identifier. Unique within an organization. | INTERNAL | IDENTIFIER | WIDGET-001 |
| ean | European Article Number (EAN-13 or EAN-8) -- a globally unique barcode identifier. | INTERNAL | IDENTIFIER | 4006381333931 |
| mpn | Manufacturer Part Number -- the identifier assigned by the brand/manufacturer. | INTERNAL | IDENTIFIER | P 85 020 |
| partNumber | Generic part number field for additional numbering schemes beyond SKU, EAN, and MPN. | INTERNAL | IDENTIFIER | PN-A12-3456 |
| name | Human-readable product name or title. | INTERNAL | DESCRIPTIVE | Industrial Sensor Module, 24V, IP67 |
| description | Free-text product description. May contain technical specifications, application notes, or marketing text. | INTERNAL | DESCRIPTIVE | Industrial-grade temperature sensor module with 24V DC supply, IP67 housing, and 4–20 mA analog output. |
| priceNet | Net price (excluding tax) in the currency specified by the currency field. | INTERNAL | TRANSACTIONAL | 149.00 |
| currency | ISO 4217 currency code for the price. | INTERNAL | TRANSACTIONAL | EUR |
| taxRate | Tax rate as a decimal fraction (e.g. 0.19 for 19% German VAT). | INTERNAL | TRANSACTIONAL | 0.19 |
| weightKg | Product weight in kilograms. | INTERNAL | OTHER | 0.85 |
| hasVariants | Whether this product has size/color/specification variants. | INTERNAL | OTHER | false |
| status | Product lifecycle status: DRAFT (not visible), ACTIVE (available), DISCONTINUED (no longer sold), ARCHIVED (hidden). | INTERNAL | DESCRIPTIVE | ACTIVE |
| crossReferences | Links to equivalent, superseding, or compatible products from other brands. | INTERNAL | OTHER | [{"type":"EQUIVALENT","relatedProductId":"019314c2-..."}] |
Other entities this product references. Use them as breadcrumbs when you map the product against your own data model.
| Relationship | Target entity | Cardinality | Description |
|---|---|---|---|
| manufactured_by | Brand | one | The brand/manufacturer of this product. |
| categorized_in | Category | many | Product categories (hierarchical). A product can belong to multiple categories. |
| stocked_at | StockLevel | many | Stock quantities across warehouses. |
| cross_referenced_with | ProductCrossReference | many | Equivalent, superseding, or original-match products from other brands. |
| compatible_with | Asset | many | Assets (machines, equipment, vehicles, devices, buildings) this product is compatible with. |
Domain · logistics
A logistics shipment containing one or more items in transit.
Context·Shipments connect orders, carriers, tracking numbers, waypoints, delivery proof, and fulfillment events.
| Field | Business meaning | Sensitivity | Shape | Example |
|---|---|---|---|---|
| shipmentNumber | Human-readable shipment identifier. | INTERNAL | IDENTIFIER | — |
| status | Shipment lifecycle state. | INTERNAL | DESCRIPTIVE | — |
| trackingNumber | Carrier tracking identifier. | INTERNAL | IDENTIFIER | — |
| shippedAt | Timestamp when shipment left origin. | INTERNAL | TEMPORAL | — |
| deliveredAt | Timestamp when delivery completed. | INTERNAL | TEMPORAL | — |
Domain · inventory
A physical storage location where products are stocked.
Context·Warehouses are the inventory nodes. Each product can have stock across multiple warehouses. One warehouse is typically marked as default for order fulfillment.
| Field | Business meaning | Sensitivity | Shape | Example |
|---|---|---|---|---|
| name | Warehouse name or code. | INTERNAL | DESCRIPTIVE | Main Warehouse |
| status | Operational status. | INTERNAL | DESCRIPTIVE | ACTIVE |
| isDefault | Whether this is the primary fulfillment warehouse. | INTERNAL | OTHER | true |
| capacityM3 | Total storage capacity in cubic meters. | INTERNAL | OTHER | 12500 |
Other entities this product references. Use them as breadcrumbs when you map the product against your own data model.
| Relationship | Target entity | Cardinality | Description |
|---|---|---|---|
| stores | StockLevel | many | Stock levels for products in this warehouse. |
Care signals
Anything tagged RESTRICTED or above must be referenced by an explicit plan permission to be exposed.
Domain · commerce
fields tagged RESTRICTED or above — exposed only via explicit plan permissions; names withheld here.
AI integration
Cursor, Claude, and any MCP-aware client can query this catalog over the public MCP server. The same field-level truth shown above — entities, sensitivities, example queries — is served programmatically. No extra setup, no API key.
https://meshbase.ai/mcpLive chat
Ask in plain English — what's in here, what's sensitive, how a query might look. Answers come from what the provider published. The chat refuses to invent the rest.
Try one of these
Need more volume or different terms?
Higher limits, dedicated support, vertical-specific permissions on top of the tiers above. We connect you with the provider's commercial team and stay on the contract.