Embedded internet intelligence
Ship internet intelligence without building the collection stack
Add FullHunt data to your product through documented OEM APIs.
The question
Can we ship this feature without owning a scanning pipeline?
FullHunt runs the collection and normalization pipeline. Your product calls a documented endpoint, receives JSON, and presents the result in its own interface.
How it works
01
Start with the product screen
Define what the customer needs to see and what action they should take next.
02
Choose the response fields
Map that screen to the required organization, host, vulnerability, exploit, DNS, or credential endpoints.
03
Test real JSON
Build the first integration against the documented response schema.
04
Set the production terms
Agree on request volume, branding, redistribution rights, and support before launch.
The records behind the answer
Attack surface
Observed organizations, domains, hosts, ports, and services.
Vulnerability intelligence
CVE records with Exploit Prediction Scoring System (EPSS), CISA Known Exploited Vulnerabilities (KEV), and public exploit data.
Historical infrastructure
Passive DNS and earlier observations for investigations that need more than a snapshot.
Agent tools
The same intelligence exposed through Model Context Protocol (MCP).
FullHunt runs the data layer behind your interface.
Start with one customer task and add endpoints when the product needs them.
What you get
- Documented endpoints and JSON schemas
- OEM and white-label licensing options
- On-demand scans and continuous data access
- One commercial integration for several FullHunt datasets
Map your feature to the FullHunt API.
Tell us what the screen needs to show and how often your product will query it.