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

# FAQ

<details>

<summary>Does CoinMarketCap support historical OHLCV data in Coupler.io?</summary>

Yes — set the **Data type** parameter to **historical** when configuring your source. However, historical data is only available on paid CoinMarketCap API plans. If you're on the free Basic tier, this option will return empty results.

</details>

<details>

<summary>How do I specify which cryptocurrencies to pull for Quotes?</summary>

In the source settings, enter each symbol on a new line in the **Cryptocurrency symbols** field. Use the official CoinMarketCap ticker (e.g., BTC, ETH, SOL). You must enter at least one symbol — the Quotes entity won't return data without one.

</details>

<details>

<summary>Can I pull data for all cryptocurrencies at once?</summary>

For a full market list, use the **Listings** entity — it returns all ranked cryptocurrencies in one call without requiring symbol input. The Quotes entity is better suited for a targeted watchlist of specific coins.

</details>

<details>

<summary>What's the difference between Listings and Quotes?</summary>

Listings returns the full CoinMarketCap ranked table with market cap, volume, supply, and price change data for every tracked coin. Quotes returns detailed pricing data for specific coins you define by symbol. Use Listings for market overviews and Quotes for monitoring a custom set of assets.

</details>

<details>

<summary>Can I combine data from multiple CoinMarketCap entities in one destination?</summary>

Yes. Add multiple entities within the same data flow and use Coupler.io's **Join** transformation to merge them (e.g., join Listings with Quotes on the symbol field), or use **Append** to stack data from different entities or multiple data flows into one table.

</details>

<details>

<summary>Can I send CoinMarketCap data to an AI tool for analysis?</summary>

Absolutely. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. Pull your Quotes or Listings data and route it to any of these tools for automated market summaries, trend detection, or portfolio commentary.

</details>

<details>

<summary>How often can I refresh CoinMarketCap data?</summary>

You can schedule refreshes as frequently as your CoinMarketCap API plan allows. The free Basic plan has monthly credit limits — each sync run consumes credits. Hourly refreshes are a practical balance for most use cases on a free plan.

</details>

<details>

<summary>Why is my CoinMarketCap data slightly different from the website?</summary>

CoinMarketCap prices update continuously. Any data you've pulled reflects the moment of the last sync, not the real-time price. Check the **last\_updated** field in your data to see exactly when the snapshot was taken.

</details>

{% hint style="info" %}
For a full list of available fields and metric definitions, see the [Data Overview](/sources/category/finance-and-accounting/coinmarketcap/data-overview.md) article. If you're hitting API errors or missing data, check [Common Issues](/sources/category/finance-and-accounting/coinmarketcap/common-issues.md) for fixes.
{% endhint %}


---

# 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/coinmarketcap/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.