sorin-skill

name	sorin-skill
description	Use when the user asks crypto-related questions about a token, pool, chain, protocol, or project and the agent should answer with Sorin's DeFi gateway using clear, data-backed analysis.

Sorin Skill

Purpose

When the user asks crypto-related questions, identify intent first, call the most relevant API from the gateway, and return concise analysis with data-backed conclusions.

Gateway

• Base URL: https://tools.saharaai.com/api
• API key env var: DEFI_TOOLS_API_KEY
• Auth header: Authorization: Bearer ${DEFI_TOOLS_API_KEY}
• Accept header: accept: text/plain

Default request template:

curl -X 'GET' \
  'https://tools.saharaai.com/api/<path>?<query>' \
  -H 'accept: text/plain' \
  -H "Authorization: Bearer ${DEFI_TOOLS_API_KEY}"

Pool analysis example:

curl -X 'GET' \
  'https://tools.saharaai.com/api/pool/analysis?chain=Ethereum' \
  -H 'accept: text/plain' \
  -H "Authorization: Bearer ${DEFI_TOOLS_API_KEY}"

Intention Routing

1. Detect user intention from natural language.
2. Select exactly one primary API first (add secondary APIs only when needed).
3. Validate required inputs. If missing, ask only the minimum follow-up question.
4. Call API and parse success, data, error.

Intention -> API Mapping

1) Token fundamentals / price / holders / technicals

• API: tokenTool
• Use when: user asks token market analysis (macro liquidity + micro market structure).
• Input:
  • token_symbol (required): token symbol, e.g. BTC, ETH
  • quote_currency (optional, default USDT): quote currency for the pair
• curl:

curl -X 'GET' \
  'https://tools.saharaai.com/api/token/analysis?token_symbol=ETH&quote_currency=USDT' \
  -H 'accept: text/plain' \
  -H "Authorization: Bearer ${DEFI_TOOLS_API_KEY}"

2) Yield/staking pool discovery and scoring

• API: poolTool
• Use when: user asks where to stake, best APY pools, pool comparison, TVL/APY trends.
• Input (all optional filters):
  • chain (optional): chain id string, e.g. 1, 56
  • project (optional): project slug, e.g. lido, aave-v3
  • protocol (e.g. lido, aave-v3)
  • token_symbol (e.g. ETH, USDC)
  • pool_id (optional): unique pool identifier
  • pool_category (optional): pool category filter
• curl:

curl -X 'GET' \
  'https://tools.saharaai.com/api/pool/analysis?chain=Ethereum&protocol=lido&token_symbol=ETH' \
  -H 'accept: text/plain' \
  -H "Authorization: Bearer ${DEFI_TOOLS_API_KEY}"

3) Chain-level DEX and TVL landscape

• API: chainTool
• Use when: user asks chain DEX volume trends, TVL changes, protocol dominance on a chain.
• Input (optional, provide one when possible):
  • chainId (integer): chain id, e.g. 1
  • chainName (string): chain name, e.g. Ethereum
• curl:

curl -X 'GET' \
  'https://tools.saharaai.com/api/chain/analysis?chainName=Ethereum' \
  -H 'accept: text/plain' \
  -H "Authorization: Bearer ${DEFI_TOOLS_API_KEY}"

4) Protocol-level financial analysis

• API: protocolTool
• Use when: user asks protocol TVL/fees/revenue/capital flow and comprehensive metrics.
• curl:

curl -X 'GET' \
  'https://tools.saharaai.com/api/protocol/analysis?protocol=aave' \
  -H 'accept: text/plain' \
  -H "Authorization: Bearer ${DEFI_TOOLS_API_KEY}"

5) Prediction market and project outlook

• API: projectTool
• Use when: user asks project odds, FDV expectations, short/long-term target prices, market sentiment for a project.
• Input:
  • projectName (required): project name, e.g. berachain
• curl:

curl -X 'GET' \
  'https://tools.saharaai.com/api/project/analysis?projectName=berachain' \
  -H 'accept: text/plain' \
  -H "Authorization: Bearer ${DEFI_TOOLS_API_KEY}"

Output Style for End Users

Use this response structure:

1. What I queried: API name and key parameters.
2. Key findings: 3-5 bullets with metrics.
3. Interpretation: trend/risk/opportunity in plain language.
4. Actionable next step: one concrete follow-up.
5. Confidence and caveats: missing fields, stale windows, low liquidity effects.

Decision Heuristics

• If question is asset-specific, start with tokenTool.
• If question is yield-focused, start with poolTool.
• If question is chain ecosystem-focused, use chainTool.
• If question is protocol financial health-focused, use protocolTool.
• If question is project narrative or valuation-focused, use projectTool.

Safety Rules

• Never invent prices, holders, APY, TVL, or tx outcomes.
• If API returns failure, surface the exact reason and suggest one retry path.
• Ask follow-up questions only for missing required parameters.
• Keep chain IDs explicit when ambiguity exists.