#llmsmap.me

Independent technical audit

builtwith.com

builtwith.com

Overall AI readiness score

A combined result across all audit signals.

98of 100Excellent
AI readiness audit: 11/5/2026Public technical data

About the site

BuiltWith is a service that detects which technologies a website uses, including CMS, ecommerce platforms, analytics, frameworks and hosting providers. The site offers domain lookups, technology trend data, ecommerce product lists, and API and MCP tools for integration. It serves sales teams, AI and engineering teams, investors and analysts.

Written by AI from the site’s llms.txt and homepage.

Overall AI readiness assessment

How ready builtwith.com is for AI systems

98/100

BuiltWith was independently audited by llmsmap. builtwith.com currently scores 98/100 for AI readiness. The result combines AI-specific files, crawler policy, sitemap discovery, structured homepage data, and—when available—the mobile Google Lighthouse technical profile.

Audit context

llms.txt is accessible and contains 1,627 tokens. An expanded llms-full.txt is also available with 3,243 tokens, giving agents more direct context. A separate ai.txt policy is published.

robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 4. The homepage exposes Schema.org types Organization, WebSite; 7 OpenGraph tags were found and markup completeness is 90%.

The Google Lighthouse measurement is still collecting. Once complete, performance, accessibility, technical quality, SEO, and experimental browser-agent signals will be added with a limited weight.

Confirmed strengths

  • Accessible llms.txt
  • Expanded llms-full.txt
  • Published AI policy
  • 4 sitemap declarations
  • Schema.org: Organization, WebSite
  • Complete social metadata

Priority improvements

  1. 1Keep machine-readable files and markup aligned with future site changes.
llms.txt tokens1,627
llms-full.txt tokens3,243
ai.txt
sitemap.xml

Google Lighthouse technical profile

Google data is temporarily unavailable. The independent llmsmap AI-readiness audit remains valid.

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://builtwith.com/llms.txt
llms-full.txt

Full version is available

https://builtwith.com/llms-full.txt
ai.txt

AI rules are defined

https://builtwith.com/ai.txt
Sitemap in robots.txt4

4 sitemaps found

Schema.org (JSON-LD)

Types: Organization, WebSite

OpenGraph90%

7 OG tags found

AI bot access

Based on robots.txt analysis

GPTBotNot mentioned
OAI-SearchBotNot mentioned
ChatGPT-UserNot mentioned
Google-ExtendedNot mentioned
ClaudeBotNot mentioned
Claude-SearchBotNot mentioned
Claude-UserNot mentioned
BytespiderNot mentioned
CCBotNot mentioned
PerplexityBotNot mentioned
Perplexity-UserNot mentioned

Sitemaps

Declared discovery routes for crawlers and agents.

OpenGraph tags

Social preview metadata found on the homepage.

Markup completeness: 90%
og:titleBuiltWith
og:descriptionFind out what websites are BuiltWith
og:urlhttps://builtwith.com/
og:site_nameBuiltWith
og:typewebsite
og:langen-US

Schema.org markup

Structured entities and properties exposed on the homepage.

Types found: 2 · Properties: 5
OrganizationWebSite
nameBuiltWith
urlhttps://builtwith.com/
logohttps://builtwith.com/img/logo/logoSquare.png
potentialAction{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://builtwith.com/?q={search_term_string}"},"q
publisher{"@id":"https://builtwith.com/#organization"}
# BuiltWith

> Find out what websites are built with.

BuiltWith detects the technologies used on any website including CMS, ecommerce platforms, analytics,
frameworks, hosting providers, and more.

## Start Here (For LLMs and AI Agents)

Use the API-focused LLM guide first:
- https://api.builtwith.com/llms.txt

For BuiltWith knowledge-base guidance, see https://kb.builtwith.com/llms.txt.

This file is a high-level product map. The API LLM guide above contains detailed endpoint usage.
A full version of this product map is at https://builtwith.com/llms-full.txt and the full API
reference is at https://api.builtwith.com/llms-full.txt.

Choose an access method:
- BuiltWith API key: normal REST or standard MCP tools; calls spend account API credits.
- Existing account with a saved Stripe method: Agent Stripe Credit Top-Up API; this is not x402.
- Base USDC without a BuiltWith account: x402 v2 at https://api.builtwith.com/x402-api, using either one-off `/agent/*` HTTP payments or prepaid MCP lookup units.

## Core BuiltWith Links

- Website lookup: `https://builtwith.com/[domain]`
  - Example: https://builtwith.com/example.org
- Natural language Ask tool: https://builtwith.com/ask
- Technology trends and market movement: https://trends.builtwith.com
- MCP endpoint for AI integration: https://api.builtwith.com/mcp
- API LLM guide (primary): https://api.builtwith.com/llms.txt

## Discovery Endpoints

BuiltWith publishes the following `.well-known` resources for agents, API clients, and integration discovery:

- Agent Skills Discovery index: https://builtwith.com/.well-known/agent-skills/index.json
- BuiltWith API agent skill: https://builtwith.com/.well-known/agent-skills/builtwith-api/SKILL.md
- MCP discovery manifest: https://builtwith.com/.well-known/mcp.json
- Agent card: https://builtwith.com/.well-known/agent-card.json
  - Legacy A2A alias: https://builtwith.com/.well-known/agent.json
- API catalog: https://builtwith.com/.well-known/api-catalog
- x402 v2 payment discovery: https://api.builtwith.com/.well-known/x402
  - `https://builtwith.com/.well-known/x402` redirects to the canonical API-host descriptor.
- OAuth authorization server metadata: https://builtwith.com/.well-known/oauth-authorization-server
- OAuth protected resource metadata: https://builtwith.com/.well-known/oauth-protected-resource
- OpenAI plugin/app manifest: https://builtwith.com/.well-known/openai.json
- HTTP message signatures directory: https://builtwith.com/.well-known/http-message-signatures-directory
- Security contact policy: https://builtwith.com/.well-known/security.txt

## MCP Registry

A directory of remote Model Context Protocol servers BuiltWith has detected on company websites,
discovered from each site's published `llms.txt`. Every server and every tool has its own page.

- Registry home: https://builtwith.com/mcp-registry
- Category: `https://builtwith.com/mcp-registry/[category-slug]`
  - Example: https://builtwith.com/mcp-registry/developer-tools
  - Newest discoveries: https://builtwith.com/mcp-registry/recently-added
- Search: `https://builtwith.com/mcp-registry?search=[term]` - matches domains, endpoint URLs,
  tool names and tool descriptions
- Single MCP server: `https://builtwith.com/mcp/[domain]`
  - Example: https://builtwith.com/mcp/globalsurfari.com
- Single MCP tool: `https://builtwith.com/mcp/[domain]/tool/[tool-slug]`
- Sitemap for all of the above: https://builtwith.com/mcp-sitemap.xml
- Bulk and programmatic access: https://api.builtwith.com/mcp-api

Categories: developer-tools, api-tools, ai---machine-learning, productivity, analytics,
security---testing, devops, data-collection, general-tools, learning-resources, databases,
content-tools, cloud-services, collaboration, design, browser-tools, marketing, ecommerce,
social-media, game-development.

## Agent Stripe Credit Top-Up Endpoints (Not x402)

These legacy mppx paths charge an existing account's saved Stripe payment method and add account API credits. They are path aliases, not an x402 or MPP payment-challenge protocol.

- Credit balance: `GET https://api.builtwith.com/mppx/api-discovery`
- Spending limits: `GET https://api.builtwith.com/mppx/api-configuration`
- Credit purchase: `POST https://api.builtwith.com/mppx/api-purchase` with a unique `Idempotency-Key`; quantities use fixed increments of 2,000.
- Auth: separately scoped Agent Billing Key in `Authorization: Bearer`; general API keys and temporary `bw-` tokens cannot purchase. Monthly limits reset in UTC.
- Local OpenAPI discovery: `GET https://api.builtwith.com/mppx/openapi.json`
- BuiltWith.com aliases:
  - `GET https://builtwith.com/mppx/api-discovery`
  - `GET https://builtwith.com/mppx/api-configuration`
  - `POST https://builtwith.com/mppx/api-purchase`
  - `GET https://builtwith.com/mppx/openapi.json`

## x402 Paid Access

BuiltWith supports accountless x402 v2 access through prepaid MCP lookup units and fixed-price HTTP routes. These lookup units are separate from account API credits.

- Human documentation: `GET https://api.builtwith.com/x402-api`
- Canonical configuration and live pricing: `GET https://api.builtwith.com/.well-known/x402`
- MCP endpoint: `https://api.builtwith.com/mcp`
- Prepaid MCP flow: call `x402-pricing`, purchase at least 2,000 non-expiring lookup units with `x402-credit-purchase`, then pass the returned reusable `creditKey` to an `x402-*` lookup tool. Payment proof is sent in MCP request metadata at `_meta["x402/payment"]` only for purchases.
- One-off HTTP flow: discover the 12 fixed-price API routes and two List-pass purchase routes at `GET https://api.builtwith.com/openapi.json`. Send the intended query/body, read `PAYMENT-REQUIRED`, and retry the identical request with `PAYMENT-SIGNATURE`; successful settlement returns `PAYMENT-RESPONSE`.
- The descriptor is authoritative for the facilitator, network, asset, payment address, available tools, volume tiers, and List passes; clients should not hard-code those values.

## Programmatic Access

For direct API requests, use the official API docs and endpoint details:
- https://api.builtwith.com

Popular API families include:
- Domain technology lookup
- Technology and company lists
- Relationships / related sites
- Trust and risk signals
- Redirect and keyword data
- API-based trends data

## Notes

- Bots/AI agents may be blocked on interactive website pages.
- For reliable automated access, use the API and MCP routes.
Share or continue the analysis
Share this audit
Discuss with AI
Added 11/5/2026

Similar sites in the directory

Sites with a close AI-readiness score — compare how they set up llms.txt and markup.

builtwith.com - AI readiness audit | llmsmap.me