Mireye MCP server for AI agents

Enrich one US parcel with selected parcel attributes, point data and polygon calculations. Give either address or lat+lng inside req. Fields and a list of Enrich presets combine by union; omit both to request all Enrich fields. Prefer a small explicit selection. Call mireye_list_fields with endpoint="enrich" for the Enrich catalog; Fetch has a different field set. Inspect parcel_match.status first: only matched returns fields. An address selects a parcel only from a rooftop-precision geocode; otherwise parcel_match is no_match with a reason, and nothing is charged. Never choose an ambiguous candidate automatically. Point data uses the parcel analysis point; polygon calculations describe its boundary. Fields are sparse: omitted fields do not establish a negative finding. Costs $0.02 per successful parcel on Free, with paid-plan discounts; charged only when at least one requested field is returned. Accept current terms and reconnect first. Use a stable idempotency_key for retries and max_cost_usd for a dollar ceiling. An empty fields map, no-match, ambiguous and unavailable results cost zero. At capacity it returns retryable enrich_busy. Fields form a flat map in Enrich preset order, preserving each preset field order; shared fields appear once at their first preset and unassigned fields follow in catalog order. Each field contains value, source, confidence, interpretation_hints, and unit when available. Failed fields are omitted. The fields map may be empty. Read hints before interpreting nulls.

Fetch free public data fields at a US coordinate or address. Give either lat+lng or address. Each field includes its value, source, source URL, timestamp, confidence and status: ok, absent, or failed. Never treat a failed field as valid no-data; retry with backoff when retryable. Parcel identity, ownership, boundaries and parcel-dependent calculations require mireye_enrich. Presets contain only eligible public fields. Authentication, rate limits and capacity limits apply; Fetch never deducts from the dollar balance. An address result includes geocode quality; an estimated street location may describe a neighboring property. Inspect parcel_grade and accuracy_type: range_interpolation is an estimate, not a rooftop match and can be about 2.9 km off in rural areas. State the precision_note before making parcel-specific claims.

Poll the status of a field request filed with mireye_request_field: status, queue position, the promised estimated_ready_at (fixed at acceptance, never recomputed on poll), and -- once status is 'live' -- the resume call (a ready-to-send /v1/fetch request) that answers the original ask. Store request_id in durable task state, not conversation context: builds run on a scale of hours and the filing session will likely be gone before one finishes. Status vocabulary: 'received'/'screening' (still being screened; check waiting_on -- 'operator' means screening failed and a human has to look), 'matched' (the catalog already answered it, use resume), 'awaiting_confirm' (a near-miss or clarify needs you), 'rejected' (typed codes in disposition, terminal), 'queued'/'claimed'/'building'/'in_review'/'approved'/'publishing' (a build is in progress), 'live' (done, resume works now), 'blocked'/'expired' (terminal, no build). Requests are visible only to the credential that filed them; an id that doesn't exist -- or belongs to someone else -- is the same 404, never a 403 (a 403 would confirm the id exists).

Resolve a US street address to a coordinate, with the quality of that coordinate. Feed lat/lng to mireye_fetch or mireye_ask. ALWAYS check accuracy_type before trusting the result: 'rooftop' is on the parcel, but 'range_interpolation' is estimated along a street centerline and can be ~2.9 km out in rural areas, far enough to describe a neighbouring property instead. An address that can only be placed at a ZIP/city/county centroid is REJECTED as address_too_coarse rather than returned, if you get that, ask the user for a more complete address instead of retrying. The address you send is retained alongside the coordinate it resolves to, so a result can be audited later; pass lat/lng instead if that does not suit the caller.

List the field names a Mireye tool accepts, with type, unit, description, interpretation hints, null meaning and source. endpoint=fetch lists mireye_fetch fields and presets; endpoint=enrich lists mireye_enrich fields, presets and price; endpoint=search lists mireye_search names with filter_ops (operators allowed in filters; empty means output-only), returnable (allowed in fields) and price. Each tool has its own list: a name valid for one may be unknown to another. Use query to narrow by a case-insensitive substring of the name or description, for example query="flood". Free; never charged.

Compute distance, nearest candidates, screening or labor sheds. Straight-line work and estimates are free; driving uses the active plan's per-calculation USD rate. Send max_cost_usd as a decimal string to bound spending and a stable idempotency_key for retries. Check resolved locations, geocode precision, unreachable legs and missing tracts. If you infer a missing city or substitute a coordinate, state that assumption to the caller.

Ask Mireye for a data field it doesn't have yet, in plain language, at one or more example locations. If the catalog already answers it you get the value now with a citation (disposition 'matched_existing'/'partial') and never spend a build; if something close exists you get 'near_miss_confirm' to accept or reject; otherwise the field is queued to build and you get a request_id to poll with mireye_field_request_status. ALWAYS pass idempotency_key for agent-originated requests: the same key replays the existing request's state instead of filing a second build. Answering use_case/decision_threshold (what decision this feeds, and the value that flips it) is optional but sharply improves match quality and build speed. example_locations (1-10 entries) each carry exactly one of address, lat+lng, or polygon, plus optional claimed_value/note -- see docs.mireye.ai/api-reference/field-requests for the full entry shape. requested_fields optionally pre-splits a bundled ask into atomic sub-questions (plain-language asks); the server decomposes bundles anyway. extra carries the rarer structured fields verbatim (area_of_interest, expected_volume, freshness, constraints, known_sources, output_preference) -- same doc has their shapes. A 'rejected' disposition carries a typed rejection_code and routing_hint, never a bare no; a genuinely ambiguous location returns a stateless 'clarify' with candidates instead of guessing. Filing a field request is free; request and build capacity limits still apply.

Find the first parcels satisfying ALL conditions, not ranked top matches. Include state2 with eq or a nonempty in list of two-letter US state codes (50 states and DC). County is optional. Every filter is applied exactly, including geometry and calculated-field filters. Address filters match the parcel's recorded situs address. Point-sampled fields use the matched parcel's recorded latitude and longitude unchanged; a candidate without a valid recorded point is not checked and is reported in remarks. Each match returns identity plus one flat fields map: scalar filter values and every field named in fields, excluding information already represented by identity. fields accepts any public Enrich field, including parcel attributes and parcel calculations, plus the geometry outputs geometry, parcel_geometry_wkt and parcel_boundary_geojson. GET /v1/search/fields lists every name with its filter operators. Missing values remain null. Search costs $0.20 per completed query on Free, including valid zero matches and every requested field; active plan discounts apply. Each continuation page is a new query. Returns 10 matches per page by default, up to 100. next_cursor is the only signal that more pages may exist: null means this is the last page, and a short or empty page can still carry a cursor. Send next_cursor with unchanged filters and fields; page size and max_cost_usd may change. Use a new idempotency key for each page. remarks is always present and empty when the page is clean; each remark has a code and a message, and may add path, hint, candidates or matches. Branch on code and path only: time_limit_reached (the time limit cut this page short), source_unavailable (parcel data became unavailable partway through; returned matches are correct), candidates_not_checked (some candidates could not be checked, so a match may be missing) and field_unavailable (a requested field, named by path such as fields[0], could not be produced for some matches and is null there). Use max_cost_usd as a decimal-string ceiling and a stable idempotency key for retries. Absent values fail hard filters; a page with remarks cannot establish no-match. Point samples describe the point, not the entire parcel. Geometry filters use WGS84 GeoJSON Polygon/MultiPolygon and do not automatically return boundaries. Output describes the exact matched parcel. Each page has a 180-second time limit; allow at least 210 seconds on the client.