Skip to main content
POST
Get Execution
Use this API to fetch an execution document by ID. This is the polling endpoint: poll until execution.status !== "running". Set includeResults: true to also fetch the per-URL findings subcollection.

Endpoint

POST https://api.velt.dev/v2/agents/execution/get

Headers

string
required
Your API key.
string
required

Body

Params

object
required

Example Requests

1. Poll status only

2. Fetch with full results

Response

Success Response (execution document)

Execution document field reference:
The legacy execution-document fields knowledgeRetrieved / knowledgeCached / degraded have been removed. Memory-RAG runtime signals now live only on the in-memory execution result and are consumed internally by the guardrails processor; they are not persisted on the execution document.

Run-level error codes

These codes end the whole execution with status error and error.retryable: true, except on a run over several pages, as described below the table. To review the page, start a new run. On a run over several pages, these two codes can also end a single page instead of the run. A page that runs out of time in an agentIds run (SUITE_TIMEOUT), or whose deliveries keep failing for 3 deliveries (RUN_ATTEMPTS_EXHAUSTED), is counted as an errored page of each execution it belongs to: resultsSummary.urlsErrored counts it, resultsSummary.erroredUrls lists it with The run took too long and was stopped. or The run could not finish after several tries., and error.code carries the code. The other pages still count, so the execution ends partial when some pages succeed. A crawl that found a single page is the exception: that page is the whole run, and SUITE_TIMEOUT ends it. A run whose crawl fails (crossPageExecute: true) ends with status error and error.code CRAWLER_ERROR.

Provider failures

Entries of error.providerFailures, resultsSummary.erroredUrls[].providerFailures, and providerFallbacks describe why one model provider failed. They never contain the request: no prompt, page text, or body.

Success Response (with results, includeResults: true)

When includeResults is true, a results array is included alongside execution:
Per-URL result fields:
Findings are nested under agentResult.findings, not on the result row itself. Read results[i].agentResult.findings. Annotation counts are not reported per URL; use resultsSummary.totalAnnotationsCreated for the run-level total.
Agent result fields (agentResult): Finding fields (AgentFinding):

Finding evidence

evidence shows what a finding rests on, so it can be judged without opening the page. Every key is optional and absent when unknown. The compact form in resultsSummary.findings uses the smaller limits in parentheses. The whole object stays under about 2 KB (1 KB). Token-like strings in text, context, and html are redacted, and evidence never carries cookies, typed form values, or full page HTML.

Failure Response

Errors: NOT_FOUND (Execution not found: {executionId} or Store database not found).