Run Summary

Get structuring metrics for a single job run: capture hit rate, synthesize rate, tier distribution, and per-field breakdown. Compare runs side by side.

The run telemetry summary returns structuring metrics for a specific job run rather than the latest run of a schema. Use it to inspect the performance of a particular execution, compare two runs side by side, or debug a run that produced unexpected results. The response shape is identical to the [Schema Summary](schema-telemetry-summary).

The typical workflow is to [list your job runs](list-jobs), then call this endpoint with the run UUID to inspect its metrics. When a run produces unexpected accuracy, the telemetry reveals whether the issue is in capture (registry gaps show up as a low capture_hit_rate), synthesis (a high synthesize_rate means heavy LLM dependence), or coverage (a high unresolved_rate).

The schema_id field identifies which schema was used, letting you cross-reference with the schema-level trend and per-field telemetry. To compare two runs, call this endpoint twice with different run IDs and diff the tier_distribution and per_field values. Use the [Schema Trend](schema-telemetry-trend) endpoint when you need the full historical view rather than a point-in-time comparison.

Response

{
  "run_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "schema_id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
  "total_fields": 20,
  "total_records": 100,
  "strategy_distribution": {
    "none": 14,
    "compute": 2,
    "reference": 2,
    "constant": 1,
    "generator": 1
  },
  "tier_distribution": {
    "captured": 1440,
    "extracted": 200,
    "synthesized": 300,
    "unresolved": 60
  },
  "capture_hit_rate": 0.72,
  "synthesize_rate": 0.15,
  "unresolved_rate": 0.03,
  "per_field": [
    {
      "field_name": "invoice_number",
      "unresolved_rate": 0.02,
      "state_distribution": { "captured": 96, "extracted": 2, "unresolved": 2 }
    }
  ]
}

Errors