Tools

Direct tool invocation without LLM overhead — structured input/output

List all available DeFi tools with schemas

get

Returns a machine-readable catalog of every direct-invocation tool: names, descriptions, parameter schemas, categories, and access requirements.

Autonomous agents should call this endpoint first to discover what operations are available and what arguments each tool expects. The response includes full JSON-Schema parameter definitions compatible with OpenAI function calling.

Price: $0.002 USDC per request (x402, eip155:8453)

Authorizations
X-PaymentstringRequired

x402 payment header. Flow:

  1. Make the request without this header → receive 402 Payment Required and, for protected routes, a PAYMENT-REQUIRED header describing accepted payment requirements
  2. Create the x402 payment payload for USDC on Base (chain 8453), typically via @x402/core and the CDP facilitator at api.cdp.coinbase.com
  3. Retry the request with this header set to the encoded payment payload

Successful 2xx responses may include a PAYMENT-RESPONSE settlement receipt. See https://github.com/rigoblock/agentic-operator/blob/main/AGENTS.md for full integration.

Responses
chevron-right
200

Tool catalog with full schemas

application/json
descriptionstringRequired
usagestringRequiredExample: POST /api/tools/{toolName}
pricestringRequiredExample: $0.002 USDC per call (x402 exact scheme, eip155:8453)
toolCountintegerRequired

Total number of tools in the catalog

get
/api/tools

Invoke a DeFi tool directly

post

Direct tool invocation without LLM overhead. Useful when you know exactly which operation to perform and want structured input/output without natural language parsing. Each call is atomic.

Discover schemas first: Call GET /api/tools to retrieve the full catalog with parameter schemas for every tool.

Price: $0.002 USDC per request (x402, eip155:8453)

Read-only tools: get_swap_quote, get_vault_info, get_token_balance, get_pool_info, get_lp_positions, gmx_get_positions, gmx_get_markets, check_delegation_status, get_crosschain_quote, get_aggregated_nav, get_rebalance_plan, verify_bridge_arrival, list_twap_orders, list_nav_syncs, list_strategies, switch_chain

State-changing tools: build_vault_swap, add_liquidity, remove_liquidity, collect_lp_fees, burn_position, gmx_open_position, gmx_close_position, gmx_increase_position, gmx_cancel_order, gmx_update_order, gmx_claim_funding_fees, crosschain_transfer, crosschain_sync, grg_stake, grg_unstake, grg_undelegate_stake, grg_end_epoch, grg_claim_rewards, deploy_smart_pool, fund_pool, create_twap_order, cancel_twap_order, create_nav_sync, cancel_nav_sync

Operator-scoped tools (require operatorVerified): setup_delegation, revoke_delegation, revoke_selectors, list_strategies, set_default_slippage, disable_swap_shield, enable_swap_shield

Oracle tools: refresh_oracle_feed

Orchestration pattern: External agents compose atomic operations from this endpoint into multi-step strategies. Each call returns either a result (reads) or unsigned calldata (writes). The full safety stack (NAV shield, Swap Shield, slippage protection) applies to all write operations.

Authorizations
X-PaymentstringRequired

x402 payment header. Flow:

  1. Make the request without this header → receive 402 Payment Required and, for protected routes, a PAYMENT-REQUIRED header describing accepted payment requirements
  2. Create the x402 payment payload for USDC on Base (chain 8453), typically via @x402/core and the CDP facilitator at api.cdp.coinbase.com
  3. Retry the request with this header set to the encoded payment payload

Successful 2xx responses may include a PAYMENT-RESPONSE settlement receipt. See https://github.com/rigoblock/agentic-operator/blob/main/AGENTS.md for full integration.

Path parameters
toolNamestring · enumRequired

Tool name to invoke

Example: get_swap_quotePossible values:
Body
chainIdinteger · enumOptional

EVM chain ID

Default: 8453Possible values:
vaultAddressstringOptional

Rigoblock vault address (required for vault-specific tools)

Example: 0xYourVaultAddress
operatorAddressstringOptional

Vault owner address (required for vault-action tools in delegated mode)

Example: 0xOperatorWallet
authSignaturestringOptional

EIP-191 signature by operatorAddress over the auth message (required for vault-action tools)

Example: 0x...
authTimestampintegerOptional

Unix timestamp (ms) when authSignature was created. Valid for 24 hours.

Example: 1741700000000
Responses
chevron-right
200

Tool result

application/json
toolstringOptional

Canonical tool name that handled the request

messagestringOptional

Human-readable tool result

transactionobjectOptional

Unsigned transaction payload for state-changing tools

chainSwitchintegerOptional

Suggested chain switch, when the tool resolved to a different chain

suggestionsstring[]Optional
post
/api/tools/{toolName}

Last updated