https://oms.superform.xyz
Access: The paths below are an upstream service inventory. SuperformOS reaches OMS through its session- and role-checked BFF, which supplies server-side service authentication. Direct integrations require explicit onboarding; these are not curator bearer-JWT endpoints. See Authentication.
In normal dashboard operations, managers do not submit intents directly. They configure strategies and monitor the resulting intent history.
Intent Lifecycle
OMS intent state is explicit and event-driven:
Terminal states cannot be modified.
Submit Intent
vault_idstrategy_idactionobjectiveaction_configauth- merkle proof / root data
- account mode (
OMS,EIP4337,EIP4337_COMPANION, orEIP7702)
Get Intent
completed_at may be null before terminal execution.
Cancel Intent
Intent Events
event_idintent_idexecution_idmessage_typeseq_num- event-specific
payload created_at
Fills and Mined Transactions
Fills represent confirmed onchain execution evidence. In the operator UI, fills may include:tx_hashchain_idamount_inamount_outtoken_intoken_outvenuegas_used- mined / fill timestamp
null gas or missing fill fields until the transaction is mined and backfilled.
Hook Transactions and Account Modes
OMS supports native hook transaction execution and smart-account/user-operation modes. Account mode controls how execution is signed and submitted:
The hook transaction adapter handles execution against SuperVault hooks once session-key and merkle authorization are valid.
Session Keys
Strategy automation requires a valid session key for the vault.Readiness
Grant
Rotate / Renew
Revoke
Session-key endpoints return transaction data for wallet signing. They do not bypass onchain permission checks.
