Adapter registry model, supported protocol actions, and extension workflow.
Each integrated protocol has a dedicated adapter.
jupiter for swap, limit-order, dca, route-plan
jupiter
swap
limit-order
dca
route-plan
pyth for price-feed, historical-price, price-update
pyth
price-feed
historical-price
price-update
marinade for stake, unstake, liquid-stake, msol-price
marinade
stake
unstake
liquid-stake
msol-price
orca for swap, open-position, close-position, whirlpool-info
orca
open-position
close-position
whirlpool-info
kamino for deposit, withdraw, rebalance, vault-info
kamino
deposit
withdraw
rebalance
vault-info
drift for deposit, withdraw, open-perp, close-perp, spot-trade
drift
open-perp
close-perp
spot-trade
raydium for swap, add-liquidity, remove-liquidity, farm-stake
raydium
add-liquidity
remove-liquidity
farm-stake
helius for get-transactions, get-assets, webhook-create, rpc-call
helius
get-transactions
get-assets
webhook-create
rpc-call
jito for send-bundle, tip-account, bundle-status
jito
send-bundle
tip-account
bundle-status
squads for create-multisig, propose-tx, approve-tx, execute-tx
squads
create-multisig
propose-tx
approve-tx
execute-tx
Each adapter maps protocol-specific actions into a consistent platform response model.
This allows users to work with different protocols through a more standardized interface.
The adapter model keeps protocol-specific logic isolated while preserving a standard execution surface.
Last updated 3 hours ago