Começar agora

API e servidor MCP

A triagem diária, como API

Esta referência está em inglês. A navegação e os rótulos estão traduzidos.

Yield Sniper screens the DeFi yield universe once a day against published risk rules. The API returns the result as JSON: every instrument with its yield, liquidity, safety score and verdict, the daily screen, the published reports and the methodology. The MCP server gives the same data to AI assistants.

What you get

  • Instruments. Lending markets, vaults and staking pools, passed and failed. A failed instrument carries the first hard rule it failed, so you can see why it was excluded.
  • Screens and reports. The outcome of each day: what was screened, what passed, failures by rule, and the published selection of up to 5 instruments per asset class.
  • Methodology. The rules, signals and bands behind every score, as data.
  • Your saved queries and watchlists, shared with the Explorer.

Queries use the same language as the Explorer: apy >= 6.5 and band = low and class = stablecoin works in the app, in GET /instruments?q= and in the MCP tool screen_instruments.

Requisição
curl https://yieldsniper.finance/api/v1/screens/latest \
  -H "Authorization: Bearer $YS_API_KEY"
Resposta200
{
  "object": "screen",
  "id": "scr_2026-10-23",
  "date": "2026-10-23",
  "as_of": "2026-10-23T23:45:21.116Z",
  "universe": {
    "instruments": 15948,
    "protocols": 503,
    "chains": 105,
    "tvl": 152788660398
  },
  "outcome": {
    "passed": 131,
    "failed": 15817,
    "pass_rate": 0.008214,
    "in_report": 12
  },
  "failures_by_rule": [
    {
      "rule": "tvl_floor",
      "count": 15655
    },
    {
      "rule": "out_of_scope",
      "count": 88
    },
    {
      "rule": "apy_floor",
      "count": 62
    },
    {
      "rule": "unaudited_small",
      "count": 7
    },
    {
      "rule": "exit_blocked",
      "count": 2
    },
    {
      "rule": "recent_incident",
      "count": 2
    },
    {
      "rule": "score_floor",
      "count": 1
    }
  ],
  "leaders": [
    {
      "asset_class": "stablecoin",
      "total_apy": 8.13962,
      "instrument_id": "ins_f3cbaa85fd31098b"
    },
    {
      "asset_class": "bitcoin",
      "total_apy": 1.73072,
      "instrument_id": "ins_7f329ae62bbbf561"
    },
    {
      "asset_class": "ether",
      "total_apy": 3.6921,
      "instrument_id": "ins_e84a5c279e1c69c8"
    }
  ],
  "methodology_version": "3.0"
}

Data freshness

The data is a daily snapshot, not a live feed. Every response is served from the latest screen stored on our side; no request triggers a live call to a data source. Two calls on the same day return the same values.

  • Every object has as_of, the time of the screen it comes from, and every response sends the Yield-Sniper-As-Of header.
  • The screen runs once a day, at about 07:30 New York time (schedule in GET /methodology). The actual time of each screen is its as_of.
  • Responses carry an ETag. Send it back in If-None-Match and you get a 304 with no body until the next screen.
The values come from on-chain data and independent data providers, checked and scored by our rules. They are research, not financial advice, and not a basis for trading within the day.
Response headers
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Yield-Sniper-As-Of: 2026-10-23T23:45:21.116Z
ETag: "VVzbh_ReUWWmU3lOurOO-Hwh3GM"
Cache-Control: private, max-age=60
RateLimit-Limit: 60
RateLimit-Remaining: 59
RateLimit-Reset: 35
X-Request-Id: req_6a4d68dd5ebded01b90a161f

Base URL and conventions

All endpoints live under https://yieldsniper.finance/api/v1, over HTTPS, with JSON in and out.

  • Keys are snake_case. Objects carry object and a prefixed id: ins_, prt_, scr_, rpt_, sq_, wl_.
  • Rates are annualised percent: 6.72786 is 6.73%. Changes are percentage points (*_pp). Shares and concentrations are ratios from 0 to 1.
  • Money is USD as a plain number. Times are ISO 8601 in UTC; dates are YYYY-MM-DD.
  • Lists are paginated with limit and next_cursor, and report the real total.
Exemplo200
{
  "yield": {
    "total_apy": 6.72786,
    "change_7d_pp": 0.04312,
    "incentive_share": 0
  },
  "liquidity": {
    "tvl": 92211394,
    "top10_concentration": 0.8919
  },
  "safety": {
    "protocol_age_days": 414
  },
  "as_of": "2026-10-23T23:45:21.116Z"
}

Versioning

The version is part of the path: /api/v1. Within v1 we only add things: endpoints, optional parameters, fields and enum values. Write clients that ignore fields they don't know and handle enum values they haven't seen.

A breaking change ships under a new path (/api/v2) while v1 keeps working, and is announced in the changelog first.

Access

API keys and the MCP server are included with paid plans. Signed-in free accounts can call the API from the browser session and get preview rows: real totals and up to 5 rows, with passing instruments shown without their identity. GET /methodology, GET /stats and GET /openapi.json are public.

CallerInstrumentsDetail, history, reportsKeys and MCP
No key, signed out401401—
Free accountPreview rows402402
Paid account or keyFullFullYes