# Nansen Entity Name Search

> Nansen Entity Name Search is a free API for AI agents from Nansen at api.nansen.ai, Free, status unknown (last checked 2026-10-11).

Search for blockchain entity names (e.g. wallets, exchanges, funds) to use as exact parameters in other Nansen v1 endpoints.

## Facts

- Endpoint: POST https://api.nansen.ai/api/v1/search/entity-name?utm_source=zero.xyz
- Price: Free
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Provider: Nansen
- Docs: https://docs.nansen.ai
- Website: https://nansen.ai
- Tags: blockchain, smart-money, wallet, tokens, defi, analytics, profiler, dex, pnl, onchain, prediction-market, data
- Canonical page: https://www.zero.xyz/c/nansen-entity-name-dc379852
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kE-a0I-9WSVntsMe4mJTe

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability nansen-entity-name-dc379852 -d '<json body>'
```

Example prompt: Search Nansen's entity name index for 'binance' so I can get the exact entity name strings to use when querying wallet balances and transactions.

## When to prefer this

Use this endpoint before calling any other Nansen v1 endpoint that accepts an `entity_name` parameter, when you only have a partial or informal name and need the exact canonical entity name string. It is free (0 credits) and should always be used to resolve entity names rather than guessing the exact format.

## Known failure modes

- Search query shorter than 2 characters returns a validation error
- No matching entities found returns an empty data array
- Query exceeding 100 characters returns a validation error
- Network or API authentication errors return HTTP 4xx/5xx responses

## How this service works

Search for entity names to use in other v1 endpoints that support `entity_name` parameters.

This endpoint helps users find the correct entity name format when they want to query by entity instead of address. Many endpoints accept either `address` or `entity_name` as parameters, but entity names must match exactly. This search endpoint makes it easy to find the right entity name.

**Key Features:**
- Case-insensitive search that matches anywhere in the entity name
- Returns up to 100 results ordered alphabetically
- Minimum 2 character search query required
- Free endpoint (0 credits)

**Use Cases:**
1. **Find entity names for profiler endpoints**: Search "vitalik" to find "Vitalik Buterin" for use in address balance or transaction queries
2. **Discover exchange entities**: Search "binance" to find all Binance-related entities
3. **Locate fund entities**: Search "jump" to find "Jump Trading" and related entities

**Example Usage:**
```json
{
  "search_query": "vitalik"
}
```

**Response:**
```json
{
  "data": [
    {"entity_name": "Vitalik Buterin"},
    {"entity_name": "Vitalik Buterin: Charity"}
  ]
}
```

**Note:** This endpoint does not support pagination as results are capped at 100 items.

## Output

A JSON array of up to 100 entity name objects, each containing an `entity_name` string (e.g. 'Vitalik Buterin', 'Vitalik Buterin: Charity'), ordered alphabetically. No pagination — results are capped at 100 items.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "title": "EntityNameSearchRequest",
 "required": [
  "search_query"
 ],
 "properties": {
  "search_query": {
   "type": "string",
   "title": "Search Query",
   "examples": [
    "vitalik",
    "binance",
    "jump"
   ],
   "maxLength": 100,
   "minLength": 2,
   "description": "Search query for entity names (minimum 2 characters). Search is case-insensitive and matches anywhere in the entity name."
  }
 },
 "description": "Request model for entity name search endpoint.\n\nThis endpoint helps users find the correct entity_name to use in other\nv1 endpoints that accept entity_name as a parameter.",
 "additionalProperties": false
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "title": "EntityNameSearchResponse",
 "required": [
  "data"
 ],
 "properties": {
  "data": {
   "type": "array",
   "items": {
    "type": "object",
    "title": "EntityNameSearchItem",
    "required": [
     "entity_name"
    ],
    "properties": {
     "entity_name": {
      "type": "string",
      "title": "Entity Name",
      "description": "Entity name that can be used in other v1 endpoints"
     }
    },
    "description": "Single entity name result."
   },
   "title": "Data",
   "description": "List of matching entity names (max 100 results, ordered alphabetically)"
  }
 },
 "description": "Response model for entity name search endpoint.\n\nReturns up to 100 entity names ordered alphabetically.\nNo pagination is provided as results are limited to 100 items."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nansen-entity-name-dc379852/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.nansen.ai](https://www.zero.xyz/host/api.nansen.ai/llms.txt)