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

# Integrations and data

The third-party services and data sources behind TRNCH, and what each one does.

TRNCH is built on Robinhood Chain's public data and on third-party services. This page lists them and what each one does for TRNCH. Naming a service here does not mean it endorses TRNCH: we use their public APIs and libraries, under their terms. What personal data each one receives is set out in the [Privacy Policy](/legal/privacy.md).

## Robinhood Chain

TRNCH runs on Robinhood Chain (chain ID 4663). Everything the Heat shows starts from the chain itself.

| Service                    | What TRNCH uses it for                                                                                                                                                                                                |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Robinhood Chain public RPC | Balances, approvals and transaction receipts, read by your browser and by our servers. The transactions you sign are broadcast by your own wallet.                                                                    |
| Envio HyperSync            | The main source of our relay: new pools and swaps, read from the chain as blocks come in.                                                                                                                             |
| Alchemy                    | A backup node provider for our relay, used when HyperSync is unavailable.                                                                                                                                             |
| Blockscout                 | The chain's block explorer. Your wallet's tokens and balances, token details, contract creation dates, and the public names registered with the chain's name service. The explorer links on the site open Blockscout. |

## Our relay

The relay is TRNCH's own real-time service, hosted on Cloudflare. It reads the swaps of the main pool families (Uniswap-style pools and Pons bonding curves), values them, keeps the recent history of active pools, computes the Heat and streams it all to your browser. It also provides the reference prices used to check swap quotes. See [Routing and quotes](/trade/routing-and-quotes.md).

## Market data

| Service       | What TRNCH uses it for                                                                                                                                                                                                                                         |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| GeckoTerminal | Price history for the charts, recent trades, the list of new pools, token details (holders, developer share, verification, socials) and logos. Holder data from GeckoTerminal feeds the Heat's trust factor. The site credits it with "Data by GeckoTerminal". |
| DexScreener   | Token logos when GeckoTerminal has none, and a second price source for the game's reference price.                                                                                                                                                             |

The live part of each chart comes from our relay. The Heat's price changes, depth, volume and last trade are read from the pools by our relay, not from a data provider. See [Heat methodology](/heat/methodology.md).

## Charts

Charts are drawn with TradingView's Lightweight Charts library, served from TRNCH's own site. The site credits it with "Charts by TradingView", linked to TradingView.

## Swap routing

| Router    | Role                                                                                            |
| --------- | ----------------------------------------------------------------------------------------------- |
| KyberSwap | Aggregator, asked for a quote on every swap.                                                    |
| LI.FI     | Aggregator, asked for a quote on every swap.                                                    |
| Uniswap   | Uniswap's trading API, asked for a quote on every swap.                                         |
| 0x        | Aggregator, asked for a quote on every swap. When it does not answer, the other three carry on. |

TRNCH's servers ask all of them at once, check the answers and keep the route that returns the most tokens among those that pass. The list may change. See [Routing and quotes](/trade/routing-and-quotes.md).

When you pay with USDG and your wallet holds none, the swap panel shows a **Bridge USDG** link to Jumper (jumper.exchange), a third-party bridge. The bridge is not part of TRNCH.

## Wallets and sign-in

| Service       | What TRNCH uses it for                                                                                    |
| ------------- | --------------------------------------------------------------------------------------------------------- |
| Privy         | Sign-in, with your wallet or your X account, and linking your X account to your profile if you choose to. |
| WalletConnect | The wallet directory in the sign-in window, and the connection to wallets that use WalletConnect.         |

TRNCH works with self-custodial wallets such as MetaMask, Rabby or Rainbow, or any wallet that connects through WalletConnect. Your wallet signs every transaction.

## Infrastructure

| Service     | What TRNCH uses it for                                                                                           |
| ----------- | ---------------------------------------------------------------------------------------------------------------- |
| Vercel      | Hosts the site and runs its server functions. Page views are counted with Vercel Web Analytics, without cookies. |
| Supabase    | Our database, hosted in the European Union (Ireland): tokens, price history, volume, packs and game data.        |
| Cloudflare  | Runs our relay.                                                                                                  |
| GitBook     | Hosts this documentation.                                                                                        |
| UptimeRobot | Checks that our relay is up.                                                                                     |
| Zoho        | Hosts our email, <hello@trnch.fun>.                                                                              |

## TRNCH API

There is no public TRNCH API for now. The site's own endpoints serve the site only, are rate-limited and can change without notice. If you want to build on TRNCH data, write to <hello@trnch.fun>.


---

# 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.trnch.fun/integrations.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.
