← All agent tools

Location & land data Mireye

Mireye API + hosted MCP

Look up cited US location and parcel information, with separate services for basic retrieval and paid enrichment.

Source review: 2026-10-22 · Imported: 1 November 2026

A practical starting point

What could you build?

A property research assistant can start with public fields at a coordinate and request more detail only when needed.

Before you connect

Keep free Fetch separate from billable enrichment and search. Preserve citations and confirm important parcel details with the original records.

Capabilities & requirements

Dated specifications from the licensed source dataset. “Not published” indicates missing information, rather than confirmed absence.

Mireye API + hosted MCP specifications
CapabilityDetails and source
StatusNot published

No beta or GA label in the docs or pricing, and no published SLA; the local MCP adapter and the Lookup and Resolve endpoints are retired.

Source (external) · Not published by vendor: checked 2026-10-22 on https://docs.mireye.ai/mcp/installation.md
API key requiredAPI key or OAuth (account)

Keyless POST /v1/fetch returned HTTP 401 auth_missing; the MCP returned 401 with an OAuth challenge. Free Fetch still needs a key.

Source (external) · Verified 2026-10-22 on https://docs.mireye.ai/authentication.md
Free tierFree Fetch + $10 once

Fetch, batch Fetch and Geocode are free on every plan; a one-time $10 balance (no expiry, no card) covers paid Enrich, Search and Ask.

Source (external) · Verified 2026-10-22 by test request to https://api.mireye.com/v1/meta/plans
Rate limit20/min Free, 60 Build, 300 Growth

rate_limit_rpm in the public plans contract; limits apply to free calls too. 429 with Retry-After.

Source (external) · Verified 2026-10-22 by test request to https://api.mireye.com/v1/meta/plans
Official MCP serverHosted, api.mireye.com/mcp

Streamable HTTP with OAuth 2.1 + PKCE; nine tools. The old local adapter is retired.

Source (external) · Verified 2026-10-22 on https://docs.mireye.ai/mcp/installation.md
Official SDKREST + OpenAPI; setup helper

An OpenAPI schema is published at api.mireye.com/v1/openapi.json; the mireye-mcp helper only configures clients. No client SDK is listed.

Source (external) · Verified 2026-10-22 on https://www.mireye.com/llms.txt
Data license / termsProprietary; parcel data restricted

Licensed parcel data cannot be resold, published, exposed via your own app or API, or used for model training without written authorization. Public fields keep their source terms.

Source (external) · Verified 2026-10-22 on https://www.mireye.com/terms
Commercial use allowedBusiness use; no redistribution

Outputs may be used for your own property research and business work; making licensed parcel data available to others needs written authorization.

Source (external) · Verified 2026-10-22 on https://www.mireye.com/terms
CORS / browser useAccess-Control-Allow-Origin: *

GET /v1/meta/plans with a third-party Origin returned *, and the preflight for POST /v1/fetch with X-API-Key returned 200 with *. Do not expose a key in browser code.

Source (external) · Verified 2026-10-22 by test request to https://api.mireye.com/v1/meta/plans
Freshness / coverageUS; 351 free Fetch fields

351 fields in 15 presets from GET /v1/meta/fields on 2026-10-22; freshness varies by source and each value carries fetched_at.

Source (external) · Verified 2026-10-22 by test request to https://api.mireye.com/v1/meta/fields

Operational reference

Additional facts and qualifications retained from AgentAPIList’s CC BY 4.0 dataset, with provider references.

Price

Fetch, batch Fetch, Geocode and field requests are free on every plan. New accounts get a one-time $10 balance with no expiry and no card. Free-plan rates: Enrich $0.02 per enriched parcel, Search $0.20 per page, driving distance $0.02 per calculation, Ask $0.10 per answer. Build is $49/month and Growth $199/month, each including the same amount of usage at lower Enrich, Search and driving rates. Our keyless GET /v1/meta/plans on 2026-10-22 returned these figures.

Provider reference (external)

API key / auth

An account is required even for free Fetch. Direct HTTP calls send X-API-Key with a key created in the dashboard after signing in and accepting the terms (new keys start with mry_). The hosted MCP uses OAuth 2.1 with PKCE. On 2026-10-22 our keyless POST /v1/fetch returned HTTP 401 auth_missing, and the MCP endpoint returned 401 with an OAuth resource-metadata challenge.

Provider reference (external)

Rate limit

20 requests a minute on Free, 60 on Build and 300 on Growth (rate_limit_rpm in /v1/meta/plans). Limits apply to free operations too, and adding funds does not raise them; over the limit you get HTTP 429 with Retry-After. Batch Fetch takes up to 25 locations per request.

Provider reference (external)

Terms

Mireye Earth Customer Terms (version 2026-10-20-v1): outputs may be used for your own property research and business work, including through AI agents. Licensed parcel data (ownership, boundaries, assessor records) may not be resold, published, exposed through your own customer-facing app or API, aggregated into a substitute dataset or used to train AI models without Mireye’s written authorization. Public fields stay under their own source terms.

Provider reference (external)

Endpoint

REST base https://api.mireye.com (POST /v1/fetch, /v1/fetch/batch, /v1/geocode, /v1/enrich, /v1/search, /v1/ask, /v1/proximity). Hosted MCP: https://api.mireye.com/mcp over Streamable HTTP with OAuth, nine tools (mireye_fetch, mireye_geocode, mireye_enrich, mireye_search, mireye_ask, mireye_proximity, mireye_request_field, mireye_field_request_status, mireye_list_fields).

Provider reference (external)

Coverage

United States; drive-time calculations also cover Canada. The free Fetch catalog listed 351 fields in 15 presets on 2026-10-22 (keyless GET /v1/meta/fields); the MCP docs say Enrich can return 525 fields. Not verified: the 160M+ parcel count and “550 data fields” in the founder’s launch post, which we did not find in Mireye’s docs.

Provider reference (external)

Status

No beta or GA label in the docs or pricing, and no published SLA. The product is changing quickly: the local MCP adapter, Lookup and Resolve endpoints are retired and now return migration errors.

Provider reference (external)

Setup references

HTTP request example

Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.

# Run without a key on 2026-10-22: the public pricing contract
curl -sS https://api.mireye.com/v1/meta/plans

# Not run: free Fetch needs a key from a Mireye account
curl -sS -X POST https://api.mireye.com/v1/fetch \
  -H "X-API-Key: $MIREYE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"lat":39.0438,"lng":-77.4874,"fields":["elevation","slope_degrees","within_floodplain_polygon"]}'
Agent connection example

Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.

// Claude Code (then run /mcp and finish browser sign-in):
//   claude mcp add --transport http --scope user mireye-earth https://api.mireye.com/mcp
// Cursor .cursor/mcp.json (remote server with OAuth)
{
  "mcpServers": {
    "mireye-earth": { "url": "https://api.mireye.com/mcp" }
  }
}
// Direct HTTP: send X-API-Key: mry_... (never put the key in a URL)

A tool schema needs an HTTP implementation; it does not by itself install an MCP server. Keep credentials out of browser code.

Other connections to explore

Back to the full directory →

Source & reuse

Download the complete licensed source snapshot (JSON), including the original source’s caveats, alternative notes and examples.