BuiltWith Domain API

Name: BuiltWith Domain API API
Brand: BuiltWith Domain API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany DataapiKey11 EndpointsREST

For Agents

Look up the technology stack, social profiles, redirects, and trust score for any domain across 11 BuiltWith endpoints.

Quickstart

Get started with BuiltWith Domain API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"look up tech stack for a domain"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with BuiltWith Domain API API.

Pull the full technology profile detected on a target domain

Run a lightweight free lookup that returns just core technology categories

Discover the domain relationships graph linking related and reseller sites

List every domain that uses a specific technology with the technology list endpoint

GET STARTED

Start building with BuiltWith Domain API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for BuiltWith Domain API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for BuiltWith Domain API, keeping it validated and agent-ready. BuiltWith maintains one of the largest technographic datasets on the web — every detected analytics, ad, framework, hosting, and ecommerce technology powering a domain. The Domain API exposes the same lookup surface as the public site plus relationships, technology trends, keyword detection, redirects, social profiles, and a trust score. Use it to enrich CRM records with tech stack data, build account scoring for outbound, monitor competitor tech changes, or qualify leads by what they currently run.

Use Cases

Patterns agents use BuiltWith Domain API API for, with concrete tasks.

★ Outbound Lead Qualification

Enrich every inbound lead with the tech stack of their company website. The agent calls GET /v22/api.json with the lead's domain and parses the technology categories to flag whether the prospect is on a competing platform, a complementary tool, or runs nothing relevant. This routes the lead to the right rep with the right talk track.

For domain example.com, fetch the BuiltWith profile and tag the lead with categories analytics, e-commerce, and marketing-automation tech detected.

Account Scoring by Tech Fit

Score target accounts based on the technologies they already run. GET /lists8/api.json returns every domain using a specific technology, letting you build a scoring model that boosts accounts already running a complementary stack. Combine it with /trust2/api.json to filter out low-trust domains automatically.

List domains using Salesforce, score each by trust, and post the top 50 to a Salesforce campaign as target accounts.

Competitive Tech Monitoring

Track when competitors add or remove a technology. Run a daily script that compares today's GET /v22/api.json snapshot for a watchlist of competitor domains against yesterday's, and alert on any changes. The trends endpoint provides longitudinal data so the same workflow can show category-level adoption over months.

Compare today's BuiltWith profile for competitor.com against yesterday's stored snapshot and alert Slack on any added or removed technologies.

AI Agent Account Researcher via Jentic

An SDR agent connected via Jentic can answer the question what does this prospect run before drafting an outbound email. The agent searches Jentic for tech stack lookup, loads the GET /v22/api.json schema, and executes against the operator's vault-stored BuiltWith key, returning a structured tech list ready for prompt context.

Search Jentic for tech stack lookup, load the GET /v22/api.json schema, and return the full technology profile for the domain in the user's prompt.

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for builtwith domain api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v22/api.json

Get full technology profile for a domain

GET

/free1/api.json

Free-tier lightweight technology lookup

GET

/lists8/api.json

List domains using a specific technology

GET

/ctu2/api.json

Company name to URL lookup

GET

/trends3/api.json

Technology adoption trends

GET

/social2/api.json

Social media profiles for a domain

GET

/trust2/api.json

Trust score for a domain

GET

/v22/api.json

Get full technology profile for a domain

GET

/free1/api.json

Free-tier lightweight technology lookup

GET

/lists8/api.json

List domains using a specific technology

GET

/ctu2/api.json

Company name to URL lookup

GET

/trends3/api.json

Technology adoption trends

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your BuiltWith API key is stored encrypted in the Jentic vault. Agents never see the raw key — Jentic appends it as the KEY query parameter at execution time and returns only the API response.

Intent-based discovery

Agents search Jentic with intents like look up tech stack or list domains using a technology, and Jentic returns the matching BuiltWith operations with full input schemas, so the agent calls the right endpoint without browsing docs.

Time to first call

Direct BuiltWith integration: a couple of hours to map endpoints, parse the technology grouping, and handle plan-tier limits. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

BulkSMS API

BulkSMS sends outbound SMS campaigns to leads enriched with BuiltWith tech-stack data.

Use BulkSMS alongside BuiltWith when an outbound flow needs to message qualified leads via SMS.

Complementary

BulkGate API

BulkGate is an alternative SMS gateway for outbound to BuiltWith-enriched leads.

Pick BulkGate when you need international SMS routing for leads enriched via BuiltWith technographics.

Complementary

Buildkite API

Unrelated CI/CD tool — listed as a name-match neighbour, not a substantive integration.

Buildkite is for software builds, not technographic data — included only as a near-name neighbour.

FAQs

Specific to using BuiltWith Domain API API through Jentic.

Why is there no official OpenAPI spec for BuiltWith Domain API?

BuiltWith documents its API in human-readable form but does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call BuiltWith Domain API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the BuiltWith Domain API use?

BuiltWith uses an API key passed as the KEY query parameter, or alternatively as Authorization: API {key} in the header. Through Jentic, the key is stored encrypted in the vault and attached to each request at execution time, never exposed to the agent.

Can I list every domain that uses a specific technology?

Yes. GET /lists8/api.json takes a technology name and returns the set of domains BuiltWith has detected running it. Use it to seed account lists for outbound or to size the addressable market for a category.

Can the BuiltWith API resolve a company name to a website?

Yes. GET /ctu2/api.json takes a company name and returns the most likely primary website plus any matched aliases. Pair it with /v22/api.json to immediately enrich the resolved domain with its tech stack.

What are the rate limits for the BuiltWith Domain API?

BuiltWith rate-limits per plan tier and per endpoint, with stricter limits on the free lookup. The OpenAPI spec does not encode the exact quotas — add retry-with-backoff for HTTP 429 responses and prefer the paid /v22/api.json for production volume.

How do I look up a tech stack from an AI agent through Jentic?

Run pip install jentic and authenticate with your ak_* key. Search Jentic with tech stack lookup, load the GET /v22/api.json operation, and execute it with the LOOKUP query parameter set to the target domain. Jentic injects the BuiltWith API key automatically.