> For the complete documentation index, see [llms.txt](https://docs.novamp.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novamp.io/identity-protection/identity-checker.md).

# Identity Checker

The identity checker tells you — for free, with no API key — whether a `Name + Ticker` is available, reserved, or protected.

{% hint style="success" %}
The checker is public. Creators use it before reserving or launching; traders use it to confirm they're looking at the recognized identity.
{% endhint %}

## Overview

Enter a name and ticker and the checker returns the **normalized identity key** (`NAME::TICKER`) plus its current status. Because it applies the same normalization as reservations and launches — names + tickers are folded to one canonical, confusables-aware key ([spec](https://docs.antivamp.io)) — the result is exactly what a launch would see, homoglyphs and look-alikes included.

Statuses you may see: `available`, `reserved`, `protected`, `expiring`, `expired`, `conflict`, `pending`, `failed`.

## How it works

```mermaid
flowchart LR
  A[name + ticker + chain] --> B[Normalize v2]
  B --> C[Look up registries]
  C --> D[Return key + status + decision]
```

1. Your input is normalized to a canonical identity key.
2. The key is looked up against on-chain reservations and post-launch locks.
3. The response returns the key, its status, and a launch decision.

## How to use it

### In the Novamp app

Name and ticker are checked live as you type in the [launch wizard](/creators/launching-a-token.md) and on the [Reserve page](/identity-protection/reserving-a-name-and-ticker.md). Novamp proxies the public checker at `/api/antivamp/check`, so no key is needed in the browser.

### Public endpoint

```http
GET /api/v1/identity/check?name=Green%20Robin&ticker=ROBIN&chain=base&launcher=0x00...a1
```

Example response (shape):

```json
{
  "identityKey": "GREENROBIN::ROBIN",
  "status": "reserved",
  "decision": "allow_authorized_only",
  "authorizedLauncher": "0x00000000000000000000000000000000000000a1",
  "protectedUntil": "2026-08-01T00:00:00Z",
  "chain": "base"
}
```

To look up a status directly by key:

```http
GET /api/v1/identity/status?key=GREENROBIN::ROBIN
```

{% hint style="info" %}
Pass `launcher` to see whether *your* wallet is the authorized launcher for a reserved identity — a `allow_authorized_only` decision means only that wallet may launch it.
{% endhint %}

## Important details

| Parameter  | Meaning                                                              |
| ---------- | -------------------------------------------------------------------- |
| `name`     | Raw token name (normalized server-side)                              |
| `ticker`   | Raw ticker (normalized server-side)                                  |
| `chain`    | One of `solana` `hyperevm` `base` `robinhood` `bnb` `ethereum`       |
| `launcher` | Optional wallet — checks authorized-launcher status for reservations |

The full endpoint reference, parameters, and decision semantics live in the AntiVamp API reference — see <https://antivamp.io/api>.

## What happens next?

* `available` → the identity is free to [reserve](/identity-protection/reserving-a-name-and-ticker.md) or launch.
* `reserved` / `allow_authorized_only` → only the authorized wallet can launch it during the window.
* `protected` / `conflict` → a copycat launch is blocked; if you believe it's a mistake, AntiVamp guardians can reverse mistakes — see <https://docs.antivamp.io>.

## Troubleshooting

| Symptom                                | Fix                                                                                                                      |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| `failed` / `service_unavailable`       | AntiVamp fails closed — treat as "do not launch" and retry shortly.                                                      |
| Key looks different from your input    | Normalization folded confusables to one canonical key — see <https://docs.antivamp.io>.                                  |
| Available in app but blocked at launch | Someone reserved it in between — re-check and consider [reserving](/identity-protection/reserving-a-name-and-ticker.md). |

## Continue exploring

* [🏷️ Protected-by-AntiVamp Badge](/identity-protection/protected-badge.md)
* [🔒 Reserve a Name + Ticker](/identity-protection/reserving-a-name-and-ticker.md)
* [📖 AntiVamp Documentation](https://docs.antivamp.io)
* [📡 AntiVamp API Reference](https://antivamp.io/api)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.novamp.io/identity-protection/identity-checker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.