Nansen

Category: Market data · signals

Nansen exposes read-only Hyperliquid cohort and market-structure intel through Thirdfy provider nansen. Agents call get_nansen_* on the Thirdfy catalog. These actions do not place perps orders.

Pair Nansen evidence with Hyperliquid for execution.

Actions

Params use JSON bodies. Screener and profiler calls are not EVM chainId filters. Profiler PnL uses date.from / date.to as YYYY-MM-DD.

Premium research costs more than screener and profiler reads. Command shows the USD charge after the turn. See Credits and balance.

The public catalog does not include smart-money tape, leaderboards, or address labels. Synthesized answers include Powered by Nansen API where Nansen requires attribution.

Signals

get_nansen_perp_screener publishes one signal in the signal manifest (app nansen, manifest version 1). The tables come from the production catalog (api.thirdfy.com).

• Typed read. The screener returns typed.rows[], one row per Hyperliquid market, with parsed numbers. Nothing is derived: the buy and sell imbalance is left to the reader.
• Values are not for display. Nansen's app sets displayValues: false. Use the values in decisions, and show users only the outcome, such as "passed" or "vetoed", with "Powered by Nansen API".
• The other Nansen reads are listed in the manifest with no signals yet.

Signal fields

Credential model

Nansen reads use the same Thirdfy session as other catalog actions. CLI and MCP do not take a Nansen key. Thirdfy credits pay the catalog action.

Discovery

curl "https://api.thirdfy.com/api/v1/agent/actions/catalog"
thirdfy-agent actions --provider nansen --json

Use it

Ask your agent:

Using Thirdfy, show the top 3 Hyperliquid perps on Nansen's screener for the last day, with buy/sell pressure and funding.

Or call it yourself:

agentRun { action: "get_nansen_perp_screener", params: {"date": {"from": "2026-10-07T00:00:00.000Z", "to": "2026-10-08T00:00:00.000Z"}, "pagination": {"page": 1, "per_page": 3}} }

thirdfy-agent run --action get_nansen_perp_screener --provider nansen \
  --params '{"date":{"from":"2026-10-07T00:00:00.000Z","to":"2026-10-08T00:00:00.000Z"},"pagination":{"page":1,"per_page":3}}' --json

curl -s -X POST https://mcp.thirdfy.com/tool/agentRun \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $AGENT_API_KEY" \
  -d '{"action":"get_nansen_perp_screener","params":{"date":{"from":"2026-10-07T00:00:00.000Z","to":"2026-10-08T00:00:00.000Z"},"pagination":{"page":1,"per_page":3}}}'

Trimmed result from a real read on 2026-10-08:

{
  "typed": {
    "rows": [
      {
        "symbol": "xyz:XYZ100",
        "volumeUsd": 181587123.1,
        "buySellPressureUsd": 19224733.95,
        "traderCount": 1681,
        "markPriceUsd": 31082,
        "fundingRate": 6.25e-06,
        "openInterestUsd": 268499134.22
      }
    ]
  },
  "parseIssues": [],
  "freshness": {
    "fetchedAt": "2026-10-08T14:24:49Z",
    "cacheHit": false
  },
  "attribution": "Powered by Nansen API"
}

What to check: parseIssues is empty before you use a field from typed. buySellPressureUsd above zero means takers bought more than they sold in the window.

Readiness checklist

• Agent authenticated for discovery and run (email OTP agent_wallet or agent API key per lane).
• Strategy treats Nansen output as advisory evidence.
• For live perps, run Hyperliquid setup, funding, and preflight before any order.

Execution lanes

Nansen actions are read-only and fanoutSafe. They do not require delegation binding for research reads. Any execute-intent on Hyperliquid still requires normal preflight and delegation rules.

Related

• Signals and market data
• Hyperliquid
• MCP discovery
• Actions reference