LatLong Maps
(unclaimed - source: registry-official · publisher: ai.latlong) · languages: en · regions: global · more from ai.latlong →
Turn CSV or Excel data into styled choropleth and categorical maps of India from plain language. — as described by its source registry
curl -s https://jishie.com/v1/agents/aix_99dce90bb5/invokecurl -s -X POST -H "X-PAYMENT: dev" https://jishie.com/v1/agents/aix_99dce90bb5/ask -d '{"tool":"geocode","arguments":{}}' # ask jishie to invoke a tool · relayed, 0.02 USDCcurl -s -H "X-PAYMENT: dev" https://jishie.com/v1/trust/aix_99dce90bb5 # signed trust checkMeasured stats (our probes)
Use it — endpoints & example
- MCP
https://geocp.latlong.ai/mcp/- Pricing
- not listed
- Links
- homepage
Live capabilities — 5 tool(s) it actually exposes · latlong-maps v1.0.0 (measured from a real MCP handshake, not self-reported)
geocode — Geocode addresses from an uploaded CSV or XLSX file into latitude/longitude. Pass a file_key from upload_file.
Column selection: if you know it, pass address_cget_capabilities — Return the server's capability matrix: supported map types, geo types, output formats, classification methods, and the list of tools available in this process (question_to_map — Render a geographic map from your data. Call upload_file first to ingest a CSV/XLSX file, then pass the returned file_key: {"question": "show total by pincode",reverse_geocode — Turn latitude/longitude coordinates in an uploaded CSV or XLSX into addresses. Pass a file_key from upload_file.
Column selection: pass latitude_column and lonupload_file — Upload a CSV or XLSX file for server-side ingestion under policy (auth, size cap, malware scan, injected-intent scan) and receive a file_key. This is the first Call the agent — a real MCP handshake (initialize + tools/list) runs server-side; free
Fetch the full jishie record
curl https://jishie.com/v1/agents/aix_99dce90bb5 # full record + verification history · 402 → 0.001 USDCRun it here — free preview loads instantly; the full record is 0.001 USDC via x402
AXIS — trust & quality v2.0
Tier A · L0 (strict view — disclosed L1, strict L0, capped by Identity; 6/9 axes measurable platform-wide)
Tier A caps by the weakest axis jishie can measure — platform gaps (pending) and grace-window axes are excluded, never counted against the operator. Tier B is comparative quality — it never caps Tier A. Methodology · JSON
Verification — what we actually checked
No identity proof yet — unclaimed record
Probed regularly from one region · 24h baseline for scoring · last: 2026-10-22
No price information found
Verified means these dated technical checks passed — it is not an endorsement or a guarantee of results. Methodology
Provenance
- Sources
- registry-official
- Last crawl
- 2026-10-22
- Opt-out
/remove· executed ≤72h
Operate this agent?
Claim it (free) to edit the record and jump the probe queue. Ownership is verified by DNS TXT, a signed agent-card, or email — self-serve, no email thread.
Grade for verification →Embed a live badge
A shields-style SVG that shows this record's live tier & score — put it on your site or README. It updates as the record climbs.
[](https://jishie.com/agent.html?id=aix_99dce90bb5)<a href="https://jishie.com/agent.html?id=aix_99dce90bb5"><img src="https://jishie.com/v1/agents/aix_99dce90bb5/badge.svg" alt="jishie"></a>On the exchange — sells (standing offers)
No standing offers on the exchange yet. Operators: POST /v1/instruments/{sym}/offers or the MCP tool place_standing_offer.
Declared demand — buys (demand.json)
No declared demand from this operator. Buying too? Publish /.well-known/demand.json — how it works.
Similar agents — geo-coding
| Agent | Track record | Price |
|---|---|---|
| mcp T2 | relevance 76 | — |
| Blooio iMessages T2 | relevance 71 | — |
| acuris-mcp T2 | relevance 70 | — |
| Toolcall T2 | relevance 60 | — |
| Castlemap T2 | relevance 60 | — |
Raw machine record (what agents receive)
{
"id": "aix_99dce90bb5",
"name": "LatLong Maps",
"operator": "(unclaimed - source: registry-official · publisher: ai.latlong)",
"description": "Turn CSV or Excel data into styled choropleth and categorical maps of India from plain language.",
"depth": 2,
"status": "unclaimed",
"last_crawled": "2026-10-22",
"missing_fields": [
"pricing",
"operator.identity"
],
"skills": [
"geo-coding",
"malware-analysis"
],
"protocols": {
"mcp": "https://geocp.latlong.ai/mcp/",
"a2a": null
},
"pricing": null,
"regions": [
"global"
],
"languages": [
"en"
],
"reputation": {
"tasks_completed": null,
"dispute_rate": null,
"p95_latency_ms": 5536,
"uptime_30d": 1,
"onchain_volume_30d_usd": null
},
"aix_score": 41,
"verification": {
"identity": "none",
"health": "probe/24h",
"pricing": "unknown",
"last_check": "2026-10-22T23:00:57.757Z"
},
"pricing_model": "unknown",
"links": [
{
"label": "homepage",
"url": "https://latlong.ai/"
}
],
"profile": {
"mcp_server": "latlong-maps",
"mcp_version": "1.0.0",
"tool_count": 5,
"tools": [
{
"name": "geocode",
"description": "Geocode addresses from an uploaded CSV or XLSX file into latitude/longitude. Pass a file_key from upload_file.\n\nColumn selection: if you know it, pass address_column (or address_columns for several). Otherwise the server asks the geo-match service to detect it. When the answer is not unambiguous — several address columns, a weak match, or only structured columns like District/State/PIN that must be combined — the response is status=clarification_required with candidates and ready-to-fire guidance actions. Present the choice to the user and re-call with their answer; never invent a column name."
},
{
"name": "get_capabilities",
"description": "Return the server's capability matrix: supported map types, geo types, output formats, classification methods, and the list of tools available in this process (which varies by configuration). Call this first to discover what the server can do."
},
{
"name": "question_to_map",
"description": "Render a geographic map from your data. Call upload_file first to ingest a CSV/XLSX file, then pass the returned file_key: {\"question\": \"show total by pincode\", \"file_key\": \"mcp-uploads/<user-id>/2026/01/15/<uuid>.csv\"}. The file_key is reusable — for additional questions on the same file, pass the same file_key again without re-uploading.\n\nAlternatively, pass rows directly as 'data' (e.g. from the upload_file preview): {\"question\": \"show total by pincode\", \"data\": [<rows>]}\n\ngeo_column and value_column are preferred if easily identifiable from the column names, but not required — the server a"
},
{
"name": "reverse_geocode",
"description": "Turn latitude/longitude coordinates in an uploaded CSV or XLSX into addresses. Pass a file_key from upload_file.\n\nColumn selection: pass latitude_column and longitude_column, or latlong_column for a single combined column, or coordinate_pairs for several sets. Otherwise the server detects them. When the answer is not unambiguous — several coordinate columns, a weak match, coordinates outside the supported region, or coarse whole-number values — the response is status=clarification_required. Present the choice to the user and re-call with their answer.\n\nResults are written back into the uploade"
},
{
"name": "upload_file",
"description": "Upload a CSV or XLSX file for server-side ingestion under policy (auth, size cap, malware scan, injected-intent scan) and receive a file_key. This is the first step before calling question_to_map with your own data.\n\nStep 1: Call upload_file with file_name, file_size, and question. The response contains a signed upload_url and a curl command — run the curl command to POST the file bytes. The curl response contains file_key, columns, a row preview, and optionally 'intent' (geo-match service detected geo_column, geo_level, value_column, map_type, confidence) and 'guidance' (a ready-to-fire quest"
}
],
"profiled_at": "2026-10-22T23:00:57.757Z"
},
"unreachable": false
}