Read groundedness — HTTP

Read the extent to which measured brand mention statements have citation support. Method: GET Path: /projects/{project_id}/runs/{run_id}/groundedness Use the HTTP base for your authorized environment and an Authorization: Bearer header. See authentication and HTTP setup.

Parameters

This table covers the standard read profile. It excludes internal application routes and advanced analysis controls.

Name	Location	Type	Required	Default	Meaning
`project_id`	path	string	Yes	—	Project ID from list_projects. Select the project in the intended workspace and environment.
`run_id`	path	string	Yes	—	Run ID from list_runs for this project. Use the exact returned value and check readiness before reading measurements.
`aggregation_level`	query	string	No	`"bundle"`	entity reports individual names; bundle requests configured brand groupings. Read grouping warnings before treating the result as bundled.
`group_by`	query	string	No	`null`	JSON-encoded array. Split results into rows by the requested dimensions. Check both filters_applied.group_by and each row’s group_by_values before labeling the groups.
`filters`	query	string	No	`null`	JSON-encoded array. Select measured answers with objects containing dimension and values. Use labels from list_dimension_options; inspect returned warnings for filters that were not applied.
`subject`	query	string	No	`null`	JSON-encoded object. Choose brands with kind: leaderboard, all, self, self_and_competitors, or specified. For specified, provide entities_or_bundles. An unmeasured name is not a measured zero.

Request example

Set IQRUSH_API_BASE and IQRUSH_ACCESS_TOKEN through secure configuration. Replace project/run IDs and sample selections with values returned by your account. JSON objects and arrays are encoded as query strings.

curl --fail-with-body --silent --show-error --get \
  --header "Authorization: Bearer ${IQRUSH_ACCESS_TOKEN}" \
  --header "Accept: application/json" \
  --data-urlencode aggregation_level=entity \
  --data-urlencode 'group_by=["platform"]' \
  --data-urlencode 'subject={"kind":"self_and_competitors"}' \
  "${IQRUSH_API_BASE%/}/projects/${IQRUSH_PROJECT_ID}/runs/${IQRUSH_RUN_ID}/groundedness"

Read the response

Measurement rows contain the returned estimate, statement counts such as n_mentions_total and n_mentions_grounded, and additional count or basis fields when available. Use estimate.value. A combined-platform estimate can differ from pooled_rate. Raw occurrences and statement counts are different units. A missing support dataset can make the result unavailable.

Fields to use

These selected fields explain the example and the result to preserve. Field presence depends on the response; this is not a complete response schema.

Field	Meaning and use
`data.rows[].entity_or_bundle`	Measured name or brand grouping.
`data.rows[].group_by_values`	Dimensions identifying the row’s scope.
`data.rows[].estimate`	Groundedness value, interval, and quality. Use the returned estimate rather than recomputing a combined rate from counts.
`data.rows[].n_mentions_total`	Mention-statement count accompanying the result.
`data.rows[].n_mentions_grounded`	Count of those mention statements with citation support.

Selected response fields from IQRush Dev. Lists are shortened and project/run IDs are placeholders; this is not the full response.

{
  "data_ready": true,
  "data": {
    "aggregation_level": "entity",
    "rows": [
      {
        "entity_or_bundle": "Supergoop",
        "group_by_values": {
          "platform": "OPENAI"
        },
        "estimate": {
          "value": 0.625,
          "ci": {
            "lower": 0.453,
            "upper": 0.771,
            "level": 0.95
          },
          "n": 32,
          "stability": "stable",
          "stability_n": 32
        },
        "n_mentions_total": 32,
        "n_mentions_grounded": 20
      }
    ]
  }
}

Read the actual returned scope, counts, and interval levels before interpreting these fields. MCP equivalent: get_groundedness. Use the parameters and defaults on this page for HTTP.

If the result is unavailable

Check HTTP status and the response’s error field before using data. A successful empty response does not establish a zero value. Preserve not_available, not_available_reason, unavailable_reason, and linked where returned. Errors and recovery shows observed examples.

Get started

Connect securely

Read measurements

Build dependable integrations

Build reports

Report recipes

Reference

Session and discovery

Visibility measurements

Sources and evidence

Changes and trends

Google data

Pages and report planning

HTTP operations

Read groundedness — HTTP

Parameters

Request example

Read the response

Fields to use

If the result is unavailable

​Parameters

​Request example

​Read the response

​Fields to use

​If the result is unavailable

Parameters

Request example

Read the response

Fields to use

If the result is unavailable