emem Locate API
The Locate API from emem — 1 operation(s) for locate.
The Locate API from emem — 1 operation(s) for locate.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/emem-dev-locate-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
description: emem is shared memory for AI agents working together in the real world.
license:
name: Apache-2.0
title: emem Locate API
version: 2.4.0
x-emem-surface-asymmetry:
memory_notes: MCP only
reach_them_at: POST /mcp, method tools/call
read_side_is_here:
- /v1/memory/search
- /v1/memory/sse
- /memories/{path}
tools:
- emem_memory_create
- emem_memory_view
- emem_memory_delete
- emem_memory_rename
- emem_memory_str_replace
- emem_memory_supersede
why_not_here: These write the agent correspondence plane, which is prose and untrusted-by-declaration. It is deliberately not part of the REST fact surface, and the two planes are kept apart rather than merged for convenience.
servers:
- description: Hosted instance (HTTPS-only)
url: https://emem.dev
tags:
- name: Locate
paths:
/v1/locate:
get:
description: 'Mint the canonical, vendor-neutral address (cell64) for a real-world place: the shared spatial identity every agent resolves to identically, so two models refer to the same ground instead of two descriptions of it. Also returns the topic-grouped inventory of bands and algorithms recallable there. For a first-class OBJECT identity (a bridge, a plot, a named place) rather than a raw cell, use emem_entity. Send EITHER `lat`+`lng` as numbers OR a free-text place; coordinates win when both arrive. `q`, `query` and `name` are all accepted spellings of `place`. A key this schema does not declare is reported in `_unrecognised_arguments`, so a typo answers about somewhere else rather than erroring.
When to use: Call when the input names a real-world place and the next step needs its cell64, or wants to know which bands exist there before recalling. `data_at_this_cell` carries `live_bands_by_topic` (every recallable band, grouped by topic), `algorithms_for_topic` (recipes that fuse them into named scores) and `declared_but_no_materializer_at_this_responder`. For one packaged answer in a single call, use `emem_ask`.'
operationId: emem_locate_get
parameters:
- in: query
name: place
required: false
schema:
description: Free-text place name. REQUIRED unless lat+lng are provided.
type: string
- in: query
name: q
required: false
schema:
description: Alias for `place`.
type: string
- in: query
name: query
required: false
schema:
description: Alias for `place`.
type: string
- in: query
name: name
required: false
schema:
description: Alias for `place`.
type: string
- in: query
name: lat
required: false
schema:
description: WGS-84 latitude. REQUIRED with `lng` unless `place` is provided.
type: number
- in: query
name: lng
required: false
schema:
description: WGS-84 longitude. REQUIRED with `lat` unless `place` is provided.
type: number
- in: query
name: lon
required: false
schema:
description: Alias for `lng`.
type: number
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/LocateResp'
description: ok
summary: resolve a place (or lat/lng) to a cell64 via query string, convenience wrapper…
tags:
- Locate
post:
description: 'Mint the canonical, vendor-neutral address (cell64) for a real-world place: the shared spatial identity every agent resolves to identically, so two models refer to the same ground instead of two descriptions of it. Also returns the topic-grouped inventory of bands and algorithms recallable there. For a first-class OBJECT identity (a bridge, a plot, a named place) rather than a raw cell, use emem_entity. Send EITHER `lat`+`lng` as numbers OR a free-text place; coordinates win when both arrive. `q`, `query` and `name` are all accepted spellings of `place`. A key this schema does not declare is reported in `_unrecognised_arguments`, so a typo answers about somewhere else rather than erroring.
When to use: Call when the input names a real-world place and the next step needs its cell64, or wants to know which bands exist there before recalling. `data_at_this_cell` carries `live_bands_by_topic` (every recallable band, grouped by topic), `algorithms_for_topic` (recipes that fuse them into named scores) and `declared_but_no_materializer_at_this_responder`. For one packaged answer in a single call, use `emem_ask`.'
operationId: emem_locate
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/LocateReq'
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/LocateResp'
description: ok
default:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorEnvelope'
description: 'error, the emem.error.v1 envelope. Branch on the stable `code` (see GET /v1/errors), not the message. A malformed or missing-field request body returns `code: invalid_argument` with the offending field named in `message`.'
summary: resolve a place name (or lat/lng) to a cell64
tags:
- Locate
components:
schemas:
LocateResp:
description: Response of /v1/locate. `cell64` is the canonical handle for the resolved place; `polygon_bbox` is present when the geocoder found an extent (city / park / lake / country / region), absent for point features. `via` declares which layer of the seven-tier embedded cascade answered, falling back to network (Photon → Nominatim) only when no embedded layer matched.
properties:
cell64:
$ref: '#/components/schemas/Cell64'
data_at_this_cell:
description: Topic-grouped inventory of recallable bands and applicable algorithms at this cell. Lets the caller chain into /v1/recall without a second introspection round-trip.
type: object
label:
description: Reader-friendly place label.
type: string
lat:
type: number
lng:
type: number
localized_names:
additionalProperties:
type: string
description: Map of ISO 639 language tag (`en`, `bn`, `zh-Hans`, `ar`, …) to localized name, when the resolved entity is in Overture and carries `names.common`. Lets an agent surface the user's-language label without a second geocoder call.
type: object
neighborhood_cells:
description: Eight neighbouring cell64s of the resolved centre cell.
items:
$ref: '#/components/schemas/Cell64'
type: array
overture_division:
description: Overture-divisions provenance, present when the cascade pulled an authoritative admin polygon. `division_id` is the GERS ID (globally stable, citable in receipts). `subtype` declares the admin level (country/region/county/locality/etc). `country` is the ISO 3166-1 alpha-2 owner.
properties:
country:
description: ISO 3166-1 alpha-2 (e.g. `BD`, `US`).
type: string
division_id:
type: string
schema_url:
type: string
subtype:
enum:
- country
- region
- county
- localadmin
- locality
- borough
- macrohood
- neighborhood
- microhood
- dependency
type: string
type: object
polygon_bbox:
description: Present when the place has spatial extent.
properties:
max_lat:
type: number
max_lng:
type: number
min_lat:
type: number
min_lng:
type: number
source:
description: '`overture_division_area` is authoritative (conflated OSM+Esri+Meta+TomTom polygon), preferred whenever Overture has a row for the entity. `country_table` / `admin1_table` / `admin2_table` / `admin3_table` are cities1000-aggregated approximations used when Overture is unreachable. `wide_bbox_table` is the curated wide-feature override for Sahara/Amazon/Himalayas etc.'
enum:
- wide_bbox_table
- country_table
- admin1_table
- admin2_table
- admin3_table
- nominatim_boundingbox
- overture_division_area
- centre_cell_bbox
type: string
type: object
polygon_geojson:
description: True OSM/Overture boundary as GeoJSON `Polygon` or `MultiPolygon` when an admin tier resolved. Pass back to /v1/recall_polygon to mask the cell grid against the boundary.
type: object
polygon_sample_cells:
description: Up to 64 representative cells covering the polygon, pass to /v1/recall_many or /v1/recall_polygon.
items:
$ref: '#/components/schemas/Cell64'
type: array
via:
description: Layer of the seven-tier locate cascade that answered. `country`/`admin1`/`admin2`/`admin3` = GeoNames hierarchical-admin tables (in-process); `embedded` = cities1000 populated places (in-process); `pois` = curated GeoNames well-known landmarks (peaks/lakes/parks/airports/monuments, in-process); `wide_bbox_table` = curated wide regions (in-process); `cache` = sled hot cache; `photon`/`nominatim` = network fallback.
enum:
- direct_latlng
- wide_bbox_table
- country
- admin1
- admin2
- admin3
- embedded
- pois
- cache
- photon
- nominatim
type: string
required:
- cell64
- via
type: object
ErrorEnvelope:
description: The `emem.error.v1` failure envelope returned by every endpoint on a 4xx/5xx. Branch on the stable `code` (not the human `message`). See GET /v1/errors for the full code catalog.
properties:
code:
description: Stable machine-readable error code. One of the codes in GET /v1/errors.
example: invalid_argument
type: string
details:
description: Optional structured recovery hints; present on errors that ship machine-readable next-steps.
type: object
message:
description: Human-readable detail. For invalid_argument this names the offending field (e.g. "missing field `q`").
type: string
path:
description: Request path that produced the error.
example: /v1/ask
type: string
schema:
const: emem.error.v1
type: string
required:
- code
- message
- schema
type: object
LocateReq:
description: 'Body for POST /v1/locate. Provide `place` (free-text, geocoded via embedded gazetteer → cache → Photon → Nominatim) OR `lat`+`lng`. Mutually exclusive: at least one of (`place`/`q`/`query`/`name`) or (`lat`+`lng`) must be present.'
oneOf:
- required:
- place
- required:
- q
- required:
- query
- required:
- name
- required:
- lat
- lng
properties:
lat:
description: WGS-84 latitude. REQUIRED with `lng` unless `place` is provided.
type: number
lng:
description: WGS-84 longitude. REQUIRED with `lat` unless `place` is provided.
type: number
name:
description: Alias for `place`.
type: string
place:
description: Free-text place name. Resolved via embedded gazetteer → cache → Photon → Nominatim.
type: string
q:
description: Alias for `place`.
type: string
query:
description: Alias for `place`.
type: string
type: object
Cell64:
description: 'cell64 wire form: four base-65,536 bigrams separated by dots, e.g. `defi.zb4d9.pefa.zf619`. Encoded resolution is ~9.55 m at the equator. Each bigram is either a CVCV quad, consonant `[bcdfghjklmnpqrstvwxyz]` followed by vowel `[aeiouAEIOU]` repeated twice, OR a synthetic 5-char `z[0-9a-f]{4}` slot used for the unused pad cells in the 65,536-entry alphabet. The regex pin matches `pattern` below byte-for-byte and is also surfaced under `Cell64Pattern` so agents can validate before sending.'
example: defi.zb4d9.pefa.zf619
maxLength: 23
minLength: 19
pattern: ^(?:(?:[bcdfghjklmnpqrstvwxyz][aeiouAEIOU]){2}|z[0-9a-f]{4})(?:\.(?:(?:[bcdfghjklmnpqrstvwxyz][aeiouAEIOU]){2}|z[0-9a-f]{4})){3}$
type: string