Does the API calculate prompt volatility?

No. Compare repeated news result lists in your own application. The API supplies collected provider outputs; this analysis belongs in your application.

How should failed or empty collections be handled?

Inspect per-target failedRuns and each successful run identity. Empty sources or null fields are valid output; a missing failed run is not an empty successful answer. A completed job can contain failed collections.

Customer-built analysis

Google News: prompt volatility

Compare repeated news result lists in your own application.

Collection target: google_news. This is customer-built analysis, not a computed API response field.

Build this analysis in your application

Compare article URLs, publishers and snippets across successful news collections. Declare how you handle empty lists, duplicate articles and changing publication labels; failed collections are not changes in news coverage.

Customer-built analysis

The API returns individual successful runs and failedRuns, not volatility scores or recommended sample sizes. Failed collection is not evidence that an answer changed.

The google_news target returns googleNews.results and googleNews.topNews. Article fields include title, url, snippet, publisher, position and publishedAt. Publication labels are provider text, such as 2 hours ago, not normalized timestamps. News collections can contain empty lists. Google Search and Google News share a task when requested together, while each target has its own outputs and failedRuns count.

Collected input for your analysis

These are illustrative successful run excerpts, not full result files or calculated metrics. Submit POST /v1/crawl-jobs, track completion, then download the authenticated result. Outputs depend on the target; a chatbot has no news articles or Google position fields.

{
  "runNumber": 1,
  "runTaskId": "53b39f0d-9576-44d6-a796-45dbfbfcdbf3",
  "status": "completed",
  "capturedAt": "2026-10-09T10:01:00.000Z",
  "pageUrl": "https://www.google.com/search?q=example&tbm=nws",
  "googleNews": {
    "results": [
      {
        "position": 1,
        "publishedAt": "2 hours ago",
        "publisher": "Example Publisher",
        "snippet": "Illustrative article summary.",
        "title": "Illustrative article title",
        "url": "https://example.com/article"
      }
    ],
    "topNews": []
  }
}

Illustrative provider output. Empty lists and null fields are valid; inspect failedRuns in the result file.

Full result format and failed-run handling →

Prompt volatility FAQ

Does the API calculate prompt volatility?: No. Compare repeated news result lists in your own application. The API supplies collected provider outputs; this analysis belongs in your application.
How should failed or empty collections be handled?: Inspect per-target failedRuns and each successful run identity. Empty sources or null fields are valid output; a missing failed run is not an empty successful answer. A completed job can contain failed collections.

Use collected data to build your own reporting and analysis. Our team arranges API access and follows up with next steps.

Request API access Read the docs