Geocode AI

geocode-api

Write code that calls the Geocode AI API - REST (fetch, curl, Python requests) with the OpenAPI spec, the @meterapp/geocode CLI in scripts and CI, or the hosted MCP server from an agent framework. Covers auth with geo_ keys kept server-side, the resource and RPC routes, reading the op catalog, RFC 9457 errors, rate limit headers, batching points, caching polygons you already fetched, and the device sign-in for tools. Use when implementing or reviewing code that talks to Geocode AI; do not use for answering a boundary question in chat (geocode-boundaries) or building a described area (geocode-areas).

geocode-areas

Turn a plain-language description of an area into one validated polygon with Geocode AI's create_area - "Alameda and Contra Costa counties excluding Oakland", "the Bay Area minus San Francisco, plus SFO", a delivery or service area, or wording pasted from a contract, policy, license or regulation. An AI agent composes includes and excludes from real administrative boundaries and returns GeoJSON plus where each part came from, or explains what it could not map. Use when the area is not a single named place; for one named place use geocode-boundaries (instant and far cheaper).

geocode-boundaries

Look up administrative boundaries anywhere in the world with Geocode AI and work with their polygons - find a country, state, county, city, district or postcode by name, get its polygon as GeoJSON, find every boundary containing a coordinate (reverse), list what is inside a boundary (children), check which zone each of many points falls in (contains), and merge several boundaries into one shape (union). Use for "get the boundary/polygon/shape of X", "which county is this point in", "list the counties of Y", "is this address inside Z", service areas built from named places, and map data for a page or a notebook; do not use for a described area that is not one named place (geocode-areas) or for writing code against the API (geocode-api).

geocode-feedback

Report a Geocode AI bug with the failing request attached, request a missing feature, upvote or comment on what others asked for, follow up on what the human filed, and post or read reviews - report_issue (with the request_id from the failed call), request_feature, upvote_feedback, comment_on_feedback, list_feedback, get_feedback, list_my_feedback, submit_review, list_reviews. Use after a Geocode AI call fails in a way that looks like our bug (5xx, a wrong or missing boundary), when the human wishes the API did something it cannot, asks what is planned, or wants to rate the product; do not use for ordinary lookups (geocode-boundaries), described areas (geocode-areas) or purchases.

geocode-teams

Work inside a Geocode AI organization - tell which organization a key or connection acts in and the caller's role (get_account, list_orgs), who is in it and which teams exist (list_members, list_teams), save a boundary export to the organization's shared file library (save_file), find files teammates saved (list_files, get_file) and share a file with a team or a person at read, write or admin access (share_file, unshare_file, update_file). Use for "share this boundary with the GIS team", "what files has my team saved", "who is in our account", "which org am I in", a 403 forbidden; do not use for looking boundaries up (geocode-boundaries), purchases, or inviting and removing people, which a human does on the dashboard.