> 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/developers/authentication.md).

# Authentication

How to authenticate against the Novamp Public Data API: the short answer is you usually don't. Standard data endpoints are public and read-only.

> **Public data GETs need no key. A few operational routes use internal headers. Partner keys for identity protection come from AntiVamp.**

{% hint style="success" %}
The Novamp Public Data API is **public and read-only**. Token feeds, discovery, search, quotes, and the DEX adapter need **no API key** and ship with permissive CORS — call them from a browser, bot, or serverless function.
{% endhint %}

## Standard data endpoints — no key

All the endpoints most integrations use are unauthenticated:

* Token feeds — `/api/tokens`, `/api/tokens/recent`, `/api/tokens/graduated`, `/api/tokens/:chainId/:address`
* Discovery & search — `/api/discovery`, `/api/discovery/pulse`, `/api/search`, `/api/trenches`
* Quotes — `/api/zerox/quote`, `/api/relay/quote`, `/api/uniswap/quote`
* DEX adapter — `/api/dex/*`
* Availability — `/api/ticker/availability`, `/api/ticker/reservations`

```bash
curl "https://app.novamp.io/api/tokens?limit=25&sort=volume"
```

No `Authorization` header, no key, no signup. Rate limits are applied **per IP** — see [Errors, Idempotency & Rate Limits](/developers/errors.md).

## Operational routes — internal headers

A small number of non-public routes are gated by internal secrets and are **not** part of the integration surface. They exist for Novamp's own operations:

| Header                   | Used by                         |
| ------------------------ | ------------------------------- |
| `x-admin-secret`         | Admin backfill / reindex routes |
| `x-novamp-ticker-secret` | Ticker hub cross-chain sync     |
| `x-pin-secret`           | Metadata / logo pinning         |

If you're building a terminal, aggregator, or bot, you will never need these.

## Identity protection & partner keys

Novamp's identity protection is powered by **AntiVamp**, a separate protocol. Inside Novamp it happens automatically — you don't need any credentials to benefit from it.

If you run a **launchpad** and want to integrate AntiVamp's identity protection directly (validated launches, signed decisions, reservations), AntiVamp partner API keys are **issued by AntiVamp**, not by Novamp:

* Overview of how protection works in Novamp: [Identity Protection](/developers/identity-protection.md)
* Get keys and read the partner API: <https://docs.antivamp.io>

{% hint style="info" %}
Novamp never issues or holds AntiVamp partner keys. Obtain, store, and rotate them through AntiVamp per their partner documentation.
{% endhint %}

## Continue exploring

* [🌐 Environments](/developers/environments.md)
* [❌ Errors, Idempotency & Rate Limits](/developers/errors.md)
* [📡 Public Data API](/developers/public-api.md)
* [🧩 Integration Examples](/developers/integration-examples.md)
* [🛡️ Identity Protection](/developers/identity-protection.md)


---

# 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/developers/authentication.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.