Recommended Types of Resources
[Mandatory for Graduation] This document outlines the recommended resources that should be exposed for common fund-transfer related use cases.
Design Principles
Position IDs are mandatory Any system involving positions (perps, options, prediction markets) should expose a consistent
positionIdacross active and historical endpoints.Timestamp Readability To improve readability, the timestamp like
2025-01-13T11:05:44Zshould be converted to13 Jan 2025, 11:05 UTChuman readable timestamps with explicit timezone.Numeric identifiers for chain id (e.g. 8453) are opaque to users without prior context. Agent team should either:
Document the list of chain id for
chainInandchainOutin field description ORExpose chain registry resource that maps chain IDs to human-readable network information.
History is as important as state Agents without historical context tend to hallucinate intent or repeat failed strategies.
Validation endpoints reduce failures Lightweight checks such as
is_token_tradabledramatically reduce execution errors.
Use Case Quick References:
Spot Trading
get_token_balance
get_trade_history
supported_token_list
get_market_price
Perpetual (Perp) Trading
get_active_positions
get_historical_positions
get_position_margin
is_token_tradable
get_funding_rate (optional)
Same Chain/ Cross Chain Swap Agent (DEX / Aggregator)
Shared Resources (Swap + Cross-Chain Swap)
is_token_tradable
get_token_balance
get_swap_quote
get_swap_history
get_token_balance
Cross-Chain–Specific Resources
get_cross_chain_routes (Cross-Chain Only)
get_pending_transfers (Cross-Chain Only)
Options Trading
get_active_positions (options positions)
get_historical_positions
get_option_chain
get_expiry_schedule
get_greeks (optional)
Returns option sensitivity metrics for a specific contract. Supports delta-neutral or volatility-based strategies.
Prediction Markets
get_active_positions (open bets)
get_historical_positions (resolved bets)
get_market_status
is_market_open
get_market_odds (optional)
Last updated