Prices and oracles
| Integration | How it plugs in |
|---|---|
| The administrator’s NAV feed | The price source signs each NAV on its own node. Its feed, by API or by file, adds an expiry and a kill switch: an expired NAV, a pulled switch, or a NAV that disagrees with the ledger holds the asset until two approvers release it. |
| CAPS price capsules | The price source can publish its NAV as a CAPS capsule it derives itself, through an adapter the deployment adds behind the Oracle interface. The same capsules share the fund’s NAV with lenders and distributors, each reading only its own. |
| Chainlink, RedStone and Kaiko | A provider’s NAV, posted by a connector of the deployment’s own to a nav source, is checked against the price source’s: an independent check that never prices an order. The options are compared on Price source and oracles. |
The asset’s own price source stays the authority for the price an order settles at. Outside data adds checks and reach; it never overrides that signature. See Price the asset.
KYC and compliance
| Integration | How it plugs in |
|---|---|
| Your own KYC | KYC stays with you. Its results (residency, investor type, accreditation, each with an expiry) become eligibility claims on the investor’s credential. No personal data reaches the ledger. |
| KYC providers | A provider’s verification webhook issues a claim, or expires it. |
| Sanctions and AML screening | A screening hit freezes the investor at once; two approvers lift the freeze. |
Identity and operations
| Integration | How it plugs in |
|---|---|
| Identity provider | Staff and investors sign in through your OIDC provider; their roles come from its tokens. |
| Monitoring | Health and metrics for your monitoring stack, signed webhooks for control events, and an ordered event feed. |