Skip to main content
Every Web Search Agent task follows the same three steps: create a run, wait for it to complete, and retrieve the result. This page walks through the full loop. You need an API key from the Nimble Platform and a client:
1

Create a run

Send the task in plain language. agents.run generates an agent with default settings (research mode, high effort) and starts the run asynchronously:
The response contains the run id and the generated agent’s id. Both are needed to poll and fetch the result:
Add an output_schema to the request to get structured JSON back instead of prose. See Dataset Building.
2

Wait for completion

Poll while is_active is true. Alternatively, create the run with enable_events: true and stream GET .../runs/{run_id}/events as server-sent events:
3

Retrieve the result

The output contains the answer and its trust report:
Every [n] maps to a claim in trust.claims, with source URLs, verbatim excerpts, and a confidence grade. See Trust.
Fetching the result while the run is still active returns 409 — keep polling. A failed run returns 422 with error details.

Run lifecycle

Follow-up runs

Every run carries an interaction_id. Pass it as previous_interaction_id on the next run to continue the same task with full context — a follow-up question, a refinement, or a drill-down:

Create a persistent agent

agents.run generates a one-off agent with default settings. For recurring tasks, create a persistent agent with a skill, goals, sources, and a default effort. A persistent agent keeps its memory across runs and improves over time:

Next Steps

Trust

Per-claim citations and confidence grades

Use Cases

Research, Enrichment, and Dataset Building

API Reference

Every endpoint, field, and response