# Browsing the data

> The console's dataset browser, statute reader, API reference and playground.

Page: https://docs.aggre.org/console/browsing-data · Section: Console and accounts · All pages: https://docs.aggre.org/llms.txt

The console lets you look at data before you write code. Being signed in is all it needs: you do not paste a key.

## Datasets {#datasets}

`/datasets` is the catalogue of datasets. Open a dataset to read it: candle datasets show a chart and a table, instruments and the other families show tables with the filters their routes accept. What you see is what the data API returns, including `meta.status` and the `credit` text.

## Statutes {#statutes}

`/legal` lists statutes with the route's filters (jurisdiction, language, kind, status, title contains). Opening one shows its provisions, licence, attribution and restricted flag. Where attribution is required, the page shows it.

## API reference and playground {#reference}

`/docs/api` is an in-console API reference, and `/docs/playground` lets you choose a route, fill the parameters, send the request with your key and copy the equivalent code. This documentation site is the full reference; the playground is the quickest way to try a call.

## How it reads data {#how}

The data API allows no browser access, so the console's server forwards a read-only, allow-listed set of requests. Because the data API takes only API keys, the console makes a short-lived key of its own under your personal account ("Console browsing", 24 hours, read-only), reuses it between tabs and revokes it when you sign out. Browsing therefore counts toward that key's usage. A key you create yourself is never used for browsing.