The engine and its API run at the venue and act only as the venue’s party. Register keepers, price sources and investors act on their own systems; see Who runs what.
Your systems drive NodeAsset through one REST API, and hear back through its event feed and webhooks. NodeAsset writes to Canton as your party; every other party signs its own part on its own node.

​
What you build against

​
The other parties

Each other party acts from its own node: the register keeper on its DA registry, the price source from its NAV system, and the investor’s custodian in its wallet. NodeAsset holds none of their keys and reads what they sign. You build against NodeAsset’s API, and each guide names the other parties’ steps under the same Tx numbers as yours. What each party runs and signs is on Who runs what.

Quickstart

From your deployment to a settled subscription in about ten minutes.

Guides

The calls behind each workflow, step by step.

Connect your systems

The NAV feed, oracles, KYC and screening.

Build a client

Generate a client in your language from the OpenAPI document.