Operate is the operator control plane for SuperVaults. Its APIs split by operational responsibility.Documentation Index
Fetch the complete documentation index at: https://docs.superform.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Services
| Service | Owns | Docs |
|---|---|---|
| Erebor | Vault reads, settings, registries, merkle config, upkeep, users, pause controls | Erebor API |
| Strategy Engine | Strategy lifecycle, ordering, live shards, intent projections, emergency locks | Strategy API |
| OMS | DeFiX intent execution, events, session-key readiness, hook transactions | OMS API |
| Public merkle artifact | Published proof data for keepers and integrators | Merkle Publishing |
Auth
Authenticated endpoints use Dynamic-issued bearer JWTs:Prepare, Sign, Confirm
Most protocol mutations follow this model:- API prepares calldata.
- Wallet signs and submits the transaction.
- API / indexer reads resulting state or confirms a transaction hash.
Vault Identity and Listing State
A vault can be:- Created onchain.
- Indexed in Erebor.
- Active / discoverable after upkeep is funded.
- Listed and available in the Superform catalog.
Strategy Execution Flow
- Operator configures hooks and publishes merkle authorization.
- Operator whitelists yield sources and pairs oracles.
- Operator creates and orders strategies.
- Strategy Engine evaluates rules and submits DeFiX intents.
- OMS validates authorization and executes hook transactions.
- Events and fills flow back into intent history.