Skip to content

Activity, results and evidence

Track running jobs, distinguish no-result from failure and inspect settled credits.

Activity is the portal's execution history. Expand an entry to inspect its output, explanation, sources, ID and costs. Jobs run in the backend; closing the page does not cancel an accepted job.

Execution and answer are different

App labelMeaning
QueuedAccepted and waiting to start
RunningWork is in progress
Result foundExecution completed with a value
No resultExecution completed without a usable value
FailedAn execution error prevented completion
CancelledExecution was cancelled

The API's status: "completed" means execution ended successfully. Inspect result.value to distinguish a found answer from null or an empty array. false and 0 can be valid answers and must not be classified as missing.

Result versus sources

The result is the requested value. The summary explains it; sources are evidence links. A careers-page result is not interchangeable with a blog article used to establish the company identity. Check that a source actually supports the requested fact and belongs to the intended entity. Confidence and a valid type do not prove factual accuracy.

Billing has its own status

pending means cost is not final yet. settled means the displayed credits have been reconciled. reconciliation_pending means usage needs further reconciliation. An answer can arrive before billing finishes; missing or pending cost is not zero cost.

For integrations, retain batchId, jobId and your idempotency key. Poll enrichment.get with the original batch ID. If a job appears stuck, record its ID and contact support; do not submit a second paid job just to refresh the display.