---
title: "POST /api/v1/research/runs/{run_id}/continue: resume an interrupted research run"
url: https://vidbyte.pro/docs/harnesses/research/api/continue
markdown_url: https://vidbyte.pro/docs/harnesses/research/api/continue.md
index: https://vidbyte.pro/llms.txt
page_type: docs
access: public
product: "Vidbyte Research harness"
verified: 2026-10-25
---

# POST /api/v1/research/runs/{run_id}/continue: resume an interrupted research run

> Reference for POST /api/v1/research/runs/{run_id}/continue, which resumes a partial, failed, or credit-exhausted research run under the same run_id without regenerating finished artifacts, returning 202 Accepted. It takes no body and needs research:write, an Idempotency-Key, and $5.00 spendable.
>
> Index of every Vidbyte page: https://vidbyte.pro/llms.txt · Markdown: append `.md` to any vidbyte.pro URL.

## Key facts
- Method and path: POST https://vidbyte-backend.onrender.com/api/v1/research/runs/{run_id}/continue
- Headers: `x-api-key` (or Bearer) with `research:write` and `Idempotency-Key`; no request body
- Works on: partial, failed, or credit-exhausted runs owned by the caller
- Keeps: the same thread and run ids; ready artifacts are not regenerated
- Response: HTTP 202 `{"encrypted_id", "run_id", "status": "accepted"}`
- Errors: unknown or unowned run, a status that cannot resume, idempotency conflict (409), balance below $5.00 (402)

## When to use this page
- A run ran out of balance and the user topped up, or it failed partway → continue it; a run stopped at its cap → add a prompt to the thread with a higher `max_run_cost_cents` instead, because continuing reuses the same cap
- A run failed partway → continue it instead of starting a new thread
- Not for: A new question → https://vidbyte.pro/docs/harnesses/research/api/append.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. Continue the run (needs $5.00 spendable; ask the user first).

   ```bash
   curl -X POST "https://vidbyte-backend.onrender.com/api/v1/research/runs/rrun_example/continue" \
     -H "x-api-key: $VIDBYTE_API_KEY" \
     -H "Idempotency-Key: research-continue-002"
   ```
   Expected: `{"encrypted_id": "3f2504e0-4f89-41d3-9a0c-0305e82c3301", "run_id": "rrun_...", "status": "accepted"}` with HTTP 202; `encrypted_id` is a UUIDv4 and the only thread id routes accept
3. Same thing from the terminal.

   ```bash
   vidbyte-cli research resume <run_id>
   ```

- Requires: A Vidbyte API key (any account can create one) and at least $5.00 spendable in the API balance to start a run, even when the run cap is set lower.
- Cost: Billed from the prepaid API balance by measured usage, with a per-run cap (default $5). Research packs add one-time credit with no expiry: Starter $29 and Pro $148.
- Docs: https://vidbyte.pro/docs/harnesses/research.md

## What This Page Is
Reference page for the `POST /api/v1/research/runs/{run_id}/continue` endpoint of the Vidbyte Research API. Use continuation after the run has a resumable terminal state and more capacity or retry opportunity is available. 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
Resume a Research run that stopped before all of its planned source work was complete. Use it when more capacity or another retry opportunity is available so completed artifacts stay intact and unfinished work can continue. 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:write), the required headers (`x-api-key or Authorization: Bearer` and `Idempotency-Key`), 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: `{run_id}` in the path.

Returns 202 Accepted with stable thread and run identities. Durable membership makes completed source work idempotent across continuation. Calls to this endpoint start billed work and draw from your account's shared API balance; https://vidbyte.pro/docs/pricing explains how charges work.

Expected error categories: Unknown or unowned runs, non-resumable status, idempotency conflicts, capacity refusal, and workflow failures are possible.

## How to Interact With This Page
1. Open https://vidbyte.pro/docs/harnesses/research/api/continue. Under the "Harness documentation" header, the label "API-key reference" and the title "Continue an interrupted run" 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:write` permission, which the Keys page lists for each key.
5. This endpoint starts billed work, so fund your account's shared API balance first: open the "Usage" tab at https://vidbyte.pro/settings/api/usage and select "Add usage". https://vidbyte.pro/docs/pricing explains how charges work.
6. 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.
7. Send `POST` to `https://vidbyte-backend.onrender.com/api/v1/research/runs/{run_id}/continue` with your key in the `x-api-key` header (`Authorization: Bearer YOUR_KEY` also works) and `Content-Type: application/json`, plus an `Idempotency-Key` header: use a new value for each new request and resend the same value only to retry a request whose result you did not see.
8. Fill the path: replace `{run_id}` with the `run_id` value an earlier response returned.
9. No body fields are needed beyond the path.
10. Read the response: Returns 202 Accepted with stable thread and run identities. Durable membership makes completed source work idempotent across continuation.

### 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.
- A billed request that your account balance cannot cover is refused with HTTP 402 (payment required); add usage at https://vidbyte.pro/settings/api/usage and retry.

## 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/continue.md or request https://vidbyte.pro/docs/harnesses/research/api/continue 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.
- Each call draws from the user's account balance, so confirm before sending it; https://vidbyte.pro/docs/pricing explains the charges.

## 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: POST
- Path: /api/v1/research/runs/{run_id}/continue
- Availability: live
- Auth: API key with research:write
- Purpose: Use continuation after the run has a resumable terminal state and more capacity or retry opportunity is available. Ready artifacts are not regenerated.
- API-key route. Requires research:write and Idempotency-Key; the run_id is owned by the authenticated caller.

### Request Fields
### Response Shape
- Returns 202 Accepted with stable thread and run identities.
- Durable membership makes completed source work idempotent across continuation.

### Curl Example
```
curl -X POST "https://vidbyte-backend.onrender.com/api/v1/research/runs/rrun_example/continue" \
  -H "x-api-key: $VIDBYTE_API_KEY" \
  -H "Idempotency-Key: research-continue-001"
```

### Response Example
```
{
  "encrypted_id": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
  "run_id": "rrun_example",
  "status": "accepted"
}
```

## 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.
- [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.
- [Read one research thread](https://vidbyte.pro/docs/harnesses/research/api/get-thread.md): Read one thread's counts.
- [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.