AI AGENT STORE / SERVICES

WEB DATA & EXTRACTION · FOR AI AGENTS

BuiltWith

Retrieve website technology profiles and historical detections through API or MCP.

BuiltWith gives agents structured technology observations for websites, including detection history where available. It supports account-credit lookups and documented wallet-funded access for agents researching companies, integrations or migration opportunities.

Your integration checklist

What you need from your owner
Choose account credits with an API key or authorize a funded Base USDC wallet for x402. Saved-card top-ups require separate manual enablement, spending limits and an Agent Billing Key.
Authentication
The Domain API accepts Authorization: API with the account key; standard MCP tools use a Bearer API key. Accountless HTTP requests use x402 payment proofs, while prepaid MCP purchases return a secret creditKey.
Your first task
Look up one known domain and compare current versus historical technology detections before using the profile to recommend an integration.
Billing & payment
Account Domain lookups consume API credits; other products can have different entitlements. x402 supports individual paid requests or prepaid MCP units with a minimum batch. Read the live quote before authorizing payment; list and Ask passes have separate terms.
Agent payment support
BuiltWith documents x402 v2 payments with USDC on Base, per-call HTTP access and prepaid MCP lookup units. A funded authorized wallet and compatible client are required. Saved-card credit top-ups instead need prior enablement, configured limits and a scoped Agent Billing Key.
Operational limits
Detection is an observation, not proof of a current contract or installed version. Ignore lists and stale records can affect coverage. Saved-card top-up aliases containing mppx are not an MPP or x402 payment protocol.

ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK

Check observation dates before treating a technology as currently installed

Editorial recommendation · Reviewed 2026-11-13

When to choose this service

Choose BuiltWith when a task benefits from accumulated website technology history. Directly inspecting a page may be enough for a single visible feature today.

A maintained crawl history and normalized technology index are external datasets. An agent can inspect a current page but cannot recreate years of observations from that page alone.

Suggested workflow

  1. Resolve the intended domain and select current or historical evidence for the task. Read the chosen operation’s cost and entitlement.
  2. Retrieve the profile and retain first/last detection dates with each relevant technology. Confirm consequential claims against the current site.
  3. Record the response and charge receipt once. Keep account credits, prepaid MCP keys and wallet payment proofs associated with their respective access routes.

Acceptance checks before real work

  • Historical detection does not establish present use.
  • A valid API key is not an Agent Billing Key.
  • A prepaid MCP batch can cost more than one direct lookup.

If the workflow fails

For missing data, check domain normalization and coverage before repeating paid calls. For uncertain payment delivery, reconcile the receipt or credit balance before purchasing again.

Provider documentation

Explore services for adjacent needs

Continue building your toolkit