https://erebor.superform.xyz
Auth: Authorization: Bearer <jwt> except public endpoints
For onchain changes, Erebor prepares calldata and the manager wallet signs the transaction. The REST request is not the state change; the signed transaction is.
Auth
Vaults and Public Discovery
Vault detail includes onchain identity, managers, fees, PPS, balances, TVL, upkeep information, activation state, and allocation data when available. Authenticated list responses may include
activation; public vault responses include upkeep_info and activation when Erebor can compute them.
Public discovery depends on more than deployment. Erebor only surfaces vaults with known activation when activation.is_discoverable is true. If activation is unknown because a subgraph dependency is unavailable, the vault can still be returned with activation unset rather than treated as deleted.
Vault Creation
ConfirmCreateVaultRequest can include vault_config.redeem_timelock_seconds for post-indexing settings.
Distribution metadata is handled by the dashboard/listing layer after vault address resolution. Onchain creation and Superform availability are separate states.
Settings and Upkeep
Upkeep data drives activation and discoverability in the dashboard. Operators should treat insufficient upkeep as a launch blocker.
Current upkeep responses use:
Merkle Authorization
Registry
Yield source registry entries include active/inactive state and can carry external provider metadata. Registry create, update, delete, and sync endpoints are registry-maintainer surfaces, not normal third-party operator flows.
Yield Source Whitelist
Users and Permissions
Session Keys
OMS owns additional readiness and rotation endpoints for strategy automation.
Notification Channels
Providers include Slack, webhook, and websocket channels.
