Mireye connector for AI agents

Tools your location agent reaches for on Mireye, scoped per user.

CALL ANY TOOL

API key location data across 21 Mireye tools: geocode, free public fields, parcel enrich, and drive-time proximity on the signed-in user's key.

mireye_address_geocode

Geocode Address

Resolve a US street address to a coordinate and report how precise that coordinate is. Returns lat, lng, accuracy, accuracy_type (rooftop, or range_interpolation, which can be off by about 2.9 km in rural areas), match_type, normalized_address, provider, source, parcel_grade and precision_note. Use mireye_address_geocode to check or reuse a coordinate before calling other tools with lat and lng. mireye_location_fetch, mireye_location_ask and mireye_parcel_enrich also accept an address directly and return the same geocode block. Free.

Parameters

Name

Type

Required

Description

address

string

Required

A full US street address to turn into a coordinate, 1 to 256 characters, with house number, street, city and state or ZIP. A bare street with no locality, or an address the geocoder can only place at a ZIP, city or county centroid, is rejected with 404 address_too_coarse. Example: 350 5th Ave, New York, NY 10118.

mireye_enrich_fields_list

List Enrich Fields

mireye_fetch_fields_list

List Fetch Fields

mireye_field_request_get

Get Field Request

mireye_location_fetch

Fetch Location Data

Fetch free public data fields for one US coordinate or street address, such as elevation, flood zone, wetlands, terrain, land cover and distance to nearby infrastructure. Returns each field with its value, unit, source, source_url, confidence and status, plus partial_failures for fields that failed, resolved_location, and a geocode block when you sent an address. Use mireye_location_fetch when you know which fields you need. Use mireye_location_ask for a plain-language question, mireye_parcel_enrich for parcel data such as owner, zoning or boundaries, and mireye_run_create for up to 25 locations at once. Free on every plan and usually answers in seconds, but satellite-imagery fields can take up to 60 s and road or building fields up to 35 s; submit those through mireye_run_create. Pick field names or a preset from mireye_fetch_fields_list.

Parameters

Name

Type

Required

Description

address

string

Optional

A full US street address to fetch data for (house number, street, city, state and ZIP), 1 to 256 characters. Mireye geocodes it first and returns a geocode block with the match quality. Use this instead of lat and lng; never send both. A bare street with no city or ZIP is rejected as too coarse. Example: 350 5th Ave, New York, NY 10118.

fields

array

Optional

Catalog field names to fetch at the location, from mireye_fetch_fields_list. Send fields, preset or both (the preset expands first and these are added to it). At most 50 fields outside the chosen preset. Parcel fields such as owner, zoning or boundaries are not free and are rejected here; use mireye_parcel_enrich for those. Example: ["elevation", "coast_distance_m"].

lat

number

Optional

Latitude of the US point to fetch data for, in decimal degrees (WGS84). Send lat and lng together, or send address instead; never both. Example: 40.7128.

lng

number

Optional

Longitude of the US point to fetch data for, in decimal degrees (WGS84, negative in the western hemisphere). Send lat and lng together, or send address instead; never both. Example: -74.006.

preset

string

Optional

A named bundle of fields to fetch, for a common use case. For example flood_risk returns elevation, floodplain, wetland and surface-water fields, and terrain returns elevation, slope, aspect, coast distance, soil drainage and bedrock depth. mireye_fetch_fields_list lists each preset's fields. Send fields, preset or both. Example: flood_risk. One of: `terrain`, `flood_risk`, `wildfire_underwrite`, `land_cover`, `site_selection`, `building_lookup`, `points_of_interest`, `utilities`, `boundaries`, `solar_siting`, `wind_siting`, `storage_siting`, `data_center_siting`, `grid_interconnect`, `natural_hazard`.

mireye_operation_get

Get Paid Operation

mireye_plans_list

List Plans and Prices

mireye_run_get

Get Run

mireye_search_fields_list

List Search Fields

mireye_site_get

Get Site

mireye_field_request_create

Request a New Field

Ask Mireye for a US location data point that its catalog may not have yet, described in plain language with example locations. Returns request_id, status (matched, awaiting_confirm, queued or rejected), and a disposition per sub-ask: an existing field with a sample value and the exact fetch call (resume) that answers it, a near-miss to confirm, a queued build with queue_position and estimated_ready_at, or a typed rejection with a routing hint. Use mireye_field_request_create when mireye_fetch_fields_list has no field for what you need. Then poll mireye_field_request_get; builds take hours. Free. Screening usually finishes within about 10 s; if not, Mireye returns status received and the outcome appears on the next poll.

Parameters

Name

Type

Required

Description

description

string

Required

Describe the data point you need in plain language, 1 to 8,000 characters: what the data is, what decision it feeds, and what a good answer looks like. Example: FEMA flood zone designation for a parcel I am screening for a warehouse.

example_locations

array

Required

1 to 10 US locations where you need the value. Each entry gives exactly one of: an address (a US street address), lat and lng, or polygon (a GeoJSON Polygon or MultiPolygon, for answers that depend on the parcel boundary rather than a point). Each entry may also carry claimed_value, what you believe the answer is there, and note, why the location matters. Unknown keys are rejected. Example: [{"address": "480 Berdoll Ln, Cedar Creek, TX 78612", "note": "Candidate site we are screening"}].

area_of_interest

object

Optional

Where you need coverage now: level is one of city, county, state, region or national, and names lists up to 50 places. Example: {"level": "county", "names": ["Bastrop County, TX"]}.

callback

object

Optional

Optional notification targets: webhook_url (up to 2,000 characters) receives JSON events, and email (up to 320 characters) receives the same news. Polling with mireye_field_request_get is the primary channel. Example: {"email": "analyst@example.com"}.

constraints

object

Optional

Lists of up to 20 strings each: must_not_be names data sources or fields you have already ruled out, so they are not offered back; already_have names fields you already have; acceptable_substitutes names alternatives that would also work. Example: {"must_not_be": ["within_floodplain_polygon"], "already_have": ["elevation"]}.

context_blob

string

Optional

An opaque string up to 8 KB (UTF-8 bytes), echoed back unchanged in every status response and callback. Put whatever a later agent needs to resume the task. Example: {"job":"site-screen-114"}.

deadline

string

Optional

When the answer stops being useful, as an ISO 8601 date or date-time, up to 64 characters. Example: 2026-12-31.

decision_threshold

string

Optional

The value at which your decision flips, up to 2,000 characters. If you only need to know which side of a line the answer falls on, say the line; Mireye can often answer the decision faster than the field. Example: Inside or outside the 1% annual chance floodplain.

expected_volume

object

Optional

How much you will use the field: locations is how many locations you will query (a whole number), geography is where they cluster (up to 200 characters), and cadence is one_off or recurring. Example: {"locations": 500, "geography": "Central Texas", "cadence": "recurring"}.

freshness

object

Optional

How fresh the data must be: max_staleness is the oldest data that still answers your question, as an ISO 8601 duration, and changes_how_often says how often the real value changes (up to 500 characters). If the useful life is under about a day, Mireye says at once that it cannot index it. Example: {"max_staleness": "P2Y", "changes_how_often": "When FEMA revises its maps"}.

idempotency_key

string

Optional

A key you choose for this request, up to 255 characters. Sending the same key again returns the existing request's state instead of filing a second build; reusing it with a different request returns 409 idempotency_key_reused. Strongly recommended for agents. Example: fr-flood-zone-bastrop-0001.

known_sources

object

Optional

Data sources you know about: suggested and excluded are lists of up to 10 sources, each with a name, url, note and why. They are hints, not commands; Mireye still verifies every source. Example: {"suggested": [{"name": "FEMA NFHL", "url": "https://hazards.fema.gov/femaportal/wps/portal/NFHLWMS"}]}.

output_preference

object

Optional

The answer shape you want: value_kind is one of boolean, category, number, distance or geometry; units is a unit name (up to 100 characters); buckets_ok says whether coarse ranges such as under 5k, 5k to 15k, over 15k are enough. Example: {"value_kind": "category", "buckets_ok": true}.

requested_fields

array

Optional

Optional split of a bundled request into up to 20 atomic asks, each in plain language (up to 1,000 characters) and never a Mireye field ID. Mireye splits bundles itself, so this is only a hint. Example: ["FEMA flood zone code", "Distance to the nearest wetland"].

use_case

string

Optional

What decision the value will feed, and what changes at different values, up to 4,000 characters. Example: Deciding whether to make an offer; anything in a 100-year floodplain is a no.

mireye_location_ask

Ask About a Location

Ask a plain-language question about one US coordinate or street address and get a cited answer. Returns answer (prose, with a precision caveat when an address was only estimated), confidence (high, medium or low), citations (source, source_url, fields and fetched_at per source), fields_used, data_gaps (requested fields with no value, and why), resolved_location and billing. Use mireye_location_ask when the question needs fields combined and interpreted. Use mireye_location_fetch for known fields (free) and mireye_site_ask for an area. Costs $0.10 per completed answer on every plan; incomplete answers are free. Mireye documents typical answers in 6 to 20 s and up to 110 s; a call that runs past the tool-call time limit fails here but keeps running at Mireye, so call again with the same idempotency_key and identical inputs to collect the saved result without a second charge.

Parameters

Name

Type

Required

Description

idempotency_key

string

Required

A key you choose for this question, 8 to 128 letters, digits, hyphens or underscores. Mireye keeps working after the caller disconnects: if this call times out or the response is lost, call again with the same key and identical inputs to collect the saved result without a second charge. Use a new key for new work. Reusing a key with different inputs returns 409 idempotency_conflict. Example: ask-2026-10-22-a1b2c3d4.

question

string

Required

A plain-language question about the location, 1 to 2,000 characters. Example: Is this location in a flood zone, and what is the wildfire risk?

address

string

Optional

A full US street address to ask about (house number, street, city, state and ZIP), 1 to 256 characters. Mireye geocodes it first and returns a geocode block with the match quality. Use this instead of lat and lng; never send both. A bare street with no city or ZIP is rejected as too coarse. Example: 350 5th Ave, New York, NY 10118.

lat

number

Optional

Latitude of the US point to ask about, in decimal degrees (WGS84). Send lat and lng together, or send address instead; never both. Example: 40.7128.

lng

number

Optional

Longitude of the US point to ask about, in decimal degrees (WGS84, negative in the western hemisphere). Send lat and lng together, or send address instead; never both. Example: -74.006.

max_cost_usd

string

Optional

Optional spending ceiling in US dollars for this answer, as a decimal string with up to 6 decimal places. Mireye reserves the price before it starts and refuses the request with 402 if the price exceeds this ceiling or the available balance; unused reservation is released. Example: "0.10".

mireye_parcel_enrich

Enrich Parcel

Match one US address or coordinate to a parcel and return the parcel attributes and site data you choose, such as owner, zoning, assessed value, flood, wetlands, power and terrain. Returns resolved_location, analysis_point, parcel_match (status matched, ambiguous, no_match or unavailable, with the parcel or candidates and a reason), fields (each with value, unit, source, confidence and interpretation_hints), a geocode block for addresses, and billing. Use mireye_parcel_enrich when you have one location and need parcel data with sources. Use mireye_parcels_search to find parcels by criteria and mireye_location_fetch for free public data. Check parcel_match.status first and never pick an ambiguous candidate yourself. An address selects a parcel only at rooftop precision. Costs $0.02 per enriched parcel on the Free plan ($0.018 Build, $0.015 Growth); no-match, ambiguous and empty results are free. Mireye documents no typical latency and advises allowing 210 s; a call that runs past the tool-call time limit fails here but keeps running at Mireye, so call again with the same idempotency_key and identical inputs to collect the saved result without a second charge. Pick field IDs or presets from mireye_enrich_fields_list.

Parameters

Name

Type

Required

Description

idempotency_key

string

Required

A key you choose for this enrichment, 8 to 128 letters, digits, hyphens or underscores. Mireye keeps working after the caller disconnects: if this call times out or the response is lost, call again with the same key and identical inputs to collect the saved result without a second charge. Use a new key for new work. Reusing a key with different inputs returns 409 idempotency_conflict. Example: enrich-2026-10-22-a1b2c3d4.

address

string

Optional

A full US street address to enrich (house number, street, city, state and ZIP), 1 to 256 characters. Mireye geocodes it first and returns a geocode block with the match quality. Use this instead of lat and lng; never send both. A bare street with no city or ZIP is rejected as too coarse. Example: 350 5th Ave, New York, NY 10118.

fields

array

Optional

Enrich field IDs to return for the matched parcel, from mireye_enrich_fields_list. Combined with preset; each field is returned once. If you send neither fields nor preset, all 525 fields are returned, which is slow and large, so start small. Example: ["owner", "zoning", "slope_degrees"].

lat

number

Optional

Latitude of the US point to enrich, in decimal degrees (WGS84). Send lat and lng together, or send address instead; never both. Example: 40.7128.

lng

number

Optional

Longitude of the US point to enrich, in decimal degrees (WGS84, negative in the western hemisphere). Send lat and lng together, or send address instead; never both. Example: -74.006.

max_cost_usd

string

Optional

Optional spending ceiling in US dollars for this parcel, as a decimal string with up to 6 decimal places. Mireye reserves the price before it starts and refuses the request with 402 if the price exceeds this ceiling or the available balance; unused reservation is released. Example: "0.02".

preset

array

Optional

One or more Enrich presets (named field bundles) to return, always as a list, combined with fields. mireye_enrich_fields_list lists each preset's fields. Example: ["terrain", "zoning"].

mireye_parcels_search

Search Parcels

Find US parcels that match all of your filters, such as state, county, acreage, zoning or a polygon, with the fields you choose for each match. Returns matches (each with parcelnumb, address, state2, county, scity, pvd_gisacre, source, analysis_point and a fields map), next_cursor (null on the last page; a short or empty page can still have one), remarks, request_id and billing. Matches are the first found, not ranked. Use mireye_parcels_search when you have criteria and need parcels. Use mireye_parcel_enrich when you already have one address or coordinate. Costs $0.20 per query on the Free plan ($0.18 Build, $0.15 Growth), including zero-match queries; each page is a new query. Mireye documents a time limit of up to 180 s per page; a call that runs past the tool-call time limit fails here but keeps running at Mireye, so call again with the same idempotency_key and identical inputs to collect the saved result without a second charge. Check filter names and operators with mireye_search_fields_list.

Parameters

Name

Type

Required

Description

filters

array

Required

Conditions every matching parcel must meet, each an object with field, op and value. Must include a state2 filter with op eq and a two-letter state code, or op in and a list of codes (50 states and DC). Operators: eq and ne take one value; in takes a non-empty list; lt, lte, gt and gte take one number or date; between takes [low, high]; intersects and within take a GeoJSON Polygon or MultiPolygon and apply only to the geometry field. Send numbers and booleans as JSON values, dates as YYYY-MM-DD, and never null. county takes a five-digit FIPS string such as "04013" or a county name; pvd_gisacre is parcel area in acres. mireye_search_fields_list lists every name and its operators. Example: [{"field": "state2", "op": "eq", "value": "AZ"}, {"field": "pvd_gisacre", "op": "between", "value": [100, 1000]}].

idempotency_key

string

Required

A key you choose for this search page, 8 to 128 letters, digits, hyphens or underscores. Mireye keeps working after the caller disconnects: if this call times out or the response is lost, call again with the same key and identical inputs to collect the saved result without a second charge. Use a new key for new work, including each new page. Reusing a key with different inputs returns 409 idempotency_conflict. Example: search-2026-10-22-page1.

cursor

string

Optional

The next_cursor from the previous page, to get the next page. Keep filters and fields unchanged, and use a new idempotency_key for each page. Cursors expire after one hour. Example: eyJ2IjoxLCJrIjoi.

fields

array

Optional

Names to return for every match: any Search name, any Enrich field ID, or the geometry outputs geometry, parcel_geometry_wkt and parcel_boundary_geojson. Values of your scalar filters are returned too. Every field is included in the query price. Example: ["owner", "zoning"].

limit

integer

Optional

Matches per page, 1 to 100. A larger value is rejected, not reduced. Defaults to 10. Example: 10. Default: `10`.

max_cost_usd

string

Optional

Optional spending ceiling in US dollars for this query, as a decimal string with up to 6 decimal places. Mireye reserves the price before it starts and refuses the request with 402 if the price exceeds this ceiling or the available balance; unused reservation is released. Example: "0.20".

mireye_proximity_distance

Compute Drive Distances

Compute driving or straight-line distance and duration for every origin and destination pair, in the US and Canada. Returns legs (origin_index, destination_index, distance_miles, distance_km, duration_seconds, duration_minutes, and flag unreachable_or_snapped when no real road route exists), resolved_origins, resolved_destinations, paid_driving_calcs, notes and billing. A destination that fails to resolve is left out of legs and named in notes, so read notes before summarizing. Use mireye_proximity_distance for a distance matrix. Use mireye_proximity_nearest for the closest airports, substations and similar, and mireye_proximity_screen to filter sites by drive time. Durations reflect typical traffic, not live conditions. Driving calculations cost $0.02 each on the Free plan ($0.018 Build, $0.015 Growth); straight-line distances are free. Mireye documents no typical latency for this synchronous call; a call that runs past the tool-call time limit fails here but keeps running at Mireye, so call again with the same idempotency_key and identical inputs to collect the saved result without a second charge.

Parameters

Name

Type

Required

Description

destinations

array

Required

End points, 1 to 500; origins times destinations may not exceed 10,000. Each locator is a "lat,lng" string or a full US street address with city and state or ZIP, never a place or landmark name (a name such as JFK Airport does not resolve). Addresses below street precision are refused, and at most 25 addresses may appear in one request. Example: ["40.6413,-73.7781"].

idempotency_key

string

Required

A key you choose for this request, 8 to 128 letters, digits, hyphens or underscores. Mireye keeps working after the caller disconnects: if this call times out or the response is lost, call again with the same key and identical inputs to collect the saved result without a second charge. Use a new key for new work. Reusing a key with different inputs returns 409 idempotency_conflict. Example: dist-2026-10-22-a1b2c3d4.

origins

array

Required

Starting points, 1 to 500. Each locator is a "lat,lng" string or a full US street address with city and state or ZIP, never a place or landmark name (a name such as JFK Airport does not resolve). Addresses below street precision are refused, and at most 25 addresses may appear in one request. Example: ["40.630973,-73.97228"].

max_cost_usd

string

Optional

Optional spending ceiling in US dollars for this request, as a decimal string with up to 6 decimal places. Mireye reserves the price before it starts and refuses the request with 402 if the price exceeds this ceiling or the available balance; unused reservation is released. Defaults to $10. Example: "2.00".

mode

string

Optional

driving (default) returns road distance and typical-traffic duration, billed per route; straightline returns free great-circle distance with null durations. Example: driving. One of: `driving`, `straightline`. Default: `driving`.

mireye_proximity_labor_shed

Compute Labor Shed

Estimate the civilian labor force and population that live within a drive time of one US site. Returns origin (as resolved), civilian_labor_force, population, tracts_counted, tracts_matrix_queried, tracts_unreachable, minutes, paid_driving_calcs, notes and billing. With estimate set to true it returns only the maximum price. Use mireye_proximity_labor_shed for the workforce reachable within a commute. Use mireye_location_fetch with tract_civilian_labor_force and tract_population for the site's own Census tract only (free). Only uncertain-band tracts are routed and billed ($0.02 per driving calculation on the Free plan, $0.018 Build, $0.015 Growth); call with estimate true first to see the maximum price. Mireye documents no typical latency for this synchronous call; a call that runs past the tool-call time limit fails here but keeps running at Mireye, so call again with the same idempotency_key and identical inputs to collect the saved result without a second charge.

Parameters

Name

Type

Required

Description

idempotency_key

string

Required

minutes

integer

Required

Drive-time radius in minutes, 5 to 90. Example: 45.

origin

string

Required

The site to measure from. Each locator is a "lat,lng" string or a full US street address with city and state or ZIP, never a place or landmark name (a name such as JFK Airport does not resolve). Addresses below street precision are refused, and at most 25 addresses may appear in one request. Example: 32.9,-96.9.

estimate

boolean

Optional

If true, return only the maximum price of this labor shed (maximum_cost_usd_by_plan) without running it or charging. Defaults to false. Example: true. Default: `false`.

max_cost_usd

string

Optional

mireye_proximity_nearest

Find Nearest Infrastructure

Find the closest airports, substations, power plants, rail, ports or urban areas to one US or Canadian point, ranked by drive time. Returns origin (as resolved), candidates (name, lat, lng, attributes, distance_miles, distance_km, duration_seconds, duration_minutes), applied_filters, paid_driving_calcs, notes and billing. candidates is empty when nothing qualifies within 160 km, and can hold fewer than n when a candidate has no road route. Use mireye_proximity_nearest to reach named infrastructure; never pass a place name to the other proximity tools. Use mireye_proximity_distance for your own destinations. Driving calculations cost $0.02 each on the Free plan ($0.018 Build, $0.015 Growth); straight-line distances are free. Mireye documents no typical latency for this synchronous call; a call that runs past the tool-call time limit fails here but keeps running at Mireye, so call again with the same idempotency_key and identical inputs to collect the saved result without a second charge.

Parameters

Name

Type

Required

Description

idempotency_key

string

Required

origin

string

Required

The starting point. Each locator is a "lat,lng" string or a full US street address with city and state or ZIP, never a place or landmark name (a name such as JFK Airport does not resolve). Addresses below street precision are refused, and at most 25 addresses may appear in one request. Example: 40.630973,-73.97228.

set

string

Required

The curated destination set to rank: @airports (public-use airports), @substations (by default only those rated 115 kV or more), @power_plants, @rail, @ports or @urban_areas. Candidates are searched within a fixed 160 km radius. Example: @substations. One of: `@airports`, `@substations`, `@power_plants`, `@rail`, `@ports`, `@urban_areas`.

filters

object

Optional

Optional set-specific filter override. Only @substations takes one today: min_kv sets the minimum voltage in kV (the default floor is 115; 0 includes every rated substation). Example: {"min_kv": 230}.

max_cost_usd

string

Optional

mode

string

Optional

driving (default) ranks by typical-traffic drive time and is billed; straightline ranks by free great-circle distance. Example: driving. One of: `driving`, `straightline`. Default: `driving`.

integer

Optional

How many of the nearest candidates to return, 1 to 25. Defaults to 3. Billing counts n times 5 driving calculations (at most 25), not the number returned. Example: 3. Default: `3`.

mireye_proximity_screen

Screen Sites by Drive Time

Filter candidate sites in the US and Canada by typical-traffic drive time to any of up to 10 anchor points. Returns survivors (origin_index, best_anchor_index, best_duration_seconds, best_duration_minutes), screened_out (each site's best duration, or null when no anchor is reachable), resolved_origins, resolved_anchors, paid_driving_calcs, notes and billing. Use mireye_proximity_screen to keep only sites within a drive-time band. Use mireye_proximity_distance for the full matrix. Every origin and anchor pair is billed as a driving calculation ($0.02 each on the Free plan, $0.018 Build, $0.015 Growth), however many survive. Mireye documents no typical latency for this synchronous call; a call that runs past the tool-call time limit fails here but keeps running at Mireye, so call again with the same idempotency_key and identical inputs to collect the saved result without a second charge.

Parameters

Name

Type

Required

Description

anchors

array

Required

The points a site must be close to (any one of them counts), 1 to 10. Each locator is a "lat,lng" string or a full US street address with city and state or ZIP, never a place or landmark name (a name such as JFK Airport does not resolve). Addresses below street precision are refused, and at most 25 addresses may appear in one request. Example: ["40.6413,-73.7781"].

idempotency_key

string

Required

max_minutes

integer

Required

The longest acceptable drive time to the nearest anchor, in minutes, 1 to 300. Example: 30.

origins

array

Required

The candidate sites to screen, 1 to 500; origins times anchors may not exceed 10,000. Each locator is a "lat,lng" string or a full US street address with city and state or ZIP, never a place or landmark name (a name such as JFK Airport does not resolve). Addresses below street precision are refused, and at most 25 addresses may appear in one request. Example: ["40.70,-73.95", "40.75,-73.80"].

max_cost_usd

string

Optional

min_minutes

integer

Optional

Optional shortest acceptable drive time, in minutes, to exclude sites that are too close to every anchor. Example: 10.

mireye_run_create

Submit Batch Fetch Run

mireye_site_ask

Ask About a Site

mireye_site_create

Prepare Site

Build your Agent

Same API key vault and scoped tool list across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
const sk = new ScalekitClient(
  process.env.SCALEKIT_ENVIRONMENT_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET,
);
const page = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["mireye"], toolNames: [
    "mireye_location_fetch",
    "mireye_address_geocode",
    "mireye_enrich_fields_list",
  ]}, pageSize: 100,
});
const tools = page.tools.map((t) => new DynamicStructuredTool({
  name: t.name, description: t.description, schema: t.inputSchema,
  func: (input) => sk.tools.executeTool({ identifier: "user_123", toolName: t.name, toolInput: input }),
});

import { ScalekitClient } from "@scalekit-sdk/node";
const sk = new ScalekitClient(
  process.env.SCALEKIT_ENVIRONMENT_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET,
);
const page = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["mireye"], toolNames: [
    "mireye_location_fetch",
    "mireye_address_geocode",
    "mireye_enrich_fields_list",
  ]}, pageSize: 100,
});
const result = await sk.tools.executeTool({
  identifier: "user_123",
  toolName: "mireye_location_fetch",
  toolInput: { preset: "flood_risk", address: "350 5th Ave, New York, NY 10118" },
});

import { ScalekitClient } from "@scalekit-sdk/node";
const sk = new ScalekitClient(
  process.env.SCALEKIT_ENVIRONMENT_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET,
);
const page = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["mireye"], toolNames: [
    "mireye_location_fetch",
    "mireye_address_geocode",
    "mireye_enrich_fields_list",
  ]}, pageSize: 100,
});
// pass page.tools into the Anthropic tool runner
const result = await sk.tools.executeTool({
  identifier: "user_123",
  toolName: "mireye_address_geocode",
  toolInput: { address: "350 5th Ave, New York, NY 10118" },
});

import { ScalekitClient } from "@scalekit-sdk/node";
const sk = new ScalekitClient(
  process.env.SCALEKIT_ENVIRONMENT_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET,
);
const page = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["mireye"], toolNames: [
    "mireye_location_fetch",
    "mireye_address_geocode",
    "mireye_enrich_fields_list",
  ]}, pageSize: 100,
});

Try these prompts

Copy a prompt into your agent. Each one maps to Mireye location data tools for the signed-in user.

Free public fields

Copy the prompt

Copied

Geocode 350 5th Ave, New York, NY 10118 and report rooftop accuracy.

Copy the prompt

Copied

Fetch the flood_risk preset for that address and cite each field source.

Copy the prompt

Copied

List fetch field names before I pick a preset.

Parcels and search

Copy the prompt

Copied

List enrich field presets, then enrich this parcel with owner and zoning.

Copy the prompt

Copied

Search parcels near that coordinate and cap spend with max_cost_usd 0.10.

Copy the prompt

Copied

Repeat a timed-out enrich with the same idempotency key and identical inputs.

Drive time and sites

Copy the prompt

Copied

Compute drive-time distance from this site to the nearest highway access.

Copy the prompt

Copied

Ask a plain-language question about flood and wetlands at this address.

Copy the prompt

Copied

Create a site record for this address after the fetch returns.

SEE HOW AUTH WORKS

Your users connect once. Their Mireye API keys stay vaulted, every call is checked, and every action is logged.

Authorize

Your user connects

Mireye

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Mireye

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Mireye

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Mireye

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

Reuse the same per-user API key vault and audit chain on other location and analytics connectors.

No items found.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Mireye API key makes every location fetch look like a bot. Scalekit resolves the key of the actual user who triggered the agent, never a shared bot.

// shared key
audit → bot_acct

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Mireye today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Mireye as the user or a shared key?

Per-user resolution. Each tool call uses the signed-in user's Mireye API key, so location fetches attribute to that user in the audit log.

Where is the Mireye API key stored?

In Scalekit's AES-256 vault, namespaced per tenant. You revoke access from one dashboard without rotating a shared secret across every agent.

Can I limit what the agent does in Mireye?

Yes. Filter tool names in listScopedTools (for example mireye_location_fetch only) and Scalekit checks that scope before the API call.

What happens when a user revokes access?

The next Mireye tool call fails closed for that user. Other users and other connectors are unaffected. The revoke is logged.

Do paid Mireye tools charge twice if a call times out?

Paid tools take an idempotency key. Repeat the call with the same key and identical inputs to get the saved result without a second charge. A new key is new work.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit