PreOpen Signal

Florida restaurant opening signals via MCP and REST API from public DBPR records, for lead-gen and agent workflows

Hosted MCP Server

npx add-mcp 'https://preopensignal.com/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

Florida Restaurant Opening Data for Software and AI Agents

The same source-backed Florida restaurant opening signals shown on this site are available programmatically through a REST API and MCP access, with provenance and methodology unchanged.

1. What data is available

Programmatic access covers the public Florida restaurant signal dataset: matched restaurant entities with regulatory status, commercial stage, confidence labels, opportunity tags, latest signal, and a source-backed signal timeline per entity. The data is a periodic snapshot of public regulatory records, not a live feed.

2. REST API

Versioned REST endpoints expose listing and detail reads over the public dataset under the /api/v1 path. Responses are read-only and carry the same stage and confidence model as the public pages. Access requires an API key passed with the request.

3. MCP access

PreOpen Signal exposes its public dataset through an MCP (Model Context Protocol) endpoint, so AI agents and assistant software can query Florida restaurant opening signals directly as tools without page parsing.

4. Available MCP tools

find_preopening_restaurants

Find restaurants whose observed signals indicate a likely pre-opening or recently approved stage, filterable by city and other public fields.

find_new_restaurants

Find restaurants with recent opening-related regulatory activity in the current snapshot.

get_restaurant_signal

Retrieve the source-backed signal history, including signal dates, types, and provenance, for one restaurant entity.

find_owner_changes

Find restaurants with observed ownership-change filings or approvals.

5. Source provenance

Data is derived from public records provided by the Florida Department of Business and Professional Regulation. Programmatic responses carry the same source dataset, retrieval timestamp, and official source links as the public pages, so machine consumers can trace every signal back to its evidence.

6. Access and example configuration

Get a key from Pricing: Pro $149/month or $1,490/year, or the Florida Data Pack $299 one-time. A confirmed payment delivers the key to the billing email; no separate account signup is required.

  • Pro: up to 5,000 successful API or MCP requests per UTC day while the subscription is active.
  • Data Pack: up to 5,000 requests per UTC day for 30 days; access expires 30 days after purchase, independent of whether a webhook arrives.
  • Keys are bearer credentials. To revoke access, open the management link in your delivery email. It includes the token required by /account. For help, contact the address in the site footer.
  • Over-limit requests return 429 with Retry-After and X-RateLimit-Limit / X-RateLimit-Remaining headers.

MCP configuration:

{
  "mcpServers": {
    "preopen-signal": {
      "url": "https://preopensignal.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Keep bearer credentials server-side and replace YOUR_API_KEY only in your private runtime configuration.

No key needed to try it: GET /api/v1/demo/restaurants returns five public entities, limited to 60 requests per UTC day per IP. You can also browse the public directory without a key.

7. Data snapshot / freshness

The dataset is a periodic snapshot of public regulatory records. The current snapshot date is shown on every public page and reflects what the regulator had published at retrieval time; recent real-world events may not yet appear.

8. Limitations

  • Commercial stages are interpretations of observed public records, not regulator findings.
  • Confidence labels describe signal strength and recency, not an opening probability.
  • No confirmed opening dates are provided or estimated.
  • A regulatory filing or approval does not guarantee that a business will open or remain open.
  • The snapshot may lag real-world events.

9. Example use cases

  • Find likely pre-opening restaurants in Miami for timed sales outreach.
  • Find recently approved restaurants in Orlando to track new market entries.
  • Retrieve the source-backed signal history for one restaurant before contacting it.
  • Find restaurant ownership changes that may precede remodels or rebrands.

See the methodology for how signals, stages, and confidence are defined.