Prompt volatility

Build this analysis in your application

Repeated collections can help measure changes in text, brand presence and source overlap. For example, Jaccard similarity compares the intersection and union of two source sets; decide how to handle two empty sets before aggregating.

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": "7f5c0888-f5ad-4661-b07b-79fbbe1c7b31",
  "status": "completed",
  "capturedAt": "2026-10-09T10:01:00.000Z",
  "pageUrl": "https://www.google.com/search?q=example",
  "aioverview": null,
  "serp": {
    "organic": [
      {
        "position": 1,
        "snippet": "Illustrative search result summary.",
        "title": "Illustrative CRM comparison",
        "url": "https://example.com/crm-comparison"
      }
    ],
    "peopleAlsoAsk": [],
    "shopping": [],
    "sponsored": []
  }
}

Prompt volatility FAQ

Does the API calculate prompt volatility?

No. Compare repeated answers and source sets 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.