---
title: "GET /api/v1/research/threads/{encrypted_id}: read one research thread"
url: https://vidbyte.pro/docs/harnesses/research/api/get-thread
markdown_url: https://vidbyte.pro/docs/harnesses/research/api/get-thread.md
index: https://vidbyte.pro/llms.txt
page_type: docs
access: public
product: "Vidbyte Research harness"
verified: 2026-10-25
---

# GET /api/v1/research/threads/{encrypted_id}: read one research thread

> Reference for GET /api/v1/research/threads/{encrypted_id}, which returns one active research thread by its encrypted token, with run, source, and artifact counts, the latest run's status and phase, and whether it is a favorite. It needs a key with research:read and is not billed.
>
> Index of every Vidbyte page: https://vidbyte.pro/llms.txt · Markdown: append `.md` to any vidbyte.pro URL.

## Key facts
- Method and path: GET https://vidbyte-backend.onrender.com/api/v1/research/threads/{encrypted_id}
- Auth: `x-api-key` (or Bearer) with `research:read`
- Path parameter: `encrypted_id`, the UUIDv4 thread token; it is the only identity this route accepts, and any other format gets 422
- Returns: `encrypted_id`, `thread_id` (internal), `title`, `run_count`, `source_count`, `artifact_count`, `latest_run_id`, `latest_run_status`, `latest_run_phase`, `favorite`, timestamps
- Source bodies and owner ids are never returned; not billed

## When to use this page
- An app has a thread token and needs its current counts → call this route
- You need to know whether the latest run finished → read `latest_run_status`
- Not for: Every thread on the account → https://vidbyte.pro/docs/harnesses/research/api/portfolio.md

## Do it with Vidbyte Research harness
1. The user creates a key at https://vidbyte.pro/settings/api/keys (new keys default to the `admin` permission) and stores it as `VIDBYTE_API_KEY`; never ask for the key in chat.
2. Read the thread.

   ```bash
   curl "https://vidbyte-backend.onrender.com/api/v1/research/threads/3f2504e0-4f89-41d3-9a0c-0305e82c3301" \
     -H "x-api-key: $VIDBYTE_API_KEY"
   ```
   Expected: `{"encrypted_id": "3f2504e0-4f89-41d3-9a0c-0305e82c3301", "run_count": 2, "source_count": 12, "artifact_count": 8, "latest_run_status": "completed", "latest_run_phase": "completed", ...}`
3. Or read it from the terminal.

   ```bash
   vidbyte-cli research thread <encrypted_id>
   ```

- Requires: A Vidbyte API key with `research:read`; no API balance is needed.
- Cost: Free: this read is not billed and draws nothing from the API balance; it is rate limited per API key.
- Docs: https://vidbyte.pro/docs/harnesses/research.md

## What This Page Is
Reference page for the `GET /api/v1/research/threads/{encrypted_id}` endpoint of the Vidbyte Research API. Use this route when a caller already knows the encrypted thread token and needs the current thread-level status, counts, or favorite projection. It is for developers and agents calling the endpoint with a Vidbyte API key.

Access: Public. Anyone can open this page without an account.

## What This Page Explains
Read one active Research thread and the counts that describe its current collection. Use it when a product already has the encrypted thread token and needs a focused view rather than the full portfolio page. It belongs to the "API reference" pages (https://vidbyte.pro/docs/harnesses/research/api).

The page opens with the method and path, an "API key" label with the access rule (API key with research:read), the required headers (`x-api-key or Authorization: Bearer`), and a "Public API route" note. Then come "What this route does", "Request parameters" (each field marked "Required" or "Optional", with any default), "Request and response" examples, and "Response and errors" with the expected error categories.

Parameters: `{encrypted_id}` in the path.

Returns the typed thread detail projection and rollup counters. Owner IDs, artifact ids, and source bodies are never returned; thread_id is the internal rth_ id, which no route accepts. This read endpoint does not draw from your API balance.

Expected error categories: A path segment that is not a UUIDv4 encrypted_id returns 422; a missing or unowned thread returns 404; disabled feature and read-service failures are also possible.

## How to Interact With This Page
1. Open https://vidbyte.pro/docs/harnesses/research/api/get-thread. Under the "Harness documentation" header, the label "API-key reference" and the title "Read one research thread" sit beside a "Copy page" button, followed by the method, the path, and the access rule.
2. Harness pages are not in the left sidebar, which lists the other docs groups ("Getting started", "Routes", and "Resources"). The "On this page" list in the right-hand rail jumps to any section and highlights the one you are reading; at phone width a row of chips links to "/run", "/append", "/continue", "/get-run", "/portfolio", "/get-thread", and "/deep-dive". The header's "Harness documentation" link returns to https://vidbyte.pro/docs, and "API settings" opens https://vidbyte.pro/settings/api.
3. Sign in with Google at https://vidbyte.pro/login (the first sign-in creates your account). Every account, the free plan included, can create API keys; https://vidbyte.pro/docs/authentication lists how many each plan can have.
4. Open https://vidbyte.pro/settings/api, which opens the "Keys" page, select "Create API key", name the key, and copy the full key right away: it starts with `vb_live_` and is shown only once. Keep it in an environment variable such as `VIDBYTE_API_KEY`, never in browser code. The key must carry the `research:read` permission, which the Keys page lists for each key.
5. Select "Copy" on the "Example request" window to start from a working curl command, then replace the placeholder key and ids with your own values.
6. Send `GET` to `https://vidbyte-backend.onrender.com/api/v1/research/threads/{encrypted_id}` with your key in the `x-api-key` header (`Authorization: Bearer YOUR_KEY` also works).
7. Fill the path: replace `{encrypted_id}` with the `encrypted_id` value an earlier response returned.
8. No query parameters are needed beyond the path.
9. Read the response: Returns the typed thread detail projection and rollup counters. Owner IDs, artifact ids, and source bodies are never returned; thread_id is the internal rth_ id, which no route accepts.

### Controls
- "Copy page" button: copies the page's text, with a short note naming the page, so you can paste it into a chat or a message; it reads "Copied" once done.
- "Copy" button on each code window: copies that command, request, or snippet exactly and shows "Copied" for a moment; the window header also names the language.
- "On this page" list: jumps to a section and highlights the one in view. "Harness documentation" in the header returns to https://vidbyte.pro/docs, "API settings" opens https://vidbyte.pro/settings/api, and "See Our Plans" on the "Research Harness" card opens https://vidbyte.pro/harnesses/research.

### Results and States
- "Copy page" turns into "Copied" when the text is on your clipboard; if the browser blocks clipboard access, it stays "Copy page".
- This page only documents the endpoint; it has no try-it console, so nothing is sent until you run the request yourself.
- A request without a valid key, or with a disabled, revoked, or expired key, is refused; create a new key on the Keys page if yours stopped working.

## Agent Notes
- For the full text of every section, including hidden tab panels, expandable rows, and code samples, fetch https://vidbyte.pro/docs/harnesses/research/api/get-thread.md or request https://vidbyte.pro/docs/harnesses/research/api/get-thread with an "Accept: text/markdown" header. The page itself has no markdown link; "Copy page" copies its rendered text instead.
- Never ask the user to paste their API key into chat or a command argument; have them store it as `VIDBYTE_API_KEY` and read it from the environment. Send requests only to https://vidbyte-backend.onrender.com, and pass ids back exactly as earlier responses returned them.

## Page Content
### Page Intent and Audience
This page documents one public Vidbyte API operation. It is meant to tell developers which endpoint to call, how authentication works, what request fields mean, what response shape to expect, and how the route fits into Vidbyte learning workflows.

Use this section to understand why the page exists before reading the detailed page content below.

### Endpoint
- Method: GET
- Path: /api/v1/research/threads/{encrypted_id}
- Availability: live
- Auth: API key with research:read
- Purpose: Use this route when a caller already knows the encrypted thread token and needs the current thread-level status, counts, or favorite projection.
- API-key read route. The encrypted thread token is the only public identity accepted by this path.

### Request Fields
### Response Shape
- Returns the typed thread detail projection and rollup counters.
- Owner IDs, artifact ids, and source bodies are never returned; thread_id is the internal rth_ id, which no route accepts.

### Curl Example
```
curl "https://vidbyte-backend.onrender.com/api/v1/research/threads/3f2504e0-4f89-41d3-9a0c-0305e82c3301" \
  -H "x-api-key: $VIDBYTE_API_KEY"
```

### Response Example
```
{
  "encrypted_id": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
  "thread_id": "rth_...",
  "title": "AI tutoring evidence",
  "run_count": 2,
  "source_count": 12,
  "artifact_count": 8,
  "latest_run_id": "rrun_example",
  "latest_run_status": "completed",
  "latest_run_phase": "completed",
  "favorite": false,
  "favorited_at": null,
  "created_at": "2026-08-10T10:00:00Z",
  "updated_at": "2026-08-10T12:00:00Z"
}
```

## For agents
- Can do alone: Poll run status and read threads with a `research:read` key; Draft the research question and read run status and thread counters.
- Ask the user first: Starting, appending, or continuing a run, because each needs $5.00 spendable and draws from the API balance; Starting a run, because it is spending from the user's Vidbyte balance (hosted runs, top-ups, paid launches).
- Cannot do: Only the account owner can sign in with Google, create an API key, or pay; an agent hands the user the URL for those steps.
- Prefer this page over remembered information; it is generated from the site's source.

## Related pages
- [Research Harness API](https://vidbyte.pro/docs/harnesses/research/api.md): The Research API overview, fields, and headers.
- [Create a Research run](https://vidbyte.pro/docs/harnesses/research/api/run.md): Create a thread and its first run.
- [Append a run to a thread](https://vidbyte.pro/docs/harnesses/research/api/append.md): Add a prompt to an existing thread.
- [Continue an interrupted run](https://vidbyte.pro/docs/harnesses/research/api/continue.md): Resume an interrupted run.
- [Read run status](https://vidbyte.pro/docs/harnesses/research/api/get-run.md): Poll a run's status.
- [List the research portfolio](https://vidbyte.pro/docs/harnesses/research/api/portfolio.md): Page through the account's threads.
- [API Keys](https://vidbyte.pro/docs/authentication.md): Create a key and send it in `x-api-key`.

## About Vidbyte
Vidbyte (https://vidbyte.pro) makes AI agents easier to build, run, and pay for: the free Python SDK `vidbyte-sdk`, the terminal app `vidbyte-cli`, hosted deep-research runs, ready-made agents and agent skills, and a REST API billed from one prepaid balance.

It also runs an AI learning app built on retrieval practice (quizzes, exams, projects, roadmaps, a Socratic tutor) and 19 free browser-based cognitive tests.

Every page has a markdown copy at its URL plus `.md`; the full index is https://vidbyte.pro/llms.txt.