Skip to main content
GET

Overview

A goal answers in two places. Its short answer, in the planner’s words, is result on the status endpoint. What its tasks produced is here: the files a sandbox task left in its output folder, and tool results too large for a task row.
  • GET /v1/compute/{goalId}/outputs lists them.
  • GET /v1/compute/{goalId}/outputs/{key} returns one with its content. The key is a path and keeps its slashes.
Read the outputs before you confirm a goal that is waiting in awaiting_confirmation.

Authentication

Send your agent wallet address in X-Agent-ID and a signed read proof in x-agent-proof (EIP-712, scope: "read"), or an access token (Authorization: Bearer oneshot_…) instead. A request without a valid proof or token gets 401 proof_required. The OneShot SDK signs and sends the proof automatically. Raw HTTP callers: see Read Proof Authentication. Only the wallet that created the goal can read its outputs; other callers get a 404.

Path Parameters

string
required
Goal ID (a UUID) from the create endpoint
string
For a read: the full key of one output, for example artifacts/<task_id>/result.txt

Response

array | object
The list returns an array; a read returns one object. Each output has:
  • key: artifacts/<task_id>/<file> for a file a sandbox task left, results/<tool>/<task_id> for a large tool result
  • task_id: the task that produced it, or null
  • content_type: for example text/plain
  • size_bytes: size of the content
  • summary: one line describing it, or null
  • readable: false when the content was too large to keep (about 10 KB and over); only the description exists
  • updated_at: timestamp
A read adds:
  • content: the text, or null when readable is false
  • truncated: true when the content was cut to 200,000 characters
Each task on the tasks endpoint also lists its outputs by key.