Parcel Enrich: Full Catalog

How it works

1. Omit both fields and preset to request the entire current Enrich catalog. Nulling both has the same meaning; an empty fields array is invalid. Read the returned field map dynamically without a fixed count or list.
2. For a narrower bundle, send {"lat":40.75,"lng":-73.99,"preset":"terrain"}. One Enrich preset can be combined with individual fields, for example fields: ["owner"], and the server returns their union without duplicates. Enrich presets are separate from Fetch presets.
3. Authenticate with your own Mireye account or API token. Enrich costs $0.02 per parcel before plan discounts, whether selecting a few fields or the full catalog; account rate limits still apply. Set MIREYE_OPERATION_KEY once per operation and reuse it with unchanged inputs after any unconfirmed response. Use a 120-second client timeout and allow for larger responses when requesting every field.
4. Supply either a US address or lat and lng, never both. Check resolved_location and address geocode provenance, then parcel_match.status: only matched runs field calculations. Ambiguous, no_match and unavailable return empty fields; those outcomes are not evidence that requested facts are absent. Never select an ambiguous candidate automatically.
5. For a matched parcel, read analysis_point: point data uses the stored parcel centroid or input fallback, while polygon calculations use the matched boundary. Each returned field contains value, source, confidence and interpretation_hints, plus unit when applicable. Keep unfamiliar field IDs and nested JSON values unchanged.
6. The fields map is sparse: failed fields are always omitted, and null values are retained only for a temporary fixed allowlist of 33 fields. Retained nulls may mean meaningful absence or missing information; read interpretation_hints and related values because a retained null alone does not prove absence. Preserve zero, false, empty strings and empty lists. Do not infer a zero or negative finding from an omitted field. Field status, errors, retryability and partial_failures are internal to standalone Enrich and current Search enriched cells. Historical saved Search responses may still contain detailed outcomes; preserve only the metadata actually returned.
7. The sample below illustrates a response shape, not a live result for the example coordinate. Try your own parcel in the Enrich playground at https://mireye.xyz/dashboard/enrich or https://mireye.xyz/integrate. Choose names from https://docs.mireye.ai/api-reference/enrich-fields; Fetch's /v1/meta/fields catalog describes different selectors.
8. This example shows the no_match outcome: no field calculation ran. A matched response contains available results from the requested catalog, with source names, confidence and hints; omitted fields do not invalidate returned values.

Example response