Skip to main content
Operate is the operator control plane for SuperVaults. Its APIs split by operational responsibility.

​
Services

​
Auth

SuperformOS uses same-origin BFF routes with browser-session and vault-role checks. The server supplies the appropriate upstream authentication; a single curator JWT is not a credential for every service. The reference pages list upstream paths, not self-service headless access. Public reads are route-specific. For authenticated automation, agree the endpoint, identity, scope, and rate policy with the Superform team. See Authentication.

​
Prepare, Sign, Confirm

Onchain configuration changes use this model:
  1. API prepares calldata.
  2. Wallet signs and submits the transaction.
  3. API / indexer reads resulting state or confirms a transaction hash.
Do not treat a successful prepare request as a completed setting change. Offchain strategy saves and service settings can apply without a wallet signature; read back their state separately.

​
Vault Identity and Listing State

A vault can be:
  • Created onchain.
  • Indexed in Erebor.
  • Active / discoverable under the current upkeep and exemption policy.
  • Visible and available in Superform distribution surfaces.
Those are related but separate states. The dashboard setup flow tracks them together so operators do not route users into a half-configured vault.

​
Strategy Execution Flow

  1. Operator whitelists yield sources and pairs oracles.
  2. Operator configures hooks, executes the authorized root update after its timelock, and publishes the proof artifacts.
  3. Operator creates and orders strategies.
  4. Strategy Engine evaluates rules and submits DeFiX intents.
  5. OMS validates authorization and executes hook transactions.
  6. Events and fills flow back into intent history.

​
API Reference Pages