# RestoSignals > A REST + MCP API that finds US restaurants, bars and cafés 1–6 months BEFORE they open. It fuses public government open-data (liquor-license applications, food/health permits, new-business filings) into one deduped venue and scores how close it is to opening with an opening_score (0–100). More independent signals → higher score. The fusion + scoring is the product; a single raw feed cannot reproduce it. Base URL: https://api.restosignals.com MCP server: https://api.restosignals.com/mcp (Model Context Protocol, Streamable HTTP, JSON-RPC 2.0, protocol 2025-06-18) Metering: 1 credit = 1 returned lead. Empty results are free. 100 free credits on email sign-up, no card. A no-email trial key (15 credits) is one POST away. Live states: NY, TX, IL, CA (fused, multi-signal) plus OR, CO, WA (liquor-only, thin, no hot leads yet). Call `coverage` for the current list. Query any other state and you get an empty list, never a fabricated result. Signal types (exact values): liquor, food_permit, business. Owner contact (subscribers): every lead carries a `contact` block built from the public filings — owner name on nearly every lead, phone for many NYC venues, owner mailing address for most Texas venues. Trial keys see `contact.locked: true` plus `contact.available` saying whether details exist. No scraped emails. Scope: US food & beverage venues about to open. Not for already-open listings, reviews or menus. ## Start (agents, no human needed) 1. `coverage` (MCP tool, free, no key) — see live states and hot-lead counts. 2. Get credentials: either OAuth (MCP clients discover it from the 401 on /mcp) or `POST https://api.restosignals.com/v1/register` for a trial key (`pk_...`, 15 credits). 3. `new_openings {state, min_score, limit}` — scored leads, 1 credit each. 4. Out of credits → HTTP 402 / MCP error -32003 with an upgrade URL (https://restosignals.com/pricing/). Payment needs a human: hand them that link. ## API - POST /v1/register — mint a trial API key (returns pk_..., 15 trial credits). Free. - GET /v1/openings?state=NY&min_opening_score=40&limit=25 — scored, fused venue leads. 1 credit/lead. - GET /v1/openings/latest — venues with a signal in the last 7 days. - GET /v1/signals?state=NY&limit=5 — raw pre-fusion signal rows. - GET /v1/export?state=NY&format=csv — bulk CSV to a signed URL. 1 credit/row. - POST /v1/webhooks — register {url, criteria:{state,city,signal_type,min_opening_score}} for new-match alerts (paid accounts). - GET /v1/account — balance and keys for the calling key. - Auth: header `X-API-Key: pk_...` or `Authorization: Bearer pk_...` (never a query string). ## MCP tools - coverage — live states + venue/hot-lead counts. Free, no key. Call first. - new_openings {state, min_score, limit} — scored leads with contact block. 1 credit/lead. - venue_signals {venue_id} — the raw filings fused into a venue. 1 credit. - watch_area {url, criteria} — new-match webhook (paid accounts). ## Auth - OAuth 2.1 (PKCE S256 + Dynamic Client Registration): https://api.restosignals.com/.well-known/oauth-authorization-server - Protected resource metadata: https://api.restosignals.com/.well-known/oauth-protected-resource - Full agent auth guide: https://api.restosignals.com/auth.md ## Discovery - OpenAPI: https://api.restosignals.com/openapi.json (interactive: https://api.restosignals.com/swagger) - API catalog (RFC 9727): https://api.restosignals.com/.well-known/api-catalog - MCP server card: https://api.restosignals.com/.well-known/mcp/server-card.json - Agent skills index: https://api.restosignals.com/.well-known/agent-skills/index.json - Installable skill (SKILL.md): https://restosignals.com/restosignals-skill.md ## Docs - API reference: https://restosignals.com/docs/ - Agent guide: https://restosignals.com/agents/ - Pricing: https://restosignals.com/pricing/ - Support: support@restosignals.com