> ## Documentation Index
> Fetch the complete documentation index at: https://docs.felixfusion.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# API organization

> How the FelixFusion public API is structured and how to navigate it.

## Base structure

The public API is organized under one base URL:

```text theme={null}
https://api.felixfusion.ai
```

All public routes documented in the API reference live under `/v1`, except the health route at `/health`.

## Main route groups

| Route group                | Purpose                                |
| -------------------------- | -------------------------------------- |
| `/v1/datasets`             | discover datasets and inspect metadata |
| `/v1/datasets/{id}/query`  | fetch rows from a dataset              |
| `/v1/datasets/{id}/audit`  | inspect dataset audit records          |
| `/v1/dataset-updates/{id}` | check update history                   |
| `/v1/pricing_locations`    | inspect pricing nodes, hubs, and zones |
| `/v1/reports/...`          | pull report-style outputs              |
| `/v1/api_usage`            | inspect plan and usage metadata        |

## Authentication model

Public routes accept API keys in two forms:

* `x-api-key` header
* `api_key` query parameter

Header-based authentication is the preferred format for production integrations.

## Response patterns

Most list and query routes return JSON responses with:

* `data` for rows or items
* `meta` for pagination details

Some routes also support CSV output through `return_format=csv`.

## How to approach the API

1. Discover the dataset you want.
2. Inspect its metadata.
3. Query it with time filters and selected columns.
4. Switch to CSV download if you need file export.