Home / Docs / API reference

Requests and responses

MCP and REST share one definition of each operation, so the field names, limits and costs are the same on both.

Operations

MCP toolRESTCostSign-in needed
find_technologiesGET /v1/technologiesFreeNot on REST
count_sitesGET /v1/countsFreeNot on REST
search_sitesGET /v1/sites1 credit per site returnedYes
lookup_domainGET /v1/domains/:domain2 credits, free when not coveredYes
get_balanceGET /v1/balanceFreeYes
buy_creditsPOST /v1/checkoutFree to callYes

REST paths are relative to https://api.whichsitesuse.com. Over MCP every tool needs you signed in; over REST the two free search tools also answer without a key.

Inputs

On REST, GET operations take their inputs as query parameters and /v1/checkout takes a JSON body. List inputs can be comma-separated (technologies=shopify,klaviyo) or repeated (technologies=shopify&technologies=klaviyo). Over MCP, pass real arrays and objects.

The response envelope

Every successful response, MCP or REST, wraps the result in the same envelope. Over MCP it comes back as the tool's structured content and as JSON text. Keep the attribution line when you publish results.

{
  "data": { ... },
  "meta": {
    "crawl_date": "YYYY-MM-DD",
    "credits_used": 0,
    "credits_remaining": ...,
    "attribution": "Technology data from HTTP Archive (httparchive.org), detected with its open-source Wappalyzer fork. Core Web Vitals from the Chrome UX Report."
  }
}

credits_remaining is your balance after the call, or null for a REST call made without a key. crawl_date is the HTTP Archive crawl the answer came from.