A generic business list tells you a company exists. A building permit, a new license, or a property purchase tells you a company is about to spend. Amalgament turns those public-record events into intent signals you can prospect against.
A business that just pulled a permit consistent with an HVAC project is a lead. A new business license is a potential customer; an expansion or a property purchase is a project in motion. Amalgament surfaces these events joined to the business behind them, so “find businesses that pulled permits suggesting a major project” is a query, not a guess.
Permits, licenses, and property moves refresh on their own schedules; Amalgament re-pulls them and attaches each new record to its entity. You get a live signal keyed to a real company, not a static export that is stale on arrival.
Pull signals over the REST API into your pipeline, or let an MCP-connected agent watch for them and enrich a lead in context. Either way the raw public-record event becomes a timed reason to reach out.
Building permits API · Business licenses API · Property records API
Lists tell you who exists. Amalgament surfaces public-record events (permits, licenses, property moves) that signal a business is about to act, joined to the company, which is intent, not just identity.
Sources are re-pulled on schedule and every record carries its date, so you can filter to recent activity and verify currency with the free freshness endpoint.
Yes, via the REST API into a CRM or pipeline, or over MCP so an AI agent surfaces and enriches signals in context.
More solutions: Due diligence · KYB & AML · Property intelligence · Commercial real estate · Competitive intelligence