---
title: "Read /api/dumps/hosted-files.jsonl through its compatible /api/dumps/hosted-files.ndjson route."
method: GET
path: "/api/dumps/hosted-files.ndjson"
tags: ["Agent Docs", "Artifacts"]
---

# Read /api/dumps/hosted-files.jsonl through its compatible /api/dumps/hosted-files.ndjson route.

`GET /api/dumps/hosted-files.ndjson`

## Request

- Base URL: `https://huggingbay.xyz`
- URL: `https://huggingbay.xyz/api/dumps/hosted-files.ndjson`
- Auth: none declared

Same handler and response as GET /api/dumps/hosted-files.jsonl. Includes only Hugging Bay-hosted files with recorded landing pages, download URLs, manifest URLs, hashes, and sizes.

**Inputs.** Path, query and header fields are listed below. No request body is required.

**Outputs.** See each status below for its media type, schema and headers. A missing record or unavailable capability is not a successful empty result.

**Errors.** API JSON failures use the documented response schema. Read code, message and next; retry only when the response allows it. Auth, invalid input and missing records need a caller change.

**Rate limits.** Public read budgets apply by client IP and route group. This operation can have a smaller route-specific budget. Read Retry-After on 429 or retryable 503 responses.

## Query parameters

- `limit` integer
- `cursor` integer
- `compat` 'containment'

## Response `200`

Nonempty newline-delimited hosted-file rows; follow Link rel=next until absent.

## Other responses

- `404`: No hosted files match this page (including a cursor past the end). JSON error; no empty download is served.
- `503`: The hosted inventory could not be checked and no rows are available. JSON error with Retry-After; no empty download is served.

---

[API](https://skmtc.dev/huggingbay/apis/hugging-bay-public-api.md) · [All operations](https://skmtc.dev/huggingbay/apis/hugging-bay-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/huggingbay/apis/hugging-bay-public-api/revisions/63c474bf0fe4?raw)