Every hub, one API
A single versioned API with scoped keys gives integrators one thing to learn.
Connect any application: a public API, events, webhooks, connectors, MCP and a data workbench.
AI gives every hub a ready-made public API with scoped keys, documented events and signed webhooks, plus a data integration module with connectors, pipelines and an on-premises agent. Tools that speak the Model Context Protocol can read and prepare work as a signed-in person. Nothing an integration does can exceed the rights of the key or person behind it.
A single versioned API with scoped keys gives integrators one thing to learn.
Documented events and signed webhooks replace polling.
Design, test and monitor pipelines in one workspace with lineage.
An on-premises agent reads local data without opening inbound ports.
MCP clients inherit a person's rights and cannot approve.
Search or filter. Planned items are labelled; everything else is available now.
One versioned REST gateway over a shared catalogue of business objects.
14 featuresKnow when something changes, without polling.
7 featuresBuild against AI from your own tools.
7 featuresPublish your own endpoints without writing a server.
5 featuresMove data in and out with a visual designer and a library of connectors.
20 featuresLet approved AI tools work inside AI as a person.
5 featuresReach people where they work.
3 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to Integration.
Publishing custom endpoints, certifying datasets and changing database objects can route through workflow approval.
Usage per key and delivery logs are visible to admins, and run history feeds monitoring.
Datasets
Dashboards
This page is the integration module itself; each hub shows its own Integration sub-hub.
/v1 with several hundred named resources; coverage differs by hub
Events
Connectors
Connector packs from the migration module reuse the same engine.
Not applicable; admin screens are desktop first.
Yes, through one gateway. Coverage differs: some hubs are fully readable and most writable, others are thinner and widening.
No. Approvals, rejections and similar decisions are person-only.
Subscribe to documented events by webhook, or poll the change feed.
Yes, with the on-premises agent.
Yes, over MCP with a person's authorisation, limited to that person's rights.
A TypeScript SDK and a command-line tool exist; other languages are planned.
Yes, from a saved report or a validated workflow action, versioned and tested before publish.