# Introduction

growthepie is a data platform for Ethereum Mainnet, Layer 2s, Ethereum-aligned chains, apps, and data availability layers. The growthepie API exposes metadata, chain coverage, project coverage, and time-series metrics that help developers answer questions such as which chains are covered, what a metric means, how fresh the data is, and how to compare networks over time.

This documentation is designed for both human developers and AI coding tools. The docs lead with plain-English definitions, use consistent terms such as `origin_key`, `metric_key`, `value`, and `date`, and link each question to a single-purpose page with runnable examples.

## Start Here

* If you are new to the API, start with [Quickstart](/getting-started/getting-started/quickstart.md).
* If you need to choose an endpoint, see [Choose The Right Endpoint](/getting-started/getting-started/choose-the-right-endpoint.md).
* If you need the canonical list of supported chains and metrics, start with [Endpoint: master.json](/api-reference/api/master-json.md).
* If you want raw daily metric rows across covered chains, start with [Endpoint: fundamentals.json](/api-reference/api/fundamentals-json.md) or [Endpoint: export/{metric}.json](/api-reference/api/export-metric-json.md).

## Canonical Terms

* `origin_key`: The canonical identifier for a chain, app, or other covered entity in growthepie data.
* `owner_project`: The canonical identifier for a covered app or project in project-level endpoints such as `labels/projects.json` and `apps/details/{owner_project}.json`.
* `metric_key`: The canonical identifier for a raw metric series such as `txcount` or `fees_paid_usd`.
* `metric_id`: The higher-level metric identifier used in richer detail endpoints such as `txcount`, `daa`, or `fees`.
* `value`: The numeric observation for a metric at a given point in time.
* `date`: The calendar date for daily export endpoints, formatted as `YYYY-MM-DD`.

## What growthepie Covers

* Chain-level metrics such as transaction count, active addresses, transaction costs, total value secured, stablecoin supply, revenue, and throughput.
* Richer per-chain JSON such as chain overview pages and metric detail pages.
* Project coverage via `labels/projects.json` and project detail JSON via `apps/details/{owner_project}.json`.
* Data availability coverage and data availability metrics exposed in `master.json`.

## Usage Limits And Freshness Safety

* Public API rate limit guidance: no more than 10 calls per minute.
* Ignore chains whose `deployment` is `DEV` or `ARCHIVED`. Those chains can expose stale data and should not be used in production analysis.
* The API is currently public, but growthepie may change API access or authentication requirements in the future.

## Usage And Data Access Notes

* When you use growthepie data, clearly state growthepie as the source.
* Research use is encouraged. If you are using growthepie for student work, academic research, or other research activity, reach out if growthepie can support the work.
* Data is only available for chains that work with growthepie.
* Chain-level data is part of the Basic package. Application-level data is part of the Advanced package. More information: [growthepie data tiers](https://www.growthepie.com/sales#data-tiers)

## Source Of Truth

This docs set is aligned to the public API at `https://api.growthepie.com/`, the live `master.json` metadata, and the growthepie backend metric registry in `backend/src/config.py`.


---

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