We turn scattered public sources into clean APIs and datasets: building permits from US city open-data portals and job postings from the public job-board APIs of nine applicant tracking systems. Pay per result, no subscription, and every known limit is in the docs.
Run them on Apify from the web, the API, Python, n8n, Make, Postman or any MCP client.
Newly issued building permits from Austin, San Antonio, New York City, Los Angeles, Chicago, Philadelphia, Boston, Seattle, San Francisco, Cincinnati, Baton Rouge, Washington DC, Denver, Nashville, Raleigh and Louisville, normalized into one record: address, ZIP, work description, valuation and contractor. Contractor phone numbers are published by Austin and Raleigh only, and we say so.
Every open role from a company's careers feed on Greenhouse, Lever, Ashby, Workday, SmartRecruiters, Workable, Recruitee, Personio or Rippling, on one schema. Give it company names or domains and it finds the board itself (about 90% of companies on our test set).
Which job board does a company use? Paste domains or company names and get the platform, the board URL, the public API endpoint and the number of open roles.
Free snapshots under CC BY 4.0. For fresh data, run the APIs above.
All three tools are available as MCP tools through Apify's MCP server. Bring your own Apify token.
https://makenomistakesllc.com/mcp?tools=make_no_mistakes/us-building-permits-scraper,make_no_mistakes/multi-ats-job-board-api,make_no_mistakes/company-ats-detector Authorization: Bearer <your Apify API token>
That endpoint forwards to mcp.apify.com unchanged; you can also call Apify's server directly with the same ?tools= list. Config examples for Claude, Cursor and other clients are in the GitHub repo.