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

# Data Overview

The CoinGecko Coins source provides two types of data: time-series market chart data and point-in-time historical records. Both entities are scoped to a single coin and currency pair per source configuration.

## Entities

| Entity        | What it contains                                                                                                 |
| ------------- | ---------------------------------------------------------------------------------------------------------------- |
| Market charts | Prices, market caps, and total volumes sampled over a selected time window (1 day up to all-time)                |
| Histories     | A historical snapshot of a coin's price, market cap, volume, and community/developer data for a given date range |

## Available data fields

#### Market charts

| Field         | Description                                             |
| ------------- | ------------------------------------------------------- |
| timestamp     | The date and time for the data point                    |
| price         | Coin price in the selected currency                     |
| market\_cap   | Total market capitalization at that timestamp           |
| total\_volume | Total trading volume across exchanges at that timestamp |

#### Histories

| Field           | Description                                                                 |
| --------------- | --------------------------------------------------------------------------- |
| date            | The date of the historical record                                           |
| current\_price  | Price in the selected currency on that date                                 |
| market\_cap     | Market cap on that date                                                     |
| total\_volume   | Total trading volume on that date                                           |
| community\_data | Metrics like Twitter followers and Reddit subscribers (where available)     |
| developer\_data | Developer activity metrics such as GitHub stars and forks (where available) |

## Common data combinations

* **Market charts + Histories** — use the **Join** transformation to cross-reference time-series price trends with historical snapshot details for deeper context
* **Multiple coins via Append** — configure one source per coin (e.g. Bitcoin, Ethereum, Solana) and use **Append** to create a single unified table for side-by-side comparison
* **Aggregate transformation** — use **Aggregate** on market chart data to calculate averages, minimums, or maximums over a time window without leaving Coupler.io

## Use cases by role

{% tabs %}
{% tab title="Finance teams" %}

* Track the USD or EUR value of crypto holdings over time using Market charts
* Pull historical price data into Excel or Google Sheets to support portfolio valuation and reporting
* Feed daily price snapshots into BigQuery for auditing or compliance records
* Use AI destinations like Claude or ChatGPT to summarize price trends and flag anomalies automatically
  {% endtab %}

{% tab title="Analysts" %}

* Compare price, market cap, and volume trends across multiple coins using Append + Aggregate transformations
* Build Looker Studio dashboards powered by live CoinGecko data refreshed on a schedule
* Use the `days=max` setting on Market charts to pull all available history for long-term trend analysis
* Send aggregated market data to Gemini or Perplexity for AI-generated market commentary
  {% endtab %}

{% tab title="Developers" %}

* Use Coupler.io as a no-code pipeline to feed CoinGecko data into BigQuery or other data warehouses
* Combine CoinGecko data with other financial sources via Join to enrich crypto data with exchange rates or stock prices
* Use the Histories entity to backfill datasets with date-range snapshots without hitting the API directly
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* The **Coin ID** must match CoinGecko's internal identifier exactly — use the [coins list endpoint](https://api.coingecko.com/api/v3/coins/list) to look up the correct ID before configuring your source
* Market chart data granularity is controlled by CoinGecko based on the `days` parameter: 1 day returns hourly data, ranges above 90 days return daily data
* Community and developer data in the Histories entity may be `null` for newer or less-tracked coins
* Free-tier CoinGecko API keys have rate limits that may affect how many coins you can sync simultaneously — check your plan limits before setting up many data flows
* Each source is scoped to a single coin and currency pair; to track multiple coins or currencies, add additional sources to your data flow


---

# 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/data-overview.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.