Pilot Service Agents Geo

Geographic and geolocation APIs — Google Maps suite (premium) plus open geocoders and IP-to-location lookups. Use this skill when: 1. Converting addresses ↔...

Security Scan

The skill is internally consistent with its stated purpose (it is an instruction-only wrapper that talks to pilot-protocol agents via pilotctl), but it requires a running pilot daemon/overlay and will forward queries to networked agents/upstream providers — so trust and privacy of the overlay are the main concerns.

Purpose & Capability

Name/description match the runtime requirements: the skill is purely an instruction set for querying geo-related 'agents' over the Pilot Protocol. Requiring pilotctl and a daemon joined to network 9 is coherent with that purpose.

Instruction Scope

SKILL.md only instructs the agent to use pilotctl to send /help, /data, /summary and to poll the inbox. It does not ask for local file reads or unrelated env vars. Note: queries (addresses, coordinates, etc.) are transmitted to overlay agents and upstream services (including paid Google Maps agents), so user data will leave the local host and go to external agents/upstream APIs.

Install Mechanism

No install spec and no code files — lowest-risk delivery model. The only runtime dependency is the pilotctl binary, which is expected given the skill's design.

Credentials

The skill declares no environment variables or credentials, which is consistent because it delegates API access to remote agents. However, that means upstream premium services (Google Maps) are accessed by those remote agents — you will not control their API keys or billing from this skill. Expect potential billing/usage and privacy implications handled by the agent network rather than by local config.

Persistence & Privilege

always is false and the skill is user-invocable only; it doesn't request elevated or persistent platform privileges and does not modify other skills or system settings.

Assessment

This skill is an instruction-only adapter for querying geo/Maps agents on the Pilot Protocol overlay. Before installing: 1) Ensure you trust the Pilot Protocol network and the operator(s) of 'network 9' and the directory agent, because your queries (addresses, coords, etc.) will be forwarded off-host to remote agents and upstream APIs. 2) Understand billing: premium Google Maps functionality will be billed upstream by those agents — the skill does not request or manage Google API keys locally. 3) Avoid sending highly sensitive location-related data unless you trust the overlay and have verified the agent operators. 4) If you prefer local control, consider using a skill that requires your own Google API key (so billing and keys remain under your control). 5) Check the AGPL-3.0 license implications for your usage and distribution needs.

Geographic and geolocation APIs — Google Maps suite (premium) plus open geocoders and IP-to-location lookups.

All agents in this category follow the standard contract described in pilot-service-agents. Send /help to any agent to read its exact filter schema — the table below is a snapshot; the catalogue grows, so always verify with a fresh list-agents query.

Agents in this category (snapshot)

Hostname	Description
country-from-ip	Country detection from IP address
elevation-open-meteo	Elevation Open Meteo
gcp-maps-address-validation	Google Maps Address Validation (premium)
gcp-maps-air-quality	Google Maps Air Quality — current conditions (premium)
gcp-maps-directions	Google Maps Directions — driving/walking routes (premium)
gcp-maps-distance-matrix	Google Maps Distance Matrix — travel times (premium)
gcp-maps-elevation	Google Maps Elevation — elevation for coordinates (premium)
gcp-maps-geocoding	Google Maps Geocoding — address/coords (premium)
gcp-maps-geolocation	Google Geolocation — locate from WiFi/cell/IP (premium)
gcp-maps-places-new	Google Maps Places (New) — text place search (premium)
gcp-maps-pollen	Google Maps Pollen — forecast by coord (premium)
gcp-maps-roads	Google Maps Roads — snap GPS to roads (premium)
gcp-maps-routes	Google Maps Routes — traffic-aware routing v2 (premium)
gcp-maps-solar	Google Maps Solar — roof solar potential (premium)
gcp-maps-timezone	Google Maps Time Zone — tz from coords (premium)
ip-api	ip-api.com - IP geolocation, ISP, country, region
nominatim-reverse	OpenStreetMap reverse geocoder
nominatim-search	OpenStreetMap forward geocoder
open-meteo-geocoding	City name to coordinates geocoder (global)
opensky-bbox	Live aircraft states in a bounding box
opentopodata-srtm	Opentopodata Srtm
osrm-route	Open Source Routing Machine — driving directions
overpass-api	Overpass Api
photon-reverse	Photon Reverse
rest-countries-currency	Countries using a specific currency code
rest-countries-region	Countries by region (Europe/Asia/etc)
restcountries-region	Restcountries Region
uk-postcodes	UK postcode geolocation + admin lookup
viacep-brazil	Brazilian address lookup by CEP code
zippopotam-city	City info by country+zip (Zippopotam.us)

What you can expect

• Google Maps Platform coverage — geocoding, directions, distance matrix, elevation, timezone, roads, places, routes, address validation, geolocation, solar, air-quality, pollen
• All Google Maps agents are premium (hostname prefix gcp-maps-*) — paid upstream, higher accuracy and SLA
• Open alternatives for basic lookups (IP-to-country, open-elevation)

What NOT to expect

• Free tier for Google services — pricing is metered upstream
• Real-time traffic fleet management (not in catalogue yet)
• Raw map tile imagery — the agents serve JSON envelopes, not PNGs

Commands (same pattern for every agent in the category)

# Read an agent's filter contract
pilotctl --json send-message <hostname> --data "/help"
pilotctl --json inbox

# Fetch structured data
pilotctl --json send-message <hostname> --data '/data {json filters}'
pilotctl --json inbox

# Natural-language summary (Gemini)
pilotctl --json send-message <hostname> --data '/summary {json filters}'
pilotctl --json inbox

Response shape

send-message returns an ACK envelope immediately ({"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}). The actual agent response arrives a few seconds later and is read with pilotctl --json inbox. Each inbox entry carries the agent's normalised envelope in its data field:

{
  "source": "<hostname>",
  "items":  [...],
  "count":  <int>,
  "total":  <int|null>,
  "page":   <int|null>,
  "next":   <cursor|null>,
  "truncated": <bool>,
  "upstream_url": "<resolved upstream URL>"
}

/help returns plain text. /summary returns a Gemini-generated prose string. Free-text queries also return Gemini prose.

Workflow Example

# 1. Fresh discovery — the catalogue grows, never hard-code
pilotctl --json send-message list-agents --data '/data {"category":"geo","limit":20}'
pilotctl --json inbox

# 2. Read the contract of a specific agent
pilotctl --json send-message gcp-maps-geocoding --data '/help'
pilotctl --json inbox

# 3. Query it
pilotctl --json send-message gcp-maps-geocoding --data '/data {"address":"1600 Amphitheatre Pkwy Mountain View CA"}'
pilotctl --json inbox

Dependencies

Requires the pilot-protocol core skill, the pilot-service-agents skill (for the general discovery flow), pilotctl on PATH, and a running daemon joined to network 9.