← All templates
Agent ToolSite diligence
Parcel Enrich: Selected Fields
A complete Agent Skill — copy it and drop it into your agent’s skills folder as parcel-enrich-selected/SKILL.md and it can run this recipe on its own.
Investigate one parcel with a small field selection and preserve each returned value's source, confidence and hints.
Selected fieldsOne parcel
Open in playgroundHow it works
- Send POST /v1/enrich with fields: ["owner", "slope_degrees"] for a small first review. fields always contains individual Enrich IDs; selecting a bundle uses the separate preset parameter. This sample omits owner because no owner value was available.
- 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.
- 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.
- 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.
- 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.
- 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.
Example response
- lat
- 40.75
- lng
- -73.99
- resolved_location
- lat
- 40.75
- lng
- -73.99
- source
- coordinate
- analysis_point
- lat
- 40.7501
- lng
- -73.9898
- method
- stored_parcel_centroid
- source
- parcel.centroid_lat/centroid_lon
- parcel_match
- status
- matched
- parcel
- parcel_id
- example-parcel
- apn
- 000001
- address
- 100 EXAMPLE ROAD, EXAMPLE CITY, NY
- source
- parcel_vendor
- match_type
- exact_intersect
- match_distance_m
- 0
- candidates
- —
- reason
- null
- fields
- slope_degrees
- 12.5 degrees — USGS_3DEP
Get a Mireye API key at mireye.com/account.