LocalIntel logo

LocalIntel

★★★½ 3.8/5
Visit site
Category
MCP
Pricing
Freemium

Quick Verdict

LocalIntel is a Florida-focused local-business discovery, market-data, and task-routing platform with a remote MCP surface for business search, regional analysis, sector gaps, RFQs, and quote status. The normalized brand is LocalIntel, not the older “The Local Intel” title. It should be treated as a regional data and routing experiment, not a nationwide business database or an authoritative site-selection adviser.

Its public pages contain unresolved conflicts. The home page advertises $0.01 MCP queries paid in pathUSD and says “no subscriptions,” while another panel sells $9.99/month AI market intelligence. Smithery still describes $0.01-$0.05 calls. Vendor data claims also vary among 113k+, 200k+, 240k+, and 614k+ businesses, while ZIP coverage appears as both 983 and 2,383. These numbers may reflect different dates, deduplication rules, datasets, or stale pages, but they remain vendor claims rather than audited facts.

Best For

  • Agent developers testing Florida local-service search or regional market research
  • Analysts able to verify Sunbiz, permit, Census, IRS, BLS, OSM, and vendor data independently
  • Experimental teams separating query, RFQ, provider selection, and payment into explicit approval steps
  • Not ideal for users who need national coverage, audited counts, or unattended job dispatch and payment

Key Features

  • Florida business discovery: search businesses, categories, ZIPs, nearby locations, and regions
  • Market analysis: sector gaps, income, permits, changes, regional comparisons, and vertical tools
  • MCP access: installation through Smithery plus a vendor-published remote MCP endpoint
  • RFQ routing: create requests, receive quotes, inspect status, and continue with registered providers
  • Agent wallet: connect or create an on-chain wallet for identity, routing, and pathUSD settlement
  • Business claims: providers can claim listings using Florida Sunbiz information and configure services and payment methods

Use Cases

The lowest-risk workflow is read-only: ask for candidate businesses or category distribution in a ZIP, then verify the records at their original public sources. Market and site-selection output should create hypotheses, not final lease, licensing, competition, or income decisions. Record query scope and data dates.

RFQs, provider contact, wallet connection, and payment are high-impact actions. Before an RFQ, show the request, contact details, service area, budget, and recipients and obtain explicit confirmation. When quotes arrive, obtain a second confirmation for provider, amount, asset, network, recipient address, and irreversibility before signing or paying. Search intent is not consent to broadcast an RFQ, and connecting a wallet is not consent to transact.

Pricing

Public statementDetailAssessment
MCP Agent Queries$0.01/query in pathUSD on Tempo mainnetVendor claim; confirm per-tool pricing and wallet flow before calling
Smithery description$0.01-$0.05/callConflicts with the home page and may describe older or tiered pricing
AI market intelligence$9.99/monthA panel describes unlimited St. Johns County questions, conflicting with “no subscriptions”
Business listingFreeDoes not make third-party POS, wallet, chain, or later payment fees free
Data Intelligence APIContactNo unified public price

The frontmatter remains freemium, but that is not confirmation of one coherent plan structure. Run a controlled test to inspect payment prompts, assets, failed-call handling, chain fees, and third-party charges, then request a written explanation of subscription versus usage pricing.

Pros

  • Clear regional scope focused on Florida
  • Combines discovery, market analysis, RFQs, and agent access
  • Offers Smithery installation and a remote endpoint for testing
  • Publishes 90-day query-log and 30-day transcript retention periods

Cons

  • Per-call, subscription, and “no subscription” statements conflict
  • Business and ZIP counts differ substantially across vendor pages
  • Rights across public records, OSM, permits, aggregated data, and proprietary data are not itemized clearly
  • Wallet, RFQ, and payment tools turn ordinary search into high-impact actions
  • Florida-only coverage and data freshness require external verification

Alternatives

ToolBest forMain difference
Brave SearchBroad web search for agentsWider coverage without Florida-specific RFQ and market workflows
Bocha AI SearchChinese search APIsBetter fit for Chinese retrieval, not a Florida business registry
Filesystem MCP ServerLocal file operationsClear local boundary without business search, wallets, or RFQs

Perplexity is another option for general cited research when transaction features are unnecessary.

FAQ

Are LocalIntel and The Local Intel different products?

This entry normalizes the official site brand to LocalIntel. The older Smithery title used “The Local Intel” but points to the same domain and MCP service.

Does LocalIntel cost $0.01 per query or $9.99 per month?

The site shows both, while also saying “no subscriptions”; Smithery lists an additional $0.01-$0.05 range. The relationship is not yet clearly documented.

How many businesses and ZIP codes does it cover?

Vendor pages show 113k+, 200k+, 240k+, and 614k+ businesses and either 983 or 2,383 ZIPs. Until methodology is unified, treat every count as a vendor claim.

Can I use the data directly for investment or site selection?

No. Verify public records, licenses, dates, duplicates, geographic boundaries, and vendor disclaimers, and use appropriate professional diligence.

How long does LocalIntel retain queries?

Its privacy policy says query logs are retained for 90 days and call/message transcripts for 30 days. Confirm how MCP calls are classified.

Can an agent send RFQs or make payments automatically?

The service exposes relevant tools and wallet flows, but they should not run without explicit approval. Require separate confirmations before RFQ transmission and before payment.

Bottom Line

LocalIntel’s Florida focus and MCP/RFQ combination have experimental value, but pricing, coverage claims, and product boundaries remain inconsistent. Begin with read-only, low-value, verifiable tests. Record source and date for every result, do not treat vendor counts as audited facts, and never broadcast contact data or sign a transaction without explicit confirmation. Keep this entry as a strict draft until pricing, data rights, and high-impact action documentation are coherent.

Last updated: July 21, 2026

Related tools