Released · May 31, 2026
Normalised machine-tool telemetry across 35+ controller dialects (Siemens, Heidenhain, Fanuc, Mitsubishi). OEE breakdowns, spindle/axis health, programme/tool consumption, and energy per part — one signed contract.
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.
$249.00/mo
14-day free trialOEE breakdowns + tool/programme consumption for a single site.
Capabilities & data
$799.00/mo
14-day free trialMulti-site fleet, spindle/axis health, MCP + natural-language query for production engineers.
Capabilities & data
$1,999.00/mo
30-day free trialDirect router for sub-30s shopfloor signals, custom OEE definitions, dedicated success engineering.
Capabilities & data
$249.00/mo
OEE breakdowns + tool/programme consumption for a single site.
$799.00/mo
Multi-site fleet, spindle/axis health, MCP + natural-language query for production engineers.
$1,999.00/mo
Direct router for sub-30s shopfloor signals, custom OEE definitions, dedicated success engineering.
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 · asset
A universal asset entity representing any physical thing that can be tracked, maintained, and linked to compatible products.
Context·Assets are the equipment side of the data model. The same model serves machinery on a shop floor, vehicles in a fleet, units in a building, devices in the field, and instruments in a lab. Assets are linked to Products via compatibility relationships, enabling "what fits this asset?" queries, and to Customers via ownership relationships.
| Field | Business meaning | Sensitivity | Shape | Example |
|---|---|---|---|---|
| name | Human-readable name or model designation of the asset. | INTERNAL | DESCRIPTIVE | CNC Mill XR-200 |
| manufacturer | The manufacturer or make of the asset. | INTERNAL | DESCRIPTIVE | Siemens |
| serialNumber | Manufacturer-assigned serial number that identifies a specific physical unit. | INTERNAL | IDENTIFIER | SN-987654321 |
| modelNumber | Model or type designation assigned by the manufacturer. | INTERNAL | IDENTIFIER | XR-200 |
| yearProduced | Year the asset was manufactured or produced. | INTERNAL | OTHER | 2019 |
| externalIds | Open key/value map of industry- or system-specific identifiers attached to the asset (e.g. registry numbers, regulator IDs, third-party reference numbers). | INTERNAL | IDENTIFIER | {"vin":"WAUZZZ8K1AA123456","epc":"DE-0010-XYZ"} |
| status | Current operational status of the asset. | INTERNAL | DESCRIPTIVE | ACTIVE |
| condition | Physical condition assessment of the asset. | INTERNAL | DESCRIPTIVE | GOOD |
Other entities this product references. Use them as breadcrumbs when you map the product against your own data model.
| Relationship | Target entity | Cardinality | Description |
|---|---|---|---|
| compatible_with | Product | many | Products (parts, consumables, accessories) that are compatible with this asset. |
| owned_by | Customer | many | Customers who own or operate this asset. |
| parent_of | Asset | many | Child assets in the hierarchy (e.g. components of a machine, units in a building, sub-systems in a vehicle). |
| located_at | Location | one | Physical location of the asset. |
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 · event
A scheduled event (conference, webinar, workshop, training) with capacity and registration.
Context·Events are time-bound activities that may have physical locations, capacity limits, and public/private visibility.
| Field | Business meaning | Sensitivity | Shape | Example |
|---|---|---|---|---|
| name | Event title. | INTERNAL | DESCRIPTIVE | Industry Data Mesh Summit 2025 |
| slug | URL-friendly identifier. | INTERNAL | IDENTIFIER | data-mesh-summit-2025 |
| type | Event classification. | INTERNAL | DESCRIPTIVE | CONFERENCE |
| status | Event lifecycle. | INTERNAL | DESCRIPTIVE | PUBLISHED |
| format | Delivery format. | INTERNAL | TEMPORAL | HYBRID |
| startDate | Event start date/time. | INTERNAL | TEMPORAL | 2025-09-12T09:00:00Z |
| endDate | Event end date/time. | INTERNAL | TEMPORAL | 2025-09-13T17:00:00Z |
| capacity | Maximum number of attendees. | INTERNAL | OTHER | 250 |
| isPublic | Whether the event is publicly listed. | INTERNAL | OTHER | true |
Other entities this product references. Use them as breadcrumbs when you map the product against your own data model.
| Relationship | Target entity | Cardinality | Description |
|---|---|---|---|
| held_at | Location | one | Physical venue. |
Domain · events
An attendee registration for an event or session.
Context·Registrations connect guests or customers to event attendance, ticket status, and check-in workflows.
| Field | Business meaning | Sensitivity | Shape | Example |
|---|---|---|---|---|
| status | Registration lifecycle state. | INTERNAL | DESCRIPTIVE | — |
| registeredAt | Timestamp when registration was created. | INTERNAL | TEMPORAL | — |
| checkedInAt | Optional check-in timestamp. | INTERNAL | TEMPORAL | — |
| ticketCode | Ticket or registration code. | INTERNAL | IDENTIFIER | — |
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 · service
A sellable or operational service offered by an organization.
Context·Services are service-domain catalog items that can be priced, scheduled, bundled, quoted, or attached to requirements.
| Field | Business meaning | Sensitivity | Shape | Example |
|---|---|---|---|---|
| name | Service display name. | PUBLIC | DESCRIPTIVE | — |
| description | Customer-facing service description. | PUBLIC | DESCRIPTIVE | — |
| status | Lifecycle state controlling availability. | INTERNAL | DESCRIPTIVE | — |
| basePrice | Default service price when configured. | PUBLIC | TRANSACTIONAL | — |
Domain · foundation
A tenant-defined label that can be attached to many different entity types.
Context·Tags provide lightweight cross-domain classification without changing the underlying model schema.
| Field | Business meaning | Sensitivity | Shape | Example |
|---|---|---|---|---|
| name | Display label for the tag. | PUBLIC | DESCRIPTIVE | — |
| slug | URL-safe tenant-local tag identifier. | PUBLIC | IDENTIFIER | — |
| color | Optional UI color for tag badges. | PUBLIC | DESCRIPTIVE | — |
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.