Core Products / Guide

API and MCP Products

Use API and MCP products to expose governed operational context to approved applications, copilots, BI, and enterprise systems.

Context that reaches your applications01 / SYSTEM VIEW
EquipmentHistoryDocuments
TwinEdgeShared asset context
Digital twinsAI agentsApps + APIs
01Define02Connect03Authorize04Consume
The application receives a clear contract and traceable source context.
Before you start

Application teams, data platform owners, AI teams, and integration partners.

  • A published DataOps product or validated operational context.
  • A known consumer application, agent, dashboard, or integration.
  • Approved authentication, permission scope, and rate expectations.
  • A test plan for read-only access before production use.
THE WORKFLOW

Move through the connected record.

  1. 01

    Define the product contract

    Document what context the consumer needs, which tenant and role scope applies, and which output shape is stable.

  2. 02

    Publish from DataOps

    Use the API/MCP workspace to expose the selected data product, catalog entry, profile, or tool surface.

  3. 03

    Test with governed access

    Validate authentication, permissions, response shape, pagination, freshness, and audit behavior with a non-production client first.

  4. 04

    Monitor consumers

    Watch run status, errors, usage, and product health so changes do not silently break consuming systems.

CONTINUE IN TWINEDGE

Open your workspace.

Sign in with your TwinEdge account to access your enabled modules.

EXPLORE THE NEXT CONNECTION

Continue the workflow.

IMPLEMENTATION GUIDANCE

Build it around your operation.

Request API enablement when a customer application or agent needs tenant-scoped access.

Talk to TwinEdge