Curator API

Deploy idle vault funds to underlying yield strategies

POST /api/curator

Deploys idle vault funds to their respective yield strategies. The curator checks the vault’s idle WBTC balance and executes the appropriate deployment strategy.

Request Body

vaultId · string · required

Vault identifier. Supported values:

• sentinel - Deploy to Vesu lending
• citadel - Stake to Endur
• trident - Execute staking loop (3 iterations)
• delta_neutral - Deploy collateral for delta-neutral position
• turbo - Deploy to Vesu
• apex - Deploy with split strategy

Response

status · string

Deployment status: deployed or no_idle_funds

tx · string

Transaction hash (only if deployed)

amount · string

Amount deployed in WBTC sats (only if deployed)

error · string

Error message if request failed

Example Request

cURL

curl -X POST https://sable.money/api/curator \
  -H "Content-Type: application/json" \
  -d '{"vaultId": "sentinel"}'

Example Response

{
  "status": "deployed",
  "tx": "0x1234...",
  "amount": "500000000"
}

Strategy Mapping

Each vault has a specific deployment strategy:

Vault	Contract Method	Description
sentinel	deploy_to_vesu	Supply WBTC to Vesu Prime lending pool
citadel	stake_to_endur	Stake WBTC to Endur Finance
trident	execute_staking_loop	Execute 3-iteration leverage staking loop
delta_neutral	deploy_collateral	Deploy as collateral for neutral position
turbo	deploy_to_vesu	Supply to Vesu with optimization
apex	deploy_split	Split deployment across multiple protocols

Implementation Details

Source: /home/daytona/workspace/source/src/app/api/curator/route.ts:18

The curator:

1. Checks vault’s WBTC balance using balanceOf
2. Skips deployment if idle balance is 0
3. Executes vault-specific deployment method
4. Waits for transaction confirmation
5. Returns transaction hash and deployed amount

This endpoint requires server-side authentication with curator private key. It is called automatically by the Sable protocol when vaults have idle funds.