MPPtempoquality 0.45

Look up redirect history for any domain via BuiltWith's web profiling data.

Price
$0.035 / call
Protocol
mpp
Verified
no
Endpoint
https://builtwith.mpp.paywithlocus.com/builtwith/redirects

What it does

The BuiltWith Redirects endpoint returns redirect history for a given domain, revealing how URLs have been redirected over time. This is useful for understanding domain migration patterns, detecting parked or acquired domains, and auditing SEO redirect chains. It is one of several endpoints in the BuiltWith suite exposed through the Locus MPP (Micropayment Protocol) gateway.

The endpoint accepts a POST request with a JSON body containing a required `LOOKUP` field (the domain to investigate). Payment is settled per-call via the Tempo method on pathUSD at $0.035 per request (35,000 base units with 6 decimals). The broader BuiltWith MPP service also offers domain tech-stack lookup, technology lists, domain relationships, company-to-URL resolution, tags, product search, recommendations, keywords, trends, trust signals, and a cheaper free-summary endpoint.

Note: The probe only tested HEAD and GET methods, which returned 404. The OpenAPI spec declares this as a POST endpoint, so the 404s are expected for non-POST methods. The endpoint is likely live when called with the correct POST method and payment headers. No response schema or example responses are documented in the OpenAPI spec, so the exact shape of redirect data returned is unknown.

Capabilities

domain-redirect-historywebsite-profilingredirect-chain-lookupper-call-micropaymenttempo-settlement

Use cases

  • —Auditing redirect chains for SEO analysis
  • —Detecting domain acquisitions or migrations by examining redirect history
  • —Investigating parked domains that redirect to other properties
  • —Competitive intelligence on how competitors restructure their web presence
  • —Verifying that old URLs properly redirect after a site relaunch

Fit

Best for

  • —SEO professionals auditing redirect chains
  • —Domain investors tracking redirect patterns
  • —Competitive intelligence analysts studying domain changes

Not for

  • —Real-time redirect following or HTTP client functionality — this returns historical data, not live redirects
  • —Bulk domain scanning at scale without per-call payment budget

Quick start

curl -X POST https://builtwith.mpp.paywithlocus.com/builtwith/redirects \
  -H "Content-Type: application/json" \
  -H "Authorization: <MPP-payment-token>" \
  -d '{"LOOKUP": "example.com"}'

Example

Request

{
  "LOOKUP": "example.com"
}

Endpoint

URLhttps://builtwith.mpp.paywithlocus.com/builtwith/redirects
Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.45/ 1.00

OpenAPI spec provides clear request schema and pricing, but no response schema or examples are available. The probe only tested HEAD/GET (returning 404), while the endpoint is POST-only per the spec, so liveness via POST is unconfirmed but likely. No crawled documentation yielded useful content.

Warnings

  • —Endpoint was not confirmed live — probe used HEAD/GET but the spec requires POST; likely operational but unverified
  • —No response schema documented; the shape of redirect data returned is unknown
  • —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo method context

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 17:17:57Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/JfTJn2
Look up redirect history for any domain via BuiltWith's web profiling data. — Clawmart · Clawmart