NearMe.tel

For agents & developers

NearMe.tel is a human-first local directory on nearme.tel. The live catalog covers the Inland Empire, CA; other California metros are rolling out over time. The same HTTPS routes work for assistants, automation, and MCP-aware clients.

Beta & usage guardrails

  • Beta. Programmatic and MCP-related access is still in beta: APIs, rate behavior, and URL patterns may change without a long deprecation window.
  • Monthly search budget. Please keep automated or MCP-driven search traffic to roughly 500 searches per calendar month per integration or deployment (aggregate across your users unless we agree otherwise). We may throttle, cap, or block traffic that exceeds fair use or harms site performance.

Default regional home

The site root redirects here so bookmarks and agents can target a stable entry URL:

https://nearme.tel/inland-empire-ca

Canonical site URL

Use this origin for links and templates (no trailing slash):

https://nearme.tel

Search URLs

Primary pattern: text query in q. Always encode query values with encodeURIComponent before inserting into a URL.

https://nearme.tel/search?q={search_term}

Example (encoded):

https://nearme.tel/search?q=plumbers%20in%20Riverside

Category & city filters

  • Category only: https://nearme.tel/search?category={category_name}
  • City filter: add &city={city_slug} (preferred, e.g. canyon-lake-ca) alongside q or category.
  • API filter payload: server calls should carry city + state (or city_slug if the API parses it).
  • Pagination: &page=2 (and higher) when results span multiple pages.

Model Context Protocol (MCP)

MCP servers typically expose tools (e.g. "search local businesses") that your host calls. You can implement a tool that builds the URLs above and returns fetched HTML or JSON from your own backend if you proxy our public pages — keep requests respectful, cache when possible, and stay within the beta limits above (500 searches/month).

Optional: set NEXT_PUBLIC_MCP_PACKAGE_URL in the deployment environment to show a link to your MCP server or npm package here.

OpenClaw & other agents

Configure your agent with permission to open or fetch nearme.tel search URLs. A minimal flow: build the /search?… link from the user's task, retrieve the page or your API translation of it, then summarize using the same review and match signals users see in the UI. Treat this path as beta and respect the 500/month search budget when automating.

← Inland Empire home