How do I install the Sushiswap API skill?

Run npx skillmds@latest add dvcrn/sushiswap-api in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sushiswap API safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sushiswap API?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sushiswap API free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sushiswap API?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sushiswap API by dvcrn — Agent Skill

Name: Sushiswap API
Rating: 4.2 (5 reviews)
Author: dvcrn

Sushiswap 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)

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

SushiSwap REST API Integration

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.

Base URL

https://api.sushi.com

API Schema

The active API schema is defined in:

references/openapi.yaml

Agents must always rely on the schema contents rather than hardcoded assumptions.

How To Use

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

Mandatory `referrer` Parameter

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.

Fee Customization

The SushiSwap API supports customized integrator fees on swap-related endpoints (e.g. /quote & /swap).

Default fee model

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

Custom fee splits

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.

Error Handling

422: Request parameters are invalid → fix inputs
529: Server overloaded → retry with backoff
500: Internal error → retry or fail gracefully

Schema Guidance

For schema usage rules and update behavior, see:

references/OPENAPI.md

---name: sushiswap-apidescription: 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)---# SushiSwap REST API IntegrationThe 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.---## Base URL```https://api.sushi.com```---## API SchemaThe **active API schema** is defined in:[references/openapi.yaml](references/openapi.yaml)Agents must **always rely on the schema contents** rather than hardcoded assumptions.---## How To Use1. Load `references/openapi.yaml`2. Discover available endpoints, parameters, and response shapes dynamically3. 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}`)4. Construct requests that strictly conform to the schema and include a valid `referrer` parameter for all quote and swap endpoints5. Validate required parameters before execution---## Mandatory `referrer` Parameter- 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.---## Fee CustomizationThe SushiSwap API supports customized integrator fees on swap-related endpoints (e.g. `/quote` & `/swap`).### Default fee model- 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### Custom fee splits- 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 SushiSwapteam rather than attempting to modify request parameters.---## Error Handling- `422`: Request parameters are invalid → fix inputs- `529`: Server overloaded → retry with backoff- `500`: Internal error → retry or fail gracefully---## Schema GuidanceFor schema usage rules and update behavior, see:[references/OPENAPI.md](references/OPENAPI.md)

Frequently asked questions