Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
REST API for optimized token swapping (including executable transaction generation), swap quoting, and pricing using the SushiSwap Aggregator. Use this skill when the user wants to: - Get a swap quote between two tokens on 40+ evm networks - Generate executable swap transaction data - Fetch token prices for a specific network or token - Retrieve token metadata - Discover supported AMM liquidity sources - Integrate SushiSwap swapping or pricing logic via HTTP/REST (and not the SushiSwap Javascript API)
REST API for optimized token swapping (including executable transaction generation), swap quoting, and pricing using the SushiSwap Aggregator. Use this skill when the user wants to: - Get a swap quote between two tokens on 40+ evm networks - Generate executable swap transaction data - Fetch token prices for a specific network or token - Retrieve token metadata - Discover supported AMM liquidity sources - Integrate SushiSwap swapping or pricing logic via HTTP/REST (and not the SushiSwap Javascript API)
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
The SushiSwap API provides HTTP access to the SushiSwap Aggregator for optimized token swaps, price discovery, and transaction generation. It aggregates liquidity from multiple DEXs to determine the best execution route.
https://api.sushi.com
The active API schema is defined in: references/openapi.yaml Agents must always rely on the schema contents rather than hardcoded assumptions.
Load references/openapi.yaml Discover available endpoints, parameters, and response shapes dynamically Select the appropriate endpoint based on user intent and schema tags Quotes โ quote endpoints (e.g. /quote/v7/{chainId}) Swap execution โ swap endpoints (e.g. /swap/v7/{chainId}) Prices โ price endpoints (e.g. /price/v1/{chainId}) Token info โ token endpoints (e.g. /token/v1/{chainId}/{tokenAddress}) Construct requests that strictly conform to the schema and include a valid referrer parameter for all quote and swap endpoints Validate required parameters before execution
The referrer parameter must be specified on swap-related endpoints (e.g. /quote & /swap) The agent or integrator must identify themselves using this field /quote or /swap requests must not be sent without a referrer value Agents must never attempt to omit, spoof, or auto-generate this value.
The SushiSwap API supports customized integrator fees on swap-related endpoints (e.g. /quote & /swap).
Swap-related requests follow an 80/20 fee split by default 80% to the integrator (referrer) 20% to SushiSwap This split applies unless explicitly overridden by SushiSwap
Alternative fee splits require a partnership with SushiSwap Agents and integrators should not assume custom splits are available. If users request alternative fee splits, agents should direct them to the SushiSwap team rather than attempting to modify request parameters.
422: Request parameters are invalid โ fix inputs 529: Server overloaded โ retry with backoff 500: Internal error โ retry or fail gracefully
For schema usage rules and update behavior, see: references/OPENAPI.md
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.