BuiltWith
Technology stack, company meta, and contacts detected on a domain.
BuiltWith Domain API on SearchIn returns the technologies a website uses, plus company meta and contacts when they are in the index. Lookups run through RapidAPI.
Capabilities
- Detected technologies with tags, categories, and first/last seen dates
- Company name, location, vertical, and rank signals when indexed
- Emails, phones, social profiles, and named contacts from BuiltWith meta
- Estimated monthly tech spend when BuiltWith has a figure
What you get back
- Company and spend card
- Filterable technology groups by tag
- Contact, social, and people lists when present
UI workflow
Open SearchIn and choose Domain.
Select BuiltWith as the provider.
Review the company card, then filter the technology inventory.
Sample queries
| Input type | Query | Notes |
|---|---|---|
domain | example.com | Tech stack + company meta |
Pricing
domain $0.10
Best for
- Seeing what a site is built on before a takedown or impersonation review
- Pivoting BuiltWith emails and socials into people-search or leak providers
- Comparing a brand’s public stack with WHOIS and host findings
How it works & why through OSINTverse
How the request runs
- 1Choose Domain and select BuiltWith.
- 2SearchIn looks up the hostname on BuiltWith’s Domain API through RapidAPI and reads technologies, meta, and attributes.
- 3Technologies are grouped by tag with first- and last-detected dates. Company, spend, emails, phones, and socials render on a summary card.
- 4Contacts and social URLs become graph nodes you can pivot into people-search or leak providers.
Coverage. BuiltWith’s historical technology index for a root domain — current and past stack detections, company meta, and contacts when they are in the profile. Live lookups of non-root hosts are slower and may omit history.
Why route BuiltWith through OSINTverse
- ·A $0.10 query returns a grouped tech inventory and company card — no BuiltWith dashboard or spreadsheet.
- ·Emails, phones, and socials from meta sit next to WHOIS and Shodan on the same identifier.
- ·Technology names become graph nodes so you can note a CMS or analytics stack on the case.
| BuiltWith directly | Through OSINTverse | |
|---|---|---|
| Getting started | BuiltWith sells Domain API access on its own plans or via RapidAPI, returning a large JSON technology profile you parse yourself. | Sign in, top up from $10, and run BuiltWith the same minute — no vendor contract, seat, or sales call. |
| What a query costs | Plan, credit pack, or contract pricing set by the vendor and paid up front. | Pay per query from your prepaid balance — BuiltWith starts at $0.10 for domain lookups, with the exact price shown before you run it. |
| Failed lookups | Handled under the vendor's own credit and refund policy. | Automatically refunded to your wallet — a search that fails upstream after billing is not charged. |
| Output format | A vendor-specific response shape you normalise and render yourself. | Normalised result panels plus the raw JSON, returned by the same POST /v1/search contract as every other integration. |
| Cross-source work | Copy-paste between vendor dashboards to follow a lead into another dataset. | Results join one case graph, so you can pivot an entity into any of the other 13 integrations in a click. |
| Running it for a team | Per-seat or per-account access, billed and administered per analyst. | One shared team wallet with roles, provider allowlists, enforced MFA, and audit history — no per-seat fee. |
| Volume work | Script the vendor API yourself, including retries, polling, and rate handling. | Bulk search takes up to 50 queries across selected providers in one submission (max 100 jobs), with per-job status and partial-failure handling. |
One wallet, no subscriptions
Top up prepaid USD from $10 and spend it a query at a time across all 14 integrations. No monthly fee, no seat count — and the balance never expires.
Failed searches are refunded
If an upstream provider errors or times out after the charge, the search is marked refunded and the money goes back to your wallet automatically.
One API for every source
The same POST /v1/search contract and x-api-key header work for every integration, so adding a source to your automation is a one-word change.
Cases and pivot graph
Results land in a named case you can reopen. Entities become graph nodes you can pivot from into any other integration without retyping.
Team wallets and controls
Share one balance with roles, provider allowlists, enforced MFA, and audit history — instead of buying a vendor seat for every analyst.
Exports built in
Download any result as JSON, CSV, or PDF, and export the case graph as PNG, SVG, entities CSV, or graph JSON.
Good to know
- Coverage follows BuiltWith’s index. A new or private site may return little or require a live lookup.
- Very large stacks are capped in the structured panel; the raw JSON still holds the full payload.
- Estimated spend and revenue are BuiltWith models, not accounting figures.
API example
$0.10 per query. Live runs charge the active workspace wallet — the same rates as the dashboard.
curl -X POST "https://apiv1.osintverse.com/v1/search" \ -H "Content-Type: application/json" \ -H "x-api-key: ov_your_api_key" \ -d '{"provider":"builtwith","input_type":"domain","query":"example.com"}'Invalid provider + input_type pairs return HTTP 422. Confirm combinations with GET /v1/providers or the pricing matrix.
Run this in the SearchIn UI or create an API key. Full HTTP reference: search workflow. Marketing overview: BuiltWith integration.