Skip to content
GOCUX
Documentation
GOCUX / Documentationtask api

Enrich a company record with supplied evidence

Add evidence-backed facts without inventing an automatic data provider.

Add evidence-backed facts without inventing an automatic data provider.

Practical procedure

  1. Identify the company subject and supply authorized evidence text with its original reference. The enrichment service records the origin; it does not fetch that URL for you.
  2. Run enrichment only after reviewing the supplied evidence and the supported field vocabulary. Keep unsupported or unverified values visible as such.
  3. Inspect each established value together with its supporting quotation. Preserve the evidence association when exporting a record or presenting it to a reviewer.

Build an approved evidence path

GoCux Research works with Knowledge sources in the selected project. A plan separates the question and ordered steps from the source allowlist. Creating the plan records a draft; it does not approve or execute the work. Review the actual source selection before approving, because an empty allowlist permits no source and an execution request cannot expand an approved plan.

Contract example

Developer examples below describe routes on an authorized, configured GoCux control-plane base URL. They are request shapes or operation references, not claims that a particular public hostname exposes the API. Use the workspace for the corresponding human workflow; availability and permissions depend on the actual deployment.

Operation reference for this workflow

GET /enrichment/subjects
GET /enrichment/subjects/{subject_id}
POST /enrichment/subjects/{subject_id}/evidence

Inspect the result

Read the saved plan before deciding. After approval and execution, retrieve its findings and inspect the cited source chunks. A finding supported by a quotation is different from a question for which no source was found. Keep that difference in the final report and in any downstream table.

What to keep explicit

Company-level enrichment is not a people-search product. A claim with no verified support must not be displayed with the same confidence as a cited value.

Handle incomplete and refused work

An unapproved plan cannot execute. A 409 can mean the state or expected version changed; reread before deciding again. A 503 means the research store is unavailable, not that research found no evidence. Access is scoped to the authenticated company; knowing an identifier does not grant another company access.

Bring this workflow into your workspace.

Set the scope. Review the evidence. Approve the steps that need it.

Open the workspace

Keep exploring