Start an artifact deep dive

Start a bounded follow-up investigation over one artifact from a signed-in browser session. The research workspace has no control that starts one yet. Use it when an existing source result needs a more focused treatment and the caller wants to choose a preset or spending cap before work begins.

POST/api/research/threads/{encrypted_id}/artifacts/{artifact_encrypted_id}/deep

Browser sessionAuthenticated browser session

Required boundary headers

X-Timestamp, X-Nonce, X-Request-Hash, and X-PreToken-Hash: signed browser-session headers the Vidbyte web app mints

Authorization (required): `Bearer <session JWT>`, or `Protected <user id>` as the web app sends it, signed into the request hash; without it the route returns 401, and the body cannot carry a user_id instead

Overview

What this route does

Use this product-session mutation when an existing source artifact needs a focused follow-up. The request can select a preset and explicit run cap.

Contract

Request parameters

Request body

Only fields in this request contract are accepted. The route rejects any undocumented field with a validation error and uses these fields to keep the work bounded and predictable.

presetOptionalenum

Chooses the configured shape of the follow-up result, such as the kind of explanation or review the artifact should receive. Leave it out to use the route's configured default, or send one supported preset value when the product needs a specific outcome.

max_run_cost_centsOptionalinteger

Sets the most the follow-up may spend on provider and model work before it stops. The value can be from 25 through 2,500 cents and defaults to 500 or your saved setting.

Examples

Request and response

Example request

bash

curl -X POST "https://vidbyte-backend.onrender.com/api/research/threads/3f2504e0-4f89-41d3-9a0c-0305e82c3301/artifacts/9b2e7c1a-5d34-4f6b-8a21-6c0d93e4b7f5/deep" \
  -H "X-Timestamp: $SESSION_TIMESTAMP" \
  -H "X-Nonce: $SESSION_NONCE" \
  -H "X-Request-Hash: $SESSION_REQUEST_HASH" \
  -H "X-PreToken-Hash: $SESSION_PRETOKEN_HASH" \
  -H "Authorization: Bearer $SESSION_JWT" \
  -H "Content-Type: application/json" \
  -d '{"preset":"complete","max_run_cost_cents":500}'

Example response

JSON

{
  "encrypted_id": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
  "artifact_encrypted_id": "9b2e7c1a-5d34-4f6b-8a21-6c0d93e4b7f5",
  "status": "accepted"
}

Response

Response and errors

Returns 202 Accepted with encrypted thread and artifact tokens plus status.
Deep-dive execution remains bounded by the accepted cap and preset policy.