Skip to main content
Partner integration guide draft · English v1.0 · 13 October 2026 Docs Home Distribution OS is Arco’s Vault API for integrating RWA and digital asset strategy vaults into partner applications. Distribution OS and Arco Vault API are two names for the same product: the former describes the product, and the latter describes its integration interface. Arco supplies the vault products. Partners connect selected products to their own services, bringing product information, participation procedures, transactions and holdings into their customer experience. The product serves companies such as wallets, fintech platforms, exchanges and institutional applications; these examples describe intended partner types.

​
Two vault families

Distribution OS connects Arco-supplied products. A product name, underlying asset listing or technically callable contract does not establish that the product is enabled for a particular partner or customer. Use the selected product’s terms and integration scope to determine access.

​
Integrating into a partner service

The partner chooses which approved products to present and builds the customer experience around product information, participation checks, transaction authorization, processing status and holdings. Arco’s vault structure connects those activities to the product’s assets, strategy, pricing and settlement. A common interface reduces repeated integration work across products. Product-specific eligibility, signing, asset representation, valuation and liquidity conditions still apply. API authentication identifies or authorizes an API caller; it does not itself approve a customer’s investment or authorize spending their assets.

​
Follow the integration guide

The eight topics below connect the product introduction to the existing product and technical guides. Shared topics remain at their established URLs.

​
Technical implementation references

Integration Guide and Developer Quickstart contain the existing EVM source implementation references and examples. They explain specific public-code behavior; they are not an operating Distribution OS API contract or evidence of production availability. Use the selected product and environment’s supplied integration specification for actual requests, authentication, transaction execution and completion evidence. This guide describes the integration concepts without assigning REST paths, SDK methods or API status values to them.