nansen-cli 1.46.0 → 2.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (78) hide show
  1. package/CHANGELOG.md +122 -0
  2. package/README.md +157 -14
  3. package/docs/browser-login.md +123 -0
  4. package/package.json +11 -2
  5. package/scripts/postinstall.js +35 -30
  6. package/skills/nansen-agent-guide/SKILL.md +13 -2
  7. package/skills/nansen-alerts-webhook-listener/SKILL.md +5 -2
  8. package/skills/nansen-dca-tracker/SKILL.md +10 -2
  9. package/skills/nansen-defi-positions/SKILL.md +5 -2
  10. package/skills/nansen-exit-signals/SKILL.md +10 -2
  11. package/skills/nansen-fund-tracker/SKILL.md +10 -2
  12. package/skills/nansen-general-search/SKILL.md +10 -2
  13. package/skills/nansen-holder-analysis/SKILL.md +10 -2
  14. package/skills/nansen-limit-orders/SKILL.md +6 -3
  15. package/skills/nansen-perp-screener/SKILL.md +10 -2
  16. package/skills/nansen-perp-trader-profile/SKILL.md +10 -2
  17. package/skills/nansen-polymarket-deep-dive/SKILL.md +10 -2
  18. package/skills/nansen-polymarket-insider-scan/SKILL.md +10 -2
  19. package/skills/nansen-polymarket-trader-profile/SKILL.md +10 -2
  20. package/skills/nansen-portfolio-tracker/SKILL.md +10 -2
  21. package/skills/nansen-prediction-markets/SKILL.md +10 -2
  22. package/skills/nansen-sm-cross-chain-flows/SKILL.md +10 -2
  23. package/skills/nansen-smart-alerts/SKILL.md +9 -4
  24. package/skills/nansen-smart-money-alpha/SKILL.md +10 -2
  25. package/skills/nansen-smart-money-tracker/SKILL.md +10 -2
  26. package/skills/nansen-smart-money-trend/SKILL.md +10 -2
  27. package/skills/nansen-token-research/SKILL.md +10 -2
  28. package/skills/nansen-token-screener/SKILL.md +14 -4
  29. package/skills/nansen-token-transfer-analysis/SKILL.md +10 -2
  30. package/skills/nansen-trading/SKILL.md +8 -2
  31. package/skills/nansen-wallet-batch/SKILL.md +10 -2
  32. package/skills/nansen-wallet-clustering/SKILL.md +10 -2
  33. package/skills/nansen-wallet-deep-dive/SKILL.md +10 -2
  34. package/skills/nansen-wallet-keychain-migration/SKILL.md +5 -2
  35. package/skills/nansen-wallet-manager/SKILL.md +11 -9
  36. package/skills/nansen-wallet-profiler/SKILL.md +10 -2
  37. package/skills/nansen-web-fetcher/SKILL.md +5 -2
  38. package/skills/nansen-web-searcher/SKILL.md +5 -2
  39. package/src/api.js +202 -104
  40. package/src/auth-browser.js +16 -0
  41. package/src/auth-credentials.js +73 -0
  42. package/src/auth-device.js +242 -0
  43. package/src/auth-key-input.js +46 -0
  44. package/src/auth-login.js +89 -0
  45. package/src/auth-state.js +487 -0
  46. package/src/auth-store-native.js +20 -0
  47. package/src/auth-store-worker.js +64 -0
  48. package/src/auth-store.js +140 -0
  49. package/src/auto-paginate.js +288 -0
  50. package/src/bridge.js +126 -21
  51. package/src/cache-inspect.js +345 -0
  52. package/src/cli.js +473 -199
  53. package/src/commands/agent.js +15 -7
  54. package/src/commands/completion.js +2 -15
  55. package/src/commands/mcp.js +20 -18
  56. package/src/cost-cache.js +16 -2
  57. package/src/debug.js +348 -0
  58. package/src/doctor.js +22 -45
  59. package/src/hl-action.js +41 -13
  60. package/src/limit-order.js +1 -1
  61. package/src/mcp-client-config.js +169 -0
  62. package/src/mcp-client-config.json +17 -0
  63. package/src/mcp-verify.js +6 -5
  64. package/src/perp.js +41 -0
  65. package/src/privy.js +12 -12
  66. package/src/response-meta.js +56 -1
  67. package/src/rpc-urls.js +9 -11
  68. package/src/schema.json +185 -8
  69. package/src/semver.js +23 -4
  70. package/src/swap-simulation.js +35 -30
  71. package/src/telemetry.js +20 -0
  72. package/src/trading.js +266 -29
  73. package/src/transfer.js +53 -6
  74. package/src/update-check.js +9 -1
  75. package/src/wallet.js +107 -17
  76. package/src/walletconnect-trading.js +24 -5
  77. package/src/x402-svm.js +123 -64
  78. package/src/x402.js +46 -14
@@ -5,7 +5,7 @@
5
5
  *
6
6
  * Runs after `npm install -g nansen-cli` and offers two optional steps:
7
7
  * 1. Install the Nansen AI coding skill (`npx skills add nansen-ai/nansen-cli`)
8
- * 2. Check account status to verify the API key works (0 credits)
8
+ * 2. Check account status to verify the effective credential (0 credits)
9
9
  *
10
10
  * Non-interactive environments (CI, piped stdin) get a one-liner tip instead.
11
11
  * Always exits 0 — onboarding failures must never break installation.
@@ -13,7 +13,7 @@
13
13
 
14
14
  import { createInterface } from "readline";
15
15
  import { execFileSync, spawn } from "child_process";
16
- import { existsSync, readFileSync } from "fs";
16
+ import { existsSync, realpathSync } from "fs";
17
17
  import { join, dirname } from "path";
18
18
  import { fileURLToPath } from "url";
19
19
 
@@ -60,18 +60,6 @@ function hasNpx() {
60
60
  }
61
61
  }
62
62
 
63
- function isLoggedIn() {
64
- const home = process.env.HOME || process.env.USERPROFILE || "";
65
- const configFile = join(home, ".nansen", "config.json");
66
- if (!existsSync(configFile)) return false;
67
- try {
68
- const config = JSON.parse(readFileSync(configFile, "utf8"));
69
- return !!(config.apiKey || config.api_key);
70
- } catch {
71
- return false;
72
- }
73
- }
74
-
75
63
  function isSkillInstalled() {
76
64
  const home = process.env.HOME || process.env.USERPROFILE || "";
77
65
  const locations = [
@@ -115,9 +103,9 @@ async function installSkill() {
115
103
 
116
104
  log(`The Nansen skill lets AI coding agents (Cursor, Claude Code, etc.) query`);
117
105
  log(`on-chain data, track smart money, analyze tokens, and use nansen trade.`);
118
- const answer = await prompt(` Install Nansen skill for your AI coding agent? [Y/n] `);
106
+ const answer = await prompt(` Install Nansen skill for your AI coding agent? [y/N] `);
119
107
 
120
- if (/^n/i.test(answer)) {
108
+ if (!/^y(es)?$/i.test(answer)) {
121
109
  log(`Skipped. You can install it later with: ${CYAN}npx skills add ${SKILL_REPO}${RESET}`);
122
110
  return;
123
111
  }
@@ -130,20 +118,31 @@ async function installSkill() {
130
118
  }
131
119
 
132
120
  async function testQuery() {
133
- if (!isLoggedIn()) {
121
+ // Selection reads metadata only. Never open storage or verify during install.
122
+ let selection;
123
+ try {
124
+ const { resolveCredential, assertUsableSelection } = await import("../src/auth-credentials.js");
125
+ selection = resolveCredential();
126
+ assertUsableSelection(selection);
127
+ } catch {
128
+ log(`Saved or selected authentication needs attention. Run: nansen auth status`);
129
+ return;
130
+ }
131
+ if (selection.kind === "anonymous") {
134
132
  log();
135
- log(`Not logged in yet. Run ${CYAN}nansen login --human${RESET} to authenticate.`);
136
- log(`Get your API key at: ${CYAN}https://app.nansen.ai/auth/agent-setup${RESET}`);
133
+ log(`Run ${CYAN}nansen login${RESET} for browser approval, or use NANSEN_API_KEY directly.`);
134
+ log(`Browser login is enabled in production; saved sessions need a supported OS credential store. See docs/browser-login.md in this package.`);
137
135
  return;
138
136
  }
139
137
 
140
138
  log();
141
- log(`Your API key is configured. Let's verify it works.`);
142
- const answer = await prompt(` Check account status? (${DIM}${TEST_QUERY_DISPLAY}${RESET}) [Y/n] `);
139
+ log(selection.kind === "session"
140
+ ? `A browser session is configured; cached metadata is unverified and storage has not been checked.`
141
+ : `An API key is configured; it has not been verified.`);
142
+ const answer = await prompt(` Check account status? (${DIM}${TEST_QUERY_DISPLAY}${RESET}, free; may renew a session) [y/N] `);
143
143
 
144
- if (/^n/i.test(answer)) {
145
- log(`Skipped. You're all set! Try: ${CYAN}nansen research smart-money netflow --chain solana${RESET}`);
146
- log(`For trading: ${CYAN}nansen trade quote --chain solana --from SOL --to USDC --amount 1000000000${RESET}`);
144
+ if (!/^y(es)?$/i.test(answer)) {
145
+ log(`Skipped account verification. Run ${CYAN}nansen account${RESET} when ready.`);
147
146
  return;
148
147
  }
149
148
 
@@ -156,11 +155,11 @@ async function testQuery() {
156
155
  log(`${GREEN}✓${RESET} All set! Run ${CYAN}nansen help${RESET} to see all available commands.`);
157
156
  } else {
158
157
  log();
159
- log(`${YELLOW}Query failed. Check your API key with: nansen auth status${RESET}`);
158
+ log(`${YELLOW}Account check failed. Inspect the effective credential with: nansen auth status${RESET}`);
160
159
  }
161
160
  }
162
161
 
163
- async function main() {
162
+ export async function main() {
164
163
  // Only run for global installs; skip local npm install / npm ci
165
164
  if (process.env.npm_lifecycle_event === "postinstall" && process.env.npm_config_global !== "true") {
166
165
  return;
@@ -172,7 +171,7 @@ async function main() {
172
171
  log(`${BOLD}Nansen CLI installed!${RESET}`);
173
172
  log();
174
173
  log(`Tip: Run '${CYAN}npx skills add ${SKILL_REPO}${RESET}' to install the Nansen AI coding skill.`);
175
- log(`Tip: Run '${CYAN}nansen login --human${RESET}' to authenticate.`);
174
+ log(`Tip: Run '${CYAN}nansen login${RESET}' for browser approval, or use NANSEN_API_KEY directly.`);
176
175
  log(`Tip: To trade, first create a wallet with '${CYAN}nansen wallet create${RESET}', then quote with '${CYAN}nansen trade quote --chain solana --from SOL --to USDC --amount 1000000000${RESET}' and execute with '${CYAN}nansen trade execute --quote <id>${RESET}'.`);
177
176
  return;
178
177
  }
@@ -186,6 +185,12 @@ async function main() {
186
185
  log();
187
186
  }
188
187
 
189
- main().catch(() => {
190
- // Never fail installation due to onboarding errors
191
- });
188
+ // Node resolves the module URL through symlinks, but argv may retain them.
189
+ // An unavailable entry path or onboarding failure must never fail installation.
190
+ try {
191
+ if (process.argv[1] && realpathSync(process.argv[1]) === realpathSync(fileURLToPath(import.meta.url))) {
192
+ main().catch(() => {});
193
+ }
194
+ } catch {
195
+ // Importing with a missing/non-file argv entry remains silent.
196
+ }
@@ -4,8 +4,6 @@ description: Routing guide -- when to use `nansen agent` (AI research) vs direct
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -15,9 +13,16 @@ metadata:
15
13
  bins: [nansen]
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
16
+ ## Authentication
17
+
18
+ Nansen account API calls accept a selected `nansen:api` browser session or conventional API key with the same permissions. `NANSEN_API_KEY` takes precedence; optional `primaryEnv` preserves configured-key injection. Run `nansen auth status` for offline selection. Cached access expiry alone permits automatic renewal during an authorized task. Stop on anonymous selection, invalid state, blocked/uncertain renewal or actual auth failure; never drop a credential or fall back to anonymous x402 payment. Browser login does not grant wallet signing, privileged service identity or a persistent MCP integration key. Preserve all confirmation, signing, sanctions and geographic checks below. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
19
+
20
+
18
21
 
19
22
  # Agent vs CLI Routing
20
23
 
24
+ Public agent fast/expert and direct API commands accept the selected nansen:api browser session or conventional API key under the same account permissions.
25
+
21
26
  | Need a... | Use |
22
27
  |-----------|-----|
23
28
  | **take** (analysis, interpretation) | `nansen agent` |
@@ -56,3 +61,9 @@ Cost: 5-50 credits per call
56
61
  - Don't use `nansen agent` for simple data fetches -- 40x more expensive
57
62
  - Don't use raw CLI for open-ended analysis -- returns data, not interpretation
58
63
  - Don't chain 3+ agent calls -- get raw data via CLI, call agent once for synthesis
64
+
65
+ ## Browser session scope
66
+
67
+ Plain `nansen login` requests fresh browser approval; `--no-browser` prints the link/code for approval on another device and keeps the same native-storage requirements. NANSEN_API_KEY overrides the single saved credential. Use `nansen auth status` for offline cached/unverified selection details and `nansen account` for a free live check. Explicit `login --human` or `login --api-key` retains legacy key setup. Selected browser sessions renew automatically; uncertain renewal requires fresh login without replay or fallback to another account/payment.
68
+
69
+ Browser nansen:api grants have API-key-equivalent account permissions, subject to enabled admission and the same endpoint restrictions. Internal service identity and wallet signing are not granted. Browser sessions cannot authorize wallet signing or be exported as MCP keys. CLI 2.0.0 is published; the preview platform limits above still apply.
@@ -4,8 +4,6 @@ description: Set up a local webhook server to receive Nansen smart alerts in rea
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  - node
@@ -16,6 +14,11 @@ metadata:
16
14
  bins: [nansen]
17
15
  allowed-tools: Bash(nansen:*), Bash(node:*), Bash(npx:*), Bash(ngrok:*), Write
18
16
  ---
17
+ ## Authentication
18
+
19
+ Nansen account API calls accept a selected `nansen:api` browser session or conventional API key with the same permissions. `NANSEN_API_KEY` takes precedence; optional `primaryEnv` preserves configured-key injection. Run `nansen auth status` for offline selection. Cached access expiry alone permits automatic renewal during an authorized task. Stop on anonymous selection, invalid state, blocked/uncertain renewal or actual auth failure; never drop a credential or fall back to anonymous x402 payment. Browser login does not grant wallet signing, privileged service identity or a persistent MCP integration key. Preserve all confirmation, signing, sanctions and geographic checks below. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
20
+
21
+
19
22
 
20
23
  # Alert Webhook Listener
21
24
 
@@ -4,8 +4,6 @@ description: "What tokens are whales dollar-cost averaging into? Jupiter DCA str
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -16,6 +14,16 @@ metadata:
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
18
16
 
17
+ ## Authentication
18
+
19
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
20
+
21
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
22
+
23
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
24
+
25
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
26
+
19
27
  # DCA Watch
20
28
 
21
29
  **Answers:** "What tokens are whales dollar-cost averaging into on Solana?"
@@ -4,8 +4,6 @@ description: "What DeFi positions does a wallet hold? Protocol-by-protocol break
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -15,6 +13,11 @@ metadata:
15
13
  bins: [nansen]
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
16
+ ## Authentication
17
+
18
+ Nansen account API calls accept a selected `nansen:api` browser session or conventional API key with the same permissions. `NANSEN_API_KEY` takes precedence; optional `primaryEnv` preserves configured-key injection. Run `nansen auth status` for offline selection. Cached access expiry alone permits automatic renewal during an authorized task. Stop on anonymous selection, invalid state, blocked/uncertain renewal or actual auth failure; never drop a credential or fall back to anonymous x402 payment. Browser login does not grant wallet signing, privileged service identity or a persistent MCP integration key. Preserve all confirmation, signing, sanctions and geographic checks below. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
19
+
20
+
18
21
 
19
22
  # DeFi Exposure
20
23
 
@@ -4,8 +4,6 @@ description: "Is smart money exiting a token I hold? Net flow direction, seller
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -16,6 +14,16 @@ metadata:
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
18
16
 
17
+ ## Authentication
18
+
19
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
20
+
21
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
22
+
23
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
24
+
25
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
26
+
19
27
  # Exit Signal
20
28
 
21
29
  **Answers:** "Is smart money exiting a token I hold? Should I be worried?"
@@ -4,8 +4,6 @@ description: "What are crypto funds and VCs holding right now? Cross-chain fund
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -16,6 +14,16 @@ metadata:
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
18
16
 
17
+ ## Authentication
18
+
19
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
20
+
21
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
22
+
23
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
24
+
25
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
26
+
19
27
  # Fund Watch
20
28
 
21
29
  **Answers:** "What are crypto funds and VCs holding right now?"
@@ -4,8 +4,6 @@ description: Search for tokens or entities by name. Use when you have a token na
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -16,6 +14,16 @@ metadata:
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
18
16
 
17
+ ## Authentication
18
+
19
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
20
+
21
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
22
+
23
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
24
+
25
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
26
+
19
27
  # Search
20
28
 
21
29
  ```bash
@@ -4,8 +4,6 @@ description: "Is this token held by quality wallets or retail noise? SM holder r
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -16,6 +14,16 @@ metadata:
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
18
16
 
17
+ ## Authentication
18
+
19
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
20
+
21
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
22
+
23
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
24
+
25
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
26
+
19
27
  # Holder Quality
20
28
 
21
29
  **Answers:** "Is this token held by quality wallets or retail noise?"
@@ -4,8 +4,6 @@ description: Guide users through native limit orders on Solana via `nansen trade
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -15,6 +13,11 @@ metadata:
15
13
  bins: [nansen]
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
16
+ ## Authentication
17
+
18
+ Nansen account API calls accept a selected `nansen:api` browser session or conventional API key with the same permissions. `NANSEN_API_KEY` takes precedence; optional `primaryEnv` preserves configured-key injection. Run `nansen auth status` for offline selection. Cached access expiry alone permits automatic renewal during an authorized task. Stop on anonymous selection, invalid state, blocked/uncertain renewal or actual auth failure; never drop a credential or fall back to anonymous x402 payment. Browser login does not grant wallet signing, privileged service identity or a persistent MCP integration key. Preserve all confirmation, signing, sanctions and geographic checks below. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
19
+
20
+
18
21
 
19
22
  # Limit Orders
20
23
 
@@ -38,7 +41,7 @@ distinct paths — pick the one that matches the user's chain:
38
41
  - The wallet must hold the sell token plus a small amount of SOL for fees.
39
42
  - For the alert fallback: a notification channel (Telegram chat ID, Slack or
40
43
  Discord webhook, or generic webhook URL).
41
- - `NANSEN_API_KEY`. Smart alerts are internal-only; non-internal users get 404.
44
+ - A selected nansen:api browser session or conventional API key for smart alerts; existing endpoint restrictions still apply.
42
45
  - First-time `trade limit-order create` auto-registers a trading vault and
43
46
  caches a JWT at `~/.nansen/limit-order-auth.json` for ~23h.
44
47
 
@@ -4,8 +4,6 @@ description: "What is the state of the Hyperliquid perp market? Top contracts by
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -16,6 +14,16 @@ metadata:
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
18
16
 
17
+ ## Authentication
18
+
19
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
20
+
21
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
22
+
23
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
24
+
25
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
26
+
19
27
  # Perp Market Scan
20
28
 
21
29
  **Answers:** "What's the state of the Hyperliquid perp market right now?"
@@ -4,8 +4,6 @@ description: "Deep dive on a Hyperliquid perp trader. Identity, open positions,
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -16,6 +14,16 @@ metadata:
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
18
16
 
17
+ ## Authentication
18
+
19
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
20
+
21
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
22
+
23
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
24
+
25
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
26
+
19
27
  # Perp Trader
20
28
 
21
29
  **Answers:** "What is this perp trader doing? What are their positions and track record?"
@@ -4,8 +4,6 @@ description: "Deep dive on a Polymarket market — OHLCV, orderbook, top holders
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -16,6 +14,16 @@ metadata:
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
18
16
 
17
+ ## Authentication
18
+
19
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
20
+
21
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
22
+
23
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
24
+
25
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
26
+
19
27
  # Prediction Market Deep Dive
20
28
 
21
29
  **Answers:** "What's happening in this specific market? Who holds it, who's trading it?"
@@ -4,8 +4,6 @@ description: "Scan a resolved Polymarket market for wallets exhibiting suspiciou
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -16,6 +14,16 @@ metadata:
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
18
16
 
17
+ ## Authentication
18
+
19
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
20
+
21
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
22
+
23
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
24
+
25
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
26
+
19
27
  # PM Suspicious Wallet Scanner
20
28
 
21
29
  **Answers:** "Are there wallets with suspicious trading patterns in this Polymarket market?"
@@ -4,8 +4,6 @@ description: "What is a Polymarket trader betting on? Trades by address, PnL bre
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -16,6 +14,16 @@ metadata:
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
18
16
 
17
+ ## Authentication
18
+
19
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
20
+
21
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
22
+
23
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
24
+
25
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
26
+
19
27
  # Polymarket Wallet Activity
20
28
 
21
29
  **Answers:** "What is this Polymarket trader betting on? Are they profitable?"
@@ -4,8 +4,6 @@ description: "How has a wallet's portfolio changed over time? Historical balance
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -16,6 +14,16 @@ metadata:
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
18
16
 
17
+ ## Authentication
18
+
19
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
20
+
21
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
22
+
23
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
24
+
25
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
26
+
19
27
  # Portfolio History
20
28
 
21
29
  **Answers:** "How has this wallet's portfolio evolved over the past month?"
@@ -4,8 +4,6 @@ description: "Polymarket screeners — discover trending events, top markets by
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -16,6 +14,16 @@ metadata:
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
18
16
 
17
+ ## Authentication
18
+
19
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
20
+
21
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
22
+
23
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
24
+
25
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
26
+
19
27
  # Prediction Market Screeners
20
28
 
21
29
  All commands: `nansen research prediction-market <sub> [options]` (alias: `nansen research pm <sub>`)
@@ -4,8 +4,6 @@ description: "Is SM buying this token on one chain but selling on another? Detec
4
4
  metadata:
5
5
  openclaw:
6
6
  requires:
7
- env:
8
- - NANSEN_API_KEY
9
7
  bins:
10
8
  - nansen
11
9
  primaryEnv: NANSEN_API_KEY
@@ -15,6 +13,16 @@ metadata:
15
13
  bins: [nansen]
16
14
  allowed-tools: Bash(nansen:*)
17
15
  ---
16
+ ## Authentication
17
+
18
+ Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged.
19
+
20
+ Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry.
21
+
22
+ Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is available in CLI 2.0.0 within the [macOS arm64 preview scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope).
23
+
24
+ API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails.
25
+
18
26
  ```bash
19
27
  TOKEN_SYMBOL=<symbol e.g. "AAVE"> CHAINS=(ethereum solana base bnb)
20
28
  for chain in "${CHAINS[@]}"; do