> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/finance-and-accounting/coingecko-coins/faq.md).

# FAQ

<details>

<summary>What is a CoinGecko Coin ID and where do I find it?</summary>

The Coin ID is CoinGecko's internal identifier for each cryptocurrency — it's not the same as the ticker symbol. For example, Bitcoin's Coin ID is `bitcoin`, and Ethereum's is `ethereum`. You can look up any coin's ID using the [CoinGecko coins list endpoint](https://api.coingecko.com/api/v3/coins/list).

</details>

<details>

<summary>Can I track multiple cryptocurrencies in one data flow?</summary>

Yes. Add multiple sources to your data flow — one per coin — and use Coupler.io's **Append** transformation to combine them into a single dataset. This lets you compare prices, market caps, and volumes across coins in one table.

</details>

<details>

<summary>What currencies are supported for the vs_currency parameter?</summary>

CoinGecko supports a wide range of fiat and crypto currencies, including `usd`, `eur`, `gbp`, `jpy`, `btc`, `eth`, and many more. See the full list at the [supported vs currencies endpoint](https://api.coingecko.com/api/v3/simple/supported_vs_currencies).

</details>

<details>

<summary>What's the difference between Market charts and Histories?</summary>

**Market charts** return time-series data — a sequence of data points (prices, market caps, volumes) over a selected number of days. **Histories** return snapshot data for a specific date range, including additional fields like community and developer metrics. Use Market charts for trend analysis and Histories for point-in-time records.

{% hint style="info" %}
See [Data Overview](/sources/category/finance-and-accounting/coingecko-coins/data-overview.md) for a full breakdown of fields available in each entity.
{% endhint %}

</details>

<details>

<summary>Why does my market chart data have fewer points than I expected?</summary>

CoinGecko automatically adjusts granularity based on the `days` value. A 1-day window returns hourly data points. Windows longer than 90 days return daily data points only. This is a platform limitation — it cannot be changed in Coupler.io.

</details>

<details>

<summary>Do I need a paid CoinGecko API plan?</summary>

A free CoinGecko API key works for getting started, but free plans have lower rate limits. If you're tracking many coins or running frequent refreshes, you may hit those limits. Check your usage in the CoinGecko Developer Dashboard and consider upgrading if you encounter rate limit errors.

{% hint style="info" %}
See [Common Issues](/sources/category/finance-and-accounting/coingecko-coins/common-issues.md) for tips on handling rate limit errors.
{% endhint %}

</details>

<details>

<summary>Can I send CoinGecko data to an AI tool like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route market chart or historical data directly to these tools for trend summaries, anomaly detection, or automated commentary.

</details>

<details>

<summary>What's the best way to build a historical price dataset from scratch?</summary>

Use the **Histories** entity with a start date and end date that covers your desired backfill window. For very long histories, you can also use the **Market charts** entity with `days=max` to pull all available time-series data in one run. Combine both entities using the **Join** transformation if you need time-series and snapshot data together.

{% hint style="info" %}
See [Best Practices](/sources/category/finance-and-accounting/coingecko-coins/best-practices.md) for advice on when to use `max` days vs. a specific window.
{% endhint %}

</details>


---

# 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.coupler.io/sources/category/finance-and-accounting/coingecko-coins/faq.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.