Skip to content
GigAI

List stored assessments

GET
/api/assessments
curl --request GET \
  --url http://127.0.0.1:8765/api/assessments

Stored quick assessments, newest first, each with its job_state. A stored assessment records its basis (prompt_version, constraints_digest, story_bank: digests and ids, no settings or answer text). Served with basis_stale (true | false) and, when true, basis_stale_reason (older_prompt | settings_changed | story_bank_changed): whether it is what its profile would be assessed with now. Derived on read; no model is called. story_bank_changed is targeted: an answer or story added or edited since answers one of the assessment’s own open questions (the same id, the near match behind bank_suggestions, or a story about it), or it cites an answer or story that was edited or deleted. Such an item also carries basis_stale_bank: the entries that made it stale, each {match: "exact" | "near" | "cited", bank_question_id, bank_question?, question_id?, question?} (ids and question words, never an answer). With a master resume stored a fourth reason exists, resume_changed, targeted the same way: a resume line the assessment quoted as evidence is no longer in what its profile would be assessed with, or a line that was not there names the subject of one of its open questions. Such an item carries basis_stale_resume: each {change: "line_changed", requirement} or {change: "new_line", question_id, question?} (the assessment’s own words, never a resume line). An assessment that read the evidence view of the master carries resume_basis: {input: "evidence", master_revision_id, master_revision, selector_version}. An assessment whose answer read fewer than three requirements from a posting of 1,200+ characters (after one retry) is stored as the model gave it and carries requirements_note: “Only N requirements were read from this posting. Open the posting to check.” (omitted otherwise). A stored v9 assessment carries checks (0.1.11.4, omitted on older ones): counts of what the code checks did, no text and no ids: {settled_rows, settled_by_rule: {rule: n}, questions_dropped, questions_capped, suggestions_dropped: {reason: n}, citations_cleaned: {action: n}, questions_removed?: {reason: n}}. job_state may carry assessment_stale: {reason: "posting_changed"} (absent otherwise) when the assessment that gives the state was made on posting text that has since changed: the verdict still reads, and the job should be re-assessed. The same marker carries reason older_prompt, settings_changed or story_bank_changed when the state comes from a stored quick assessment made with an older assess prompt, other candidate settings (work mode, countries, location, sponsorship need) or answers and stories that have since changed, and resume_changed when a master resume is stored and a resume line the assessment quoted is gone or a new line names one of its open questions; nothing is re-assessed until you ask (POST /api/assess, or assess-all). job_state.state weak_fit is needs_answers for a job whose stored assessment has few requirements met AND whose rank score is low (the fit block of the project’s settings: below 40% and below rank 50): it is not counted with the jobs that need your answers. job_state.state thin_posting (0.1.11.2) is matched for a job whose stored assessment has no requirement row about the job (an empty matrix, a lone “No stated requirements” row, eligibility rows alone): nothing was judged, so it is never shown or counted as a match. A matched verdict whose stored gate decision is not_a_match reads not_a_match.

Parameters

Section titled “Parameters”

Query Parameters

Section titled “Query Parameters”
profile_id
string

“ephemeral”: only the pasted-resume assessments. A role id leaves those out and narrows no further (0.1.11.9: a job has one assessment, whichever role asked for it).

verdict
string

Only this verdict.

Responses

Section titled “Responses”

200

Section titled “200”

Success.

Media typeapplication/json
object
schema_version
required
Allowed value: scout-assessments-list-response:1
key
additional properties
any
Example
{
  "items": [],
  "schema_version": "scout-assessments-list-response:1"
}

403

Section titled “403”

Forbidden / forbidden_origin: loopback peer and Host 127.0.0.1:<port> or localhost:<port> only (Origin too on writes).

Media typeapplication/json
object
error
required
object
allowed_keys
Array<string>
code
required
string
message
required
string
key
additional properties
any
Examplegenerated
{
  "error": {
    "allowed_keys": [
      "example"
    ],
    "code": "example",
    "message": "example"
  }
}

404

Section titled “404”

Target_unavailable

Media typeapplication/json
object
error
required
object
allowed_keys
Array<string>
code
required
string
message
required
string
key
additional properties
any
Example
{
  "error": {
    "code": "target_unavailable",
    "message": "..."
  }
}

422

Section titled “422”

Bad_enum

Media typeapplication/json
object
error
required
object
allowed_keys
Array<string>
code
required
string
message
required
string
key
additional properties
any
Example
{
  "error": {
    "code": "bad_enum",
    "message": "..."
  }
}