Nansen company primary-source snapshot

Fetched: 2026-08-08 UTC

1) Homepage / product framing

Source: https://nansen.ai/

Selected excerpts from the official site:

Trade Everything Onchain With AI

See what Smart Money is buying, trade it, and track every move - all in one platform.

500M+ labeled addresses - the deepest wallet labels onchain.

Ask anything onchain and get the answer in seconds … Then tell it to trade, all in one conversation.

Additional signals from the homepage:

  • Nansen is packaging research, wallet intelligence, trade execution, and account-level incentives inside one company-run product shell rather than a narrow analytics dashboard
  • The homepage explicitly treats labeled-wallet data and direct execution as one loop, which is exactly why the entity note matters
  • The current pitch is not just data; it is a branded operating surface for discovery, trade routing, and user workflow

2) Docs introduction / API scope

Source: https://docs.nansen.ai/

Selected excerpts from the docs:

Nansen API offers programmatic access to high-quality onchain data and advanced blockchain analytics across numerous networks.

Proprietary Data Labeling: Nansen applies unique, human-readable labels to hundreds of millions of blockchain addresses.

The API provides access to data points and analytics not readily available elsewhere, such as Smart Money analytics.

Additional signals from the docs intro:

  • Nansen openly presents proprietary labeling as the core value boundary rather than pretending the data is a neutral commodity
  • Multi-chain coverage, Smart Money analytics, and one integration point make the operator boundary analytically stronger than any single feature page
  • The docs root also groups Smart Money, Profiler, Token Screener, Portfolio, Hyperliquid, Prediction Markets, Agent, and MCP surfaces under one authenticated API shell

3) Agent access and MCP access

Sources:

Selected excerpts from the agent and MCP docs:

Your agent will ask you to visit the setup page … Sign in with your Nansen account … Copy the message shown … Paste it back to your agent.

The Nansen MCP server provides AI assistants with access to comprehensive blockchain analytics through a secure API.

Nansen MCP uses the same API as your regular API keys. Ensure you have sufficient credits for your usage.

Ask the Nansen AI agent a research question and receive a streamed answer backed by on-chain data.

Additional signals from the agent and MCP docs:

  • Agent and MCP access are not separate neutral standards; they are company-gated entry points into the same Nansen data and credit system
  • Account sign-in, API keys, credits, and hosted MCP server availability all sit squarely with Nansen as operator
  • The agent surface matters because Nansen now controls not just dashboards or APIs but also AI-facing workflow packaging and the boundaries around machine consumption of its labels and analytics

Source: https://nansen.ai/legal/api

Selected excerpts from the API terms:

The Model Context Protocol (“MCP”) is treated as an access method to the API Services and is governed by these API Terms unless expressly stated otherwise.

Nansen’s proprietary labeled blockchain data, entity classifications, and analytics methodologies constitute core intellectual property assets of Nansen.

All proprietary labeled data, entity classifications, and blockchain analytics methodologies … are owned exclusively by Nansen and are licensed, not sold, to you.

Certain endpoints may be designated as restricted. Access to such endpoints requires prior approval … Approval is at our sole discretion and may be withdrawn at any time.

We may, in our discretion, restrict or prohibit access to the API, MCP, or Nansen Data by competitors or users reasonably believed to be acting on behalf of competitors.

Additional signals from the API terms:

  • The cleanest current company boundary is not just labels or dashboards but the legal perimeter around API credentials, rate limits, restricted endpoints, redistribution rules, and machine access
  • Nansen explicitly treats its labels and classification methods as proprietary IP, which is exactly the sort of authority split the company layer is supposed to preserve
  • Competitor restrictions, endpoint approvals, and MCP-under-API-terms language make the operator boundary unusually legible

5) General terms / service-change and jurisdiction boundary

Source: https://nansen.ai/legal/terms-of-services

Selected excerpts from the terms:

We may modify or discontinue any aspect, feature, or functionality of the Services at our discretion.

The term, “Services” encompasses all current and future platforms, related websites, functionalities, applications, software, APIs, subscription plans, products, and content provided by Nansen.

We reserve the right to restrict or prevent access to our Services in any jurisdiction at our sole discretion.

Nansen is merely a technology service provider connecting you with various third parties and does not offer fiduciary services.

Additional signals from the terms:

  • The legal docs confirm that the relevant unit is the Nansen service perimeter as a whole, not one isolated app page
  • Feature retirement, jurisdiction gating, account restriction, and terms-level service scope all sit with the company boundary
  • This is useful context for any future note about Nansen trading, staking, or wallet-facing features because it shows who can actually change or withdraw access

Notes

  • This pass did not surface a classic Nansen company whitepaper or litepaper.
  • The strongest current primary materials were the homepage, docs intro, agent and MCP docs, API terms, and terms of service.
  • Nansen is best treated as a named operator boundary around proprietary labels, account-gated analytics, agent/MCP access, redistribution policy, and integrated execution workflow rather than only as an analytics product brand.