The OMS implements the DeFiX intent execution path. The Strategy Engine publishes intents; OMS validates authorization, builds execution, submits hook transactions, and emits lifecycle events / fills back to operators. Base URL: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.
https://oms.superform.xyz
Auth: Authorization: Bearer <jwt>
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:| State | Meaning |
|---|---|
RECEIVED | OMS received the intent |
ACKED | Intent accepted for processing |
STAGED | Intent staged for planning/execution |
PLANNED | Route or execution plan built |
EXECUTING | Transaction execution in progress |
COMPLETED | Execution completed |
ABORTED | OMS aborted before success |
EXPIRED | Intent expired before execution |
FAILED | Execution failed |
CANCELED | Intent cancelled before terminal execution |
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:| Mode | Meaning |
|---|---|
OMS | OMS-managed delegated signer path |
EIP4337 | ERC-4337 user operation path |
EIP4337_COMPANION | Companion 4337 path |
EIP7702 | EIP-7702 account path |
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.
Endpoint Inventory
| Endpoint | Method | Description |
|---|---|---|
/defix/intents | POST | Submit intent |
/defix/intents/{intent_id} | GET | Current intent state |
/defix/intents/{intent_id}/cancel | POST | Cancel non-terminal intent |
/defix/intents/{intent_id}/events | GET | Intent event log |
/defix/vaults/{vault_id}/session-key/readiness | GET | Session-key readiness |
/defix/vaults/{vault_id}/session-key/grant | GET | Prepare grant calldata |
/defix/vaults/{vault_id}/session-key/rotation | GET | Prepare rotation calldata |
/defix/vaults/{vault_id}/session-key/rotation/complete | POST | Complete rotation |
/defix/vaults/{vault_id}/session-key/rotation/cancel | POST | Cancel pending rotation |
/defix/vaults/{vault_id}/session-key/revoke | GET | Prepare revoke calldata |
