Developers
Three ways to build on your locator.
Everything the dashboard does, your own systems can do too. Manage locations from an AI assistant, read and write them over HTTP, or react to what visitors do on the map.
New
MCP server
Manage your locator from Claude, ChatGPT, Cursor, or any MCP client. Add locations, restyle the widget and get your embed code by chatting.
Read the docsREST
Location API
Read and write locations over HTTP with a bearer key. The same operations the MCP server exposes, for systems that own the data.
Read the docsBrowser
Widget events
The events the embedded locator dispatches on the page, for analytics and for wiring the widget into the rest of your site.
Read the docsOne key, every surface
The MCP server and the REST API take the same key and enforce the same rules: your account, your plan’s location allowance, and read-only keys that cannot write. Generate one in the dashboard under Data, then Developer tools. Keys start with hl_live_ and can be revoked at any time.
- MCP endpoint
https://app.handledlocal.com/api/mcp- Authorization header
Authorization: Bearer hl_live_your_key
The MCP server is included on every plan, including the free trial. The REST API is a Pro and Business feature. See pricing.