Mireye
Mireye is infrastructure for physical-world AI agents, turning any US latitude and longitude into sourced, structured geospatial ground truth. Its Mireye Earth API exposes two HTTP endpoints — POST /v1/fetch for deterministic per-field values and POST /v1/ask for natural-language, citation-backed Q&A — plus GET /v1/meta/fields for a self-describing catalog of 175+ fields across seven layers (terrain, land cover, built environment, utilities and energy, climate and resource, hazards, and parcels and boundaries) and 14 preset bundles. Every value carries provenance: the source identifier, upstream URL, dataset vintage, timestamp, and a confidence rating, sourced from federal agencies (USGS, NOAA, USDA, USFS, FEMA, EPA, EIA, NREL, US Census) and open and commercial datasets (Sentinel-2, Overture Maps, Regrid). Mireye also runs a hosted OAuth 2.1 MCP server (com.mireye/earth) and a local stdio adapter so agents in Claude, Cursor, and custom loops can query the earth as easily as the web. Founded 2026 by Ansh Chokshi and Shashwat Kapoor; Y Combinator S26.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Mireye the way a machine reads it — 22 machine-readable artifacts across 17 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Mireye scores 51.2/100 (developing), with a separate agent-readiness read of 69/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Mireye
Each block below is one kind of artifact we hold for Mireye. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Mireye Ask API
The Ask API from Mireye — 2 operation(s) for ask.
Mireye Ask Site API
The Ask Site API from Mireye — 1 operation(s) for ask site.
Mireye Auth API
The Auth API from Mireye — 1 operation(s) for auth.
Mireye Authorize API
The Authorize API from Mireye — 1 operation(s) for authorize.
Mireye Feature Requests API
The Feature Requests API from Mireye — 1 operation(s) for feature requests.
Mireye Fetch API
The Fetch API from Mireye — 1 operation(s) for fetch.
Mireye Healthz API
The Healthz API from Mireye — 1 operation(s) for healthz.
Mireye Mcp API
The Mcp API from Mireye — 3 operation(s) for mcp.
Mireye Meta API
The Meta API from Mireye — 1 operation(s) for meta.
Mireye Oauth API
The Oauth API from Mireye — 4 operation(s) for oauth.
Mireye Readyz API
The Readyz API from Mireye — 1 operation(s) for readyz.
Mireye Register API
The Register API from Mireye — 1 operation(s) for register.
Mireye Revoke API
The Revoke API from Mireye — 1 operation(s) for revoke.
Mireye Sites API
The Sites API from Mireye — 2 operation(s) for sites.
Mireye Token API
The Token API from Mireye — 1 operation(s) for token.
Mireye Users API
The Users API from Mireye — 5 operation(s) for users.
Mireye .well Known API
The .well Known API from Mireye — 1 operation(s) for .well known.
Scroll within the panel for all 17 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
mireye-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Mireye — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/mireye · machine-readable index on apis.io