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

# Environments

Where the Novamp Public Data API lives: one branded host that proxies to a set of per-chain indexers, each of which is also directly reachable.

> **Prefer the branded host. It fans out to the right per-chain indexer for you.**

{% hint style="info" %}
There is **one indexer service per chain**, each with an identical REST surface. The branded host proxies `/api/*` to the correct one and aggregates cross-chain endpoints, so most integrations only ever need a single base URL.
{% endhint %}

## Base URLs

|                                 | URL                                                         |
| ------------------------------- | ----------------------------------------------------------- |
| Branded (recommended)           | `https://app.novamp.io/api`                                 |
| Direct — Robinhood Chain (4663) | `https://novamp-rhc-indexer-production.up.railway.app/api`  |
| Direct — Base (8453)            | `https://novamp-base-indexer-production.up.railway.app/api` |
| Direct — BNB Smart Chain (56)   | `https://novamp-bnb-indexer-production.up.railway.app/api`  |
| Direct — Ethereum (1)           | `https://novamp-eth-indexer-production.up.railway.app/api`  |

Each direct origin also serves `/health` and its OpenAPI spec at `/openapi.json` and `/openapi.yaml`.

## Per-chain indexers

| Chain           | Chain ID | Notes                    |
| --------------- | -------- | ------------------------ |
| Robinhood Chain | `4663`   | Per-chain indexer        |
| Base            | `8453`   | Per-chain indexer        |
| BNB Smart Chain | `56`     | Live 2026-07-20          |
| Ethereum        | `1`      | Live 2026-07-20          |
| Solana          | `solana` | Server-prepared launches |

* **Cross-chain reads** — `/api/tokens`, `/api/discovery`, `/api/search`, and `/api/ticker/availability` (via the branded host) aggregate across chains.
* **Chain-scoped reads** — `/api/tokens/:chainId/:address` only resolves a token whose `chainId` matches the indexer that serves it. Querying an Ethereum token (`1`) against the BNB origin (`56`) returns `404`.

{% hint style="warning" %}
The direct Railway origins are convenient for chain-scoped debugging, but they can change. Point production integrations at the branded `https://app.novamp.io/api` host so chain routing stays transparent to your code.
{% endhint %}

## Self-describing payloads

Every response identifies its chain, so you never have to infer it from which host you called:

* Each token carries `chainId` and `chain` (`4663` `robinhood`, `8453` `base`, `56` `bnb`, `1` `ethereum`, or `solana`).
* Cross-chain list responses interleave chains and remain individually attributable via those fields.

```ts
const res = await fetch("https://app.novamp.io/api/tokens?limit=50&sort=recent");
const { tokens } = await res.json();
for (const t of tokens) {
  console.log(t.chain, t.chainId, t.tokenAddress, t.priceUsd);
}
```

## Identity decisions

Novamp exposes an on-chain **availability** view for a `Name + Ticker` at `/api/ticker/availability`. A signed, enforceable cross-launchpad launch **decision** is a separate concept powered by AntiVamp — see [Identity Protection](/developers/identity-protection.md).

## Continue exploring

* [🔑 Authentication](/developers/authentication.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/environments.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.