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

# Developer Overview

Build on Novamp. This section documents the **Novamp Public Data API** — a read-only, cross-chain market-data feed for terminals, aggregators, bots, and dashboards. It's the same data behind the in-app **Data** tab.

> **One read-only API for every Novamp chain. No key, self-describing payloads.**

{% hint style="info" %}
Everything here is copy-paste ready. Public data endpoints need **no API key** and use permissive CORS, so you can call them straight from a browser, a bot, or a serverless function.
{% endhint %}

## What the API gives you

| Capability          | Endpoints                                                                               |
| ------------------- | --------------------------------------------------------------------------------------- |
| **Token feeds**     | All tokens, newest launches, graduated tokens, single token by chain + address          |
| **Discovery**       | Aggregated discovery feed, live "pulse" activity, lifecycle board, milestone candidates |
| **Search**          | Cross-chain search over names, tickers, and addresses                                   |
| **Prices & quotes** | Per-chain market data, swap/bridge quotes, portfolio reads                              |
| **DEX adapter**     | GeckoTerminal / Dexscreener-standard pair and event feeds                               |

Every payload is **self-describing**: each token carries `chainId` and `chain` (`4663` `robinhood`, `8453` `base`, `56` `bnb`, `1` `ethereum`, or `solana`), so multi-chain results never need out-of-band context. Full endpoint reference: [📡 Public Data API](/developers/public-api.md).

## Design principles

* **Read-only aggregator.** The branded host at `https://app.novamp.io/api` proxies to one indexer per chain; cross-chain endpoints fan out and merge results for you.
* **Chain-scoped detail.** Single-token reads (`/api/tokens/:chainId/:address`) resolve only against the indexer that owns that chain.
* **Stable, machine-readable shapes.** Money values are string decimals; unknown values are `null`; list responses include `count`, `limit`, `offset`.
* **Public by default.** Standard data GETs are unauthenticated with `Access-Control-Allow-Origin: *` and per-IP rate limits.

## Identity protection

Identity protection on Novamp — reserving and defending each token's normalized `Name + Ticker` across chains and launchpads — is powered by **AntiVamp**. See the [Identity Protection](/developers/identity-protection.md) page for how it surfaces inside Novamp and where launchpads can integrate it directly.

## Continue exploring

* [🏗️ Architecture](/developers/architecture.md)
* [🔑 Authentication](/developers/authentication.md)
* [🌐 Environments](/developers/environments.md)
* [🧩 Integration Examples](/developers/integration-examples.md)
* [📡 Public Data API](/developers/public-api.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/overview.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.