Schema Fields
Get per-field structuring metrics for a schema: unresolved rate, alias fire count, and reference miss rate. Identify fields that need instruction tuning.
Per-field telemetry drills into individual field performance within a schema, computed from the latest run. For each schema field it reports the unresolved_rate (how often the field stayed empty), the alias_fire_count (how many times an alias modifier normalized the value), and the reference_miss_rate (how often reference-data lookups for the field missed). Use it to identify underperforming fields that need instruction tuning, alias additions, or reference-data fixes.
Call this endpoint after reviewing the [Schema Summary](schema-telemetry-summary) to investigate which fields are driving a high aggregate unresolved_rate. The field-level breakdown reveals whether issues are concentrated in a few problematic fields or spread evenly across the schema. For per-field cell-state counts (captured vs. synthesized), use the per_field array in the summary response.
A high reference_miss_rate means values are failing to match your uploaded reference data: check for formatting differences or missing rows in the reference table. A zero alias_fire_count on a field with configured aliases means the aliases never matched, which usually indicates they are stale.
unresolved_rate across runs are strong candidates for adding explicit extraction instructions, configuring a fill strategy (constant, reference, compute), or enriching the field registry with example values./v1/telemetry/schemas/{id}/fieldsResponse
Response fields
Response
{
"data": [
{
"field_name": "invoice_number",
"unresolved_rate": 0.02,
"alias_fire_count": 12,
"reference_miss_rate": 0
},
{
"field_name": "payment_terms",
"unresolved_rate": 0.14,
"alias_fire_count": 0,
"reference_miss_rate": 0.21
}
]
}Errors
Error responses