Skip to main content
POST
Create a MicroVault
Create a vault and its ERC-20 share token. The response contains a task that tracks deployment.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Idempotency-Key
string
required

Unique key for this intended change. Reuse it only when retrying the identical request.

Required string length: 1 - 200

Body

application/json
baseAsset
string
required

Token accepted for subscriptions and paid out on redemptions. Use the base-asset address from an available yield source on the vault's chain.

Required string length: 42
Pattern: ^0x(?!0{40}$)[0-9a-fA-F]{40}$
Example:

"0x3bf25a73a1f1033c2d50ac65f3c9d6a44123db81"

name
string
required

Full ERC-20 share-token name shown in wallets and block explorers.

Required string length: 1 - 64
symbol
string
required

Short ERC-20 ticker for the MicroVault shares, such as acmeUSDC.

Required string length: 1 - 16
feeRecipient
string
required

Wallet or contract that receives newly minted shares when management or performance fees accrue.

Required string length: 42
Pattern: ^0x(?!0{40}$)[0-9a-fA-F]{40}$
Example:

"0x3bf25a73a1f1033c2d50ac65f3c9d6a44123db81"

managementFeeBps
integer
required

Annual management fee in basis points. 100 means 1%; use 0 for no management fee.

Required range: 0 <= x <= 9999
performanceFeeBps
integer
required

Fee on gains above the vault's high-water NAV in basis points. 1000 means 10%; use 0 for no performance fee.

Required range: 0 <= x <= 9999

Response

The operation was accepted.

task
object
required

Asynchronous change accepted for submission and onchain confirmation.

Example: