26 public JSON endpoints. OpenAPI 3.1 spec. MCP manifest. Atom 1.0 regulatory feed. Partner webhook pattern. Built for home-improvement apps, insurance carriers, building-product vendors, remodeling publishers, and AI agents. Free to use under CC-BY-4.0.
Eight production-tested patterns, each one live in at least one partner integration today:
Insurance carriers and home-insurance comparison sites embed a license-verification lookup so a homeowner can confirm their contractor is active in the state regulator's database before signing. Wire up against /data/license-verifier-coverage.json to get the 118-jurisdiction endpoint manifest and render an inline iframe or server-side lookup.
Remodeling publishers (magazines, newsletters, trade blogs) pull the regulatory callouts feed to keep their evergreen permit and cost articles current. Daily GET on /data/regulatory-callouts-full.json gives you a typed array of jurisdiction → callout pairs with versioned change-dates.
For push-based regulatory updates, subscribe to /feed/regulatory-updates.rss in any Atom 1.0 reader or feed-pipeline service (Zapier, n8n, Make, custom). Each item links back to the source dataset and a human-readable changelog entry.
Every endpoint is typed in /data/openapi.json (OpenAPI 3.1). Run openapi-generator, oazapfts, or orval against it to get fully-typed TypeScript / Python / Go / Swift clients with no manual SDK maintenance on your end. Schema changes are versioned and backward-compatible per the spec changelog.
AskBaily ships an MCP (Model Context Protocol) manifest so Claude, ChatGPT, and other agentic runtimes can call our datasets as first-class tools. The manifest is at /mcp and lists every read operation with its argument schema. Good for AI-powered home-improvement concierge apps.
Building-product vendors, smart-home installers, and quote-comparison tools pull /data/cost-ranges.json to ground their own estimator UI in real contractor economics. The dataset covers 33 services across 78 metros with low/median/high bands and build-date stamps.
Home-improvement apps with a homeowner audience can match their users to licensed builders via AskBaily's routing API. We do not resell leads, so this is a referral-only integration — your user enters a project scope, we match them to a verified builder, and no lead data changes hands. See /developers for the routing-handoff contract.
For insurance carriers and large publishers, poll-based integration is noisy. Register a POST endpoint with [email protected] and we will emit signed JSON webhooks on every dataset rebuild. Includes an HMAC signature header so you can validate origin on receipt. Average throughput is 20-40 events per week across all 26 datasets.
Project-planning, renovation-tracker, and smart-home apps embed license-check + cost-range data so homeowners get one authoritative contractor-verification source inside the app.
Home-insurance carriers use the license-verifier feed to pre-screen contractors on claims work and validate bond currency against state minimums.
Window, roofing, and solar vendors pull cost-range and regulatory-callout data to ground their quote-comparison tools in real contractor economics, not marketing figures.
Magazine, newsletter, and trade-blog publishers subscribe to the regulatory RSS feed to keep their evergreen permit and cost articles current without manual research cycles.
It means reading one or more of our 26 public JSON endpoints at /data/*.json, subscribing to our regulatory RSS feed at /feed/regulatory-updates.rss, or calling our MCP-compatible ChatGPT App manifest. There is no API key, no rate-limit contract, and no partner agreement required. We publish OpenAPI 3.1 at /data/openapi.json so your code generator can stub types directly.
All static JSON endpoints are served by Cloudflare Pages, which absorbs typical application traffic without rate-limiting. For sustained high-throughput use (more than 100 requests per second from a single origin), email [email protected] and we will work with you on an edge-cache strategy. We do not meter access and we do not bill for data.
Yes. The full license-verifier dataset is at /data/license-verifier-coverage.json — it lists the regulator endpoint URLs, expected response shapes, and verification-latency benchmarks for 118 jurisdictions. You can build a widget directly against those endpoints or call the pre-rendered JSON snapshots at /data/license-verifications/[jurisdiction].json. Attribution is required under CC-BY-4.0; see /partners/affiliate for the attribution format.
Subscribe to /feed/regulatory-updates.rss. We publish a new item every time a jurisdiction changes its license-verification endpoint, updates a minimum-insurance threshold, or introduces a new permit class. Typical cadence is 5 to 12 updates per month across 118 jurisdictions. The feed is Atom 1.0 compliant and machine-readable.
Partner-tier integrations can receive outbound webhooks for the datasets they subscribe to. The pattern is documented at /developers — submit a POST endpoint to [email protected], we will confirm it within 48 hours, and you will start receiving signed JSON payloads on every dataset rebuild. This is the best pattern for insurance carriers and remodeling publishers who want push-based updates rather than polling.
Email [email protected] with your integration pattern and a POST endpoint if you want webhooks. Featured integration partners are listed in the developer portal.