API and MCP Products
Use API and MCP products to expose governed operational context to approved applications, copilots, BI, and enterprise systems.
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.
Move through the connected record.
- 01
Define the product contract
Document what context the consumer needs, which tenant and role scope applies, and which output shape is stable.
- 02
Publish from DataOps
Use the API/MCP workspace to expose the selected data product, catalog entry, profile, or tool surface.
- 03
Test with governed access
Validate authentication, permissions, response shape, pagination, freshness, and audit behavior with a non-production client first.
- 04
Monitor consumers
Watch run status, errors, usage, and product health so changes do not silently break consuming systems.
Open your workspace.
Sign in with your TwinEdge account to access your enabled modules.
DataOps API/MCP Workspace
Publish and manage data products.
Open in appProduct System
Product system operations.
Open in appProduct Catalog
Catalog entries and published products.
Open in appDataOps Monitor
Health and usage checks.
Open in appDeveloper Portal
Administrative developer access where enabled.
Open in appContinue the workflow.
Build it around your operation.
Request API enablement when a customer application or agent needs tenant-scoped access.