Mireye

Mireye's pitch is narrow and defensible: an AI agent knows the internet but not the ground, so when a frontier model answers a question about a specific parcel it estimates. Mireye answers from the authoritative record. That distinction is the entire product, and it shows up in the API design. Strengths. Per-field provenance is structural, not decorative — the demo on the homepage returns elevation = 13.03 meters, source = USGS_3DEP_COG, fetched = 2026-07-28, confidence = medium, and /v1/fetch returns the same four attributes for any of 366 typed fields. Typed refusals are the second differentiator: /v1/geocode declines centroid-grade matches rather than guessing, and where a record genuinely does not exist you get absent with the reason plus partial_failures carrying a retryable flag, so a batch of hundreds of addresses survives one bad input. The catalog skews toward infrastructure rather than maps — the docs state the largest layer is utilities and grid (substations, transmission voltage class, interconnection context, water service areas, wastewater plant capacity, fiber), which is the layer that decides whether something can actually get built. Fifteen presets (data_center_siting, solar_siting, grid_interconnect, wildfire_underwrite, flood_risk and others) turn a screening question into a defined field set, and the field-request loop routes a real gap into a queued build that benefits every caller after you. The published credit table makes budgeting possible before you run: a full 135-field data center screen is 135 credits (about 14 cents), enriching 1,000 addresses with geocode plus 20 fields is 21,000 credits, and a month of screening 500 parcels is roughly 13,000 credits. Weaknesses. It is US-only for /v1/ask and /v1/fetch, with drive-time proximity the sole Canada-capable surface, so multi-country portfolios need a second vendor. There is no proprietary risk score and no modeled interpretation — deliberately, per the docs' "What we won't do" — which means the buyer supplies the actuarial or engineering judgment on top of raw cited facts. Access is programmatic: REST endpoints or the MCP server, no point-and-click app. Field requests are HTTP-only today, with an MCP tool planned. Credits reset on the 1st (UTC) and unused credits do not roll over, so spiky workloads park credits on the floor. Where it fits. Insurance underwriting against flood zone, base flood elevation, design wind speed and distance to coast; mortgage and title teams assembling hazard disclosure without an LLM estimate; data center siting analysts screening slope, FEMA flood zone, nearest 345 kV line, substation voltage and status and the county interconnection queue; commercial lenders assessing collateral with slope, flood zone, road access, utility territory and soil shrink-swell class. Mireye's own July 2026 research used it to screen every US meat plant for cold-chain fragility in an afternoon — a good illustration of a portfolio-scale question answered from