> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iqrush.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Explore dimensions behind a result — HTTP

> Explore the available dimension-level analysis for a selected domain.

Explore the available dimension-level analysis for a selected domain.

**Method:** `GET`

**Path:** `/projects/{project_id}/runs/{run_id}/factor-analysis`

Use the HTTP base for your authorized environment and an `Authorization: Bearer` header. See [authentication](/developers/guides/04-authentication) and [HTTP setup](/developers/guides/06-http-quickstart).

## 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. |
| `domain` | query | string | Yes | — | Bare domain from the selected run’s citation results, without a scheme or page path. |
| `score_family` | query | string | No | `"citation"` | Use citation; other score families are not supported by this operation in this edition. |
| `metric` | query | string | No | `"share"` | Use share. This operation supports citation share for the selected domain. |
| `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. |

## 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.

```bash theme={null}
curl --fail-with-body --silent --show-error --get \
  --header "Authorization: Bearer ${IQRUSH_ACCESS_TOKEN}" \
  --header "Accept: application/json" \
  --data-urlencode domain=colorescience.com \
  --data-urlencode score_family=citation \
  --data-urlencode metric=share \
  "${IQRUSH_API_BASE%/}/projects/${IQRUSH_PROJECT_ID}/runs/${IQRUSH_RUN_ID}/factor-analysis"
```

## Read the response

Read data.citation\_rate for the domain’s overall citation-share estimate and data.platform\_effects for returned platform contrasts. Each effect carries its own difference interval and significance result.

Only citation/share is supported in this edition. This analysis describes associations in the measured data; it does not establish that changing a page feature will cause an increase.

### 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.domain` | Cited domain being assessed. |
| `data.citation_rate` | Overall citation-share estimate for the selected domain, including its interval. |
| `data.platform_effects[].platform` | Platform for the returned effect comparison. |
| `data.platform_effects[].effect` | Comparison object with value\_a, value\_b, diff, ci\_diff, and significant. It is not a single estimate object. |
| `data.platform_effects[].n_queries` | Query count accompanying that platform result. |
| `data.platform_effects[].significant` | Returned significance indicator for that effect. This is not proof that changing a platform characteristic causes an outcome. |

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

```json theme={null}
{
  "data_ready": true,
  "data": {
    "domain": "colorescience.com",
    "score_family": "citation",
    "metric": "share",
    "citation_rate": {
      "value": 0.026726239624239412,
      "ci": {
        "lower": 0.01989462817126389,
        "upper": 0.03468159681251653,
        "level": 0.95
      },
      "n": 48,
      "stability": "stable"
    },
    "platform_effects": [
      {
        "platform": "OPENAI",
        "effect": {
          "value_a": 0.026726239624239412,
          "value_b": 0.019599303135888493,
          "diff": -0.007126936488350919,
          "ci_diff": {
            "lower": -0.01633275954670247,
            "upper": 0.0004980505381705359,
            "level": 0.975
          },
          "significant": false
        },
        "n_queries": 238,
        "significant": false
      }
    ]
  }
}
```

The interval level is returned with each effect. Preserve it; do not relabel every returned interval as 95%.

MCP equivalent: [`get_factor_analysis`](/developers/tools/get_factor_analysis). 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](/developers/guides/13-errors) shows observed examples.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.