Browser-session reference

Start an artifact deep dive

Start a bounded follow-up investigation over one artifact from the authenticated workspace. 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

Cookie: authenticated browser sessionIdempotency-Key
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 ignores no undocumented shape 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 maximum run budget the follow-up may use before it pauses or refuses additional work. The value can be from 1 through 100,000 cents, so callers can approve a visible cap instead of accepting an open-ended spend.

Examples

Request and response

Example request

curl -X POST "https://vidbyte-backend.onrender.com/api/research/threads/rth_public_token/artifacts/rart_public_token/deep" \ -H "Cookie: authenticated-session" \ -H "Content-Type: application/json" \ -d '{"preset":"complete","max_run_cost_cents":500}'

Example response

{ "encrypted_id": "rth_public_token", "artifact_encrypted_id": "rart_public_token", "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.