Mireye

Overview

API giving AI agents cited physical-world data by location.

From the official site

Connect your AI Agents to the Real World.

The text above is quoted from this tool’s official website — the vendor’s own words.

Official FAQ

What does Mireye actually do?

Mireye is the physical-world layer for AI agents: sourced data, enrichment, and the tools on top of them. Ask a question in natural language, resolve an address to its canonical parcel, or fetch cited fields at any US coordinate — one API and one MCP server, with a citation attached to every field.

What does it cost?

Credit-based pricing. The free tier is 5,000 credits a month with no card; paid plans start at $19/mo, and no plan bills past its allowance — usage stops rather than running up an overage. Credits are the unit across all endpoints, and the credit price per call type is published on the pricing page.

What region does Mireye cover?

United States for the data catalog, with one exception: drive-time analysis (/v1/proximity) covers the US and Canada. Most of the catalog is US federal (USGS, FEMA, NOAA, USDA, BLM, EPA, EIA and more), with a few open and licensed additions such as Overture and Sentinel-2. Every value carries its own source, so you can always see which one you are relying on.

Where does the data come from?

96 authoritative sources, federal datasets primarily, plus county records and open datasets. Every field in every response returns a source name, a source URL, a fetched_at timestamp, and a confidence level so the agent can pass provenance straight through to the end user or auditor.

How fresh is the data?

It varies by layer. Elevation (USGS 3DEP) is effectively static. FEMA flood maps refresh on FEMA's cadence. USDA cropland updates yearly. Every response includes the fetched_at timestamp so the agent always knows what it is looking at.

What if the field I need doesn't exist?

Order it. Every plan includes field requests — file one and we research, build and validate the field, then notify you when it goes live: permanently, for every future caller. Requests are matched against the catalog first, and honestly rejected when they can't be built.

These questions and answers come from the tool’s own structured data, not written by us.