Skip to main content

Run Summary

Get aggregate structuring metrics for a single job run including strategy distribution, tier funnel, and capture hit rate.

Retrieve structuring telemetry for a specific job run rather than the latest run for a schema. Use this when you need to inspect the performance of a particular execution, compare two runs side by side, or debug a run that produced unexpected results.

The typical workflow is to list runs from your jobs pipeline, then call this endpoint with the run UUID to inspect its metrics. This is especially useful when a run produces unexpected accuracy — the telemetry reveals whether the issue is in capture (registry gaps), synthesis (LLM errors), or strategy selection.

The response includes capture_hit_rate, synthesize_rate, strategy_distribution, and tier_funnel — identical in shape to the Schema Summary. The schema_id field identifies which schema was used, allowing you to cross-reference with field-level telemetry. Runs that are still pending or running return a 404 until they complete.

To compare two runs, call this endpoint twice with different run IDs and diff the strategy_distribution and tier_funnel values. Pair with the Schema Trend endpoint when you need the full historical view rather than a point-in-time comparison.

The response shape is identical to the Schema Summary endpoint. The only difference is that this endpoint targets a specific run by ID instead of returning the latest run for a schema.
GET/v1/telemetry/runs/{id}/summary

Response

Response fields

run_idstringThe job run UUID.
schema_idstringUUID of the schema used for this run.
capture_hit_ratenumberFraction of cells filled via registry capture (0–1).
synthesize_ratenumberFraction of cells filled via LLM synthesis (0–1).
strategy_distributionobjectCount of cells filled per strategy (transfer, extract, compute, skip).
tier_funnelobjectCount of cells resolved per registry tier (tier1, tier2, tier3, unresolved).

Response

{
  "run_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "schema_id": "sch-uuid-1",
  "capture_hit_rate": 0.72,
  "synthesize_rate": 0.18,
  "strategy_distribution": {
    "transfer": 1240,
    "extract": 310,
    "compute": 88,
    "skip": 22
  },
  "tier_funnel": {
    "tier1": 840,
    "tier2": 400,
    "tier3": 200,
    "unresolved": 220
  }
}

Errors

Error responses

401unauthorizedMissing or invalid API key.
404not_foundNo job run with this ID exists for your organization.
429rate_limitedToo many requests. Retry after the period indicated in the Retry-After header.

Related

Schema Summary
Schema Trend