---
title: "Dataset Nodes"
method: GET
path: "/v1/datasets/{slug}/nodes"
---

# Dataset Nodes

`GET /v1/datasets/{slug}/nodes`

## Request

- Base URL: `https://api.dryos.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.dryos.ai/v1/datasets/{slug}/nodes`
- Auth: none declared

Every entity in the dataset, with how much of it there is.

The catalogue is unusable without this. A buyer can read the schema and
still not know whether the node they care about is in here, how far back it
goes, or what it last cleared at — and the answer to "what can I reference?"
is the first question anyone asks of a feed.

Aggregated per node rather than sampled, so the counts are the real ones —
once per collector run, not once per request (`entities.py`). Coverage and
facets describe the whole table whatever the filter, because a tier count
that shrank to match the search would be answering a different question.

## Path parameters

- `slug` string, required

## Query parameters

- `q` string, nullable
- `node_type` string, nullable
- `limit` integer

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/dryos/apis/dryos-api.md) · [All operations](https://skmtc.dev/dryos/apis/dryos-api/llms.txt) · [OpenAPI document](https://skmtc.dev/dryos/apis/dryos-api/revisions/30a383fd5abc?raw)