longdo-map-rest

longdo-map-rest is a skill for Claude Code from MetamediaTechnology/longdo-skills. It costs 109 tokens per session (2,732 once invoked), scanned A, original, Apache-2.0.

A reference for calling Longdo's location services over HTTP from any programming language or backend. These services provide address search, geocoding, nearby places, routing, traffic speeds, and related map data.

In plain words
What is it for?
Use it to search places, convert addresses to coordinates, find nearby points of interest, calculate routes, process batches, or query traffic data.
Why use it?
It explains the shared API-key, request, coordinate, language, and server-side usage conventions needed to connect to the services.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the longdo-map-rest plugin — 1 skill shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/metamediatechnology/longdo-skills/longdo-map-rest
Any agent
npx skills add MetamediaTechnology/longdo-skills --skill longdo-map-rest
Clone the repo
git clone --depth 1 https://github.com/MetamediaTechnology/longdo-skills

Made for: Claude Code.

Or install longdo-map-rest, the plugin that ships this one along with the rest of its 1 skill.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for longdo-map-rest

README.md
[![agentmods](https://agentmods.dev/badge/skills/metamediatechnology/longdo-skills/longdo-map-rest.svg)](https://agentmods.dev/skills/metamediatechnology/longdo-skills/longdo-map-rest)
Your own site
<a href="https://agentmods.dev/skills/metamediatechnology/longdo-skills/longdo-map-rest"><img src="https://agentmods.dev/badge/skills/metamediatechnology/longdo-skills/longdo-map-rest.svg" alt="Measured on agentmods" height="20"></a>
Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,732 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00109 $0.02732
Opus 5 $0.00055 $0.01366
Sonnet 5 $0.00022 $0.00546
Haiku 4.5 $0.00011 $0.00273

Measured 5d ago against content hash d0e007fac75a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

longdo-map-rest scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

r = requests.get("https://search.longdo.com/mapsearch/json/search", params={
plugins/longdo-map-rest/skills/longdo-map-rest/SKILL.md · 245 lines

How it starts

The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Longdo Location REST APIs

Official reference: https://map.longdo.com/docs/rest (legacy: https://api.longdo.com/map/doc/rest.php) Get a free API key: https://map.longdo.com/console/

These endpoints are language-agnostic HTTP services. Call them from your backend, a CLI, mobile, or any non-JS client. The in-browser map is a separate concern — see longdo-map-js.

Conventions that apply to every endpoint

  • Auth: every call needs key=YOUR_API_KEY.
  • Methods: GET or POST with application/x-www-form-urlencoded.
  • Format: JSON by default. Pass callback=fnName for JSONP.
  • Locale: locale=th (default) or locale=en; some endpoints accept - for multilingual output.
  • Coordinates: lon (longitude) and lat (latitude), in WGS84 degrees.
  • Hosts vary by service: search/suggest live on search.longdo.com, address/POI on api.longdo.com, routing on api.longdo.com/RouteService. Use the exact URLs below — don't assume one host.

Keep the key server-side. Unlike the JS map key (which is domain-locked in the console and meant for the browser), treat REST keys as backend secrets. Call these from your server, not from client JS where the key would leak. If you must call from the browser, use a domain-restricted key and proxy the sensitive ones.


Search & geocoding

Suggest (autocomplete)

GET https://search.longdo.com/mapsearch/json/suggest

Param Notes
keyword search term
area geocode filter (CSV)
offset / limit paging; limit default 10
dataset data sources (CSV — see Datasets)
key, callback standard

Response: suggestions[] with w (suggestion text), d (highlighted), s (dataset).

Search (POI + address)

GET https://search.longdo.com/mapsearch/json/search

Param Notes
keyword search term
lon, lat bias/center coordinates
span distance filter (deg/m/km)
tag category filter (CSV)
limit default 20
locale, key, callback standard

Read the full file on GitHub · 245 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 245 lines · 109 tokens per session scan A d0e007fac75a

Subscribe to this mod's changes

longdo-map-rest is a skill published in the GitHub repository MetamediaTechnology/longdo-skills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 109 tokens to every session and 2,732 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens