> For the complete documentation index, see [llms.txt](https://docs.revolt.cool/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revolt.cool/for-developers/api.md).

# API Overview

Revolt exposes **on-chain interfaces** for aggregators, trading terminals, bots, and wallets. Because every Revolt token is a standard Uniswap v3 pair from block one, most integrators need nothing Revolt-specific to trade them — only to **discover** them and read their metadata.

## The 30-second integration

| You want to…                  | Use                                                         |
| ----------------------------- | ----------------------------------------------------------- |
| Discover new tokens           | `TokenCreated` events on the Revolt launcher                |
| List tokens with metadata     | `getTokens(offset, limit)` view on the launcher             |
| Read a spot price             | `priceOf(token)` on the launcher, or the pool's `slot0()`   |
| Quote a swap                  | Uniswap `QuoterV2`                                          |
| Execute a swap                | Uniswap `SwapRouter02` (`exactInputSingle`, fee tier 10000) |
| Show charts / trades          | Index the Uniswap v3 pool like any other pair               |
| Collect creator/protocol fees | `collectFees(token)` on the launcher (permissionless)       |

## Launcher address

| Chain                            | Contract       | Address                                      |
| -------------------------------- | -------------- | -------------------------------------------- |
| Robinhood Mainnet (chainId 4663) | RevoltLauncher | `0x452AeB17D922837f4d85AEA74737F48Cbd2936E7` |

## Discovering launches

Watch the launcher's `TokenCreated` event:

```solidity
event TokenCreated(
    address indexed token,
    address indexed creator,
    string  name,
    string  symbol,
    string  metadata, // JSON: {image, description, x, telegram, website}
    address pool      // the Uniswap v3 pool, live immediately
);
```

The `metadata` field is a JSON string stored on-chain — it contains the token image (data URI), description, and social links. This is where trackers get the logo and socials without any off-chain API.

## Trading example (Solidity)

```solidity
ISwapRouter02(0xCaF681…).exactInputSingle{value: ethIn}(
    ISwapRouter02.ExactInputSingleParams({
        tokenIn: WETH,
        tokenOut: token,
        fee: 10000,          // 1% tier — all Revolt pools
        recipient: msg.sender,
        amountIn: ethIn,
        amountOutMinimum: minOut,
        sqrtPriceLimitX96: 0
    })
);
```

Full addresses and ABIs: [Contract Reference](/for-developers/contracts.md) · [ABI Files](/for-developers/abi-files.md).

## REST API

The website origin also serves a public, CORS-open REST API (token list with metadata and logos, unified trades, global stats) — ideal for listings without running an indexer. Machine-readable spec: `GET /openapi.yaml` on the website origin.

Notable endpoints beyond the token/trade/stats set:

* `GET /api/tokenlist` — a standard [Token List](https://tokenlists.org) covering every Revolt token, with HTTP logo URLs derived from the on-chain metadata. Wallets, DEX front-ends, and aggregators can consume it as-is to display names and images.
* `GET /api/drop/state` — live state of the hourly [free deploy](/free-deploy.md) (open window, countdown to the next one, last winner, gift share) — useful for bots and dashboards that surface the deploy timer.

## Read next

* [Integration Guide](/for-developers/integration-guide.md) — patterns for indexers, bots, and wallets, plus security notes.
* [Contract Reference](/for-developers/contracts.md) — all deployed addresses and on-chain parameters.


---

# 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.revolt.cool/for-developers/api.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.