BlockHelix API — v1 draft

This is a preview of the trading API we are building on Base. Nothing below is live yet — endpoints, schemas, and auth are subject to change until the testnet release. Join the waitlist on the homepage to get access first.

How it works

Vaults are non-custodial ERC-4626 contracts. Operators trade through this API, but every execution is checked on-chain against a merkle-authorized policy — token pairs, venues, slippage, and per-tx caps are all leaf-constrained. Depositors see policy changes 24 hours before they execute. Auth is a wallet signature; no signup.

1) Create a vault

POST /v1/vaults
{
  "asset": "USDC",
  "template": "bluechip",
  "operator": "0xYourWallet",
  "managementFeeBps": 100,
  "performanceFeeBps": 1000
}

Templates: bluechip · all-yield · balanced · midcap-momentum · perps-midcap (v2) · custom (post-launch).

2) Trade

POST /v1/vaults/:id/trade/swap
Content-Type: application/json
Authorization: Bearer <api-key bound to operator wallet>

{
  "tokenIn":  "USDC",
  "tokenOut": "WETH",
  "amount":   "5000000000",
  "maxSlippageBps": 50
}

// 200 { "orderId": "...", "status": "queued" }
// 403 if no matching leaf in the vault's merkle policy

Planned endpoints

POST /v1/vaultsCreate a vault from a policy template (root set at launch)

POST /v1/vaults/:id/trade/swapSpot swap via CoW Protocol, slippage-capped by policy

POST /v1/vaults/:id/yield/depositDeposit into a whitelisted yield source (Morpho, Aave v3)

POST /v1/vaults/:id/yield/withdrawWithdraw from a yield source

GET /v1/vaults/:id/positionsLive positions and NAV breakdown

GET /v1/vaults/:id/policyActive merkle leaf set, human-readable

POST /v1/vaults/:id/configsPropose a policy change (24h timelock)

MCP for agents

An MCP server exposing vault creation, policy configuration, and trading as tools will ship with the testnet release, so AI agents can operate vaults end-to-end. The legacy Solana runtime and its MCP endpoint are frozen.