# Endpoint: export/{metric}.json

`export/{metric}.json` returns the flat public export for one fundamental metric across covered chains. Use `export/{metric}.json` when you want a single metric such as `txcount`, `daa`, or `fees` without downloading the broader `fundamentals.json` file.

## Request

```
GET https://api.growthepie.com/v1/export/{metric}.json
```

Example:

```
GET https://api.growthepie.com/v1/export/txcount.json
```

## Supported Public Metric Paths

* `app_revenue`
* `daa`
* `fdv`
* `fees`
* `market_cap`
* `profit`
* `rent_paid`
* `stables_mcap`
* `throughput`
* `tvl`
* `txcosts`
* `txcount`

## Example Response

```json
[
  {
    "metric_key": "txcount",
    "origin_key": "arbitrum",
    "date": "2021-05-29",
    "value": 9.0
  }
]
```

## Notes On metric vs metric\_key

The path uses a higher-level metric identifier such as `fees` or `tvl`. The returned rows use raw `metric_key` values such as `fees_paid_usd`, `fees_paid_eth`, `tvl`, or `tvl_eth`.

## When To Use export/{metric}.json

* You want full metric history
* You want one metric across many chains
* You want a flat export for notebooks, CSV export, or a local cache

## Caveats

* The path parameter is the public metric identifier, not the raw `metric_key`.
* Multi-currency metrics can return more than one `metric_key` in the same file (usually USD and ETH).

## Related Pages

* [Metric Reference Overview](/metric-reference/metric-reference.md)
* [Fetch A Metric In curl](/recipes-tutorials/recipes/fetch-a-metric-in-curl.md)


---

# Agent Instructions: 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:

```
GET https://docs.growthepie.com/api-reference/api/export-metric-json.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.