Check domain trust signals via BuiltWith data, paid per call with pathUSD on Tempo.
What it does
The BuiltWith Trust endpoint (`/builtwith/trust`) returns trust-signal data for a given domain. It is part of a broader BuiltWith suite exposed through the Locus MPP (Micropayment Protocol) gateway, which covers technology profiling across 100M+ websites. This specific endpoint accepts a domain name and returns trust-related information about that site.
The endpoint is a POST request that takes a JSON body with a required `LOOKUP` field (the domain to check). Payment is settled per-call via the Tempo L2 method at 35,000 base units of pathUSD (currency address `0x20c000000000000000000000b9537d11c60e8b50`). Assuming pathUSD uses 6 decimals, this equates to $0.035 per request. The payment intent is "charge", meaning each call is a one-shot micropayment.
Note that the probe only tested HEAD and GET methods, both returning 404. The OpenAPI spec declares this as a POST endpoint, so the 404s on HEAD/GET are expected behavior — the endpoint is likely live when called with POST. No response schema or example responses are documented in the OpenAPI spec, so the exact shape of the trust data returned is unknown. The broader BuiltWith API reference at https://api.builtwith.com and LLM docs at https://beta.paywithlocus.com/mpp/builtwith.md may provide additional detail.
Capabilities
Use cases
- —Assess the trustworthiness of an unfamiliar domain before engaging with it
- —Enrich lead-scoring pipelines with domain trust signals
- —Automate due-diligence checks on vendor or partner websites
- —Feed trust data into fraud-detection or phishing-detection workflows
Fit
Best for
- —Agents that need programmatic domain trust assessment
- —Sales and marketing teams qualifying leads by website credibility
- —Security tools screening URLs for trust indicators
Not for
- —Full technology stack profiling (use the /builtwith/domain endpoint instead)
- —Free or bulk usage without per-call payment capability
- —Use cases requiring detailed response schema guarantees (response shape is undocumented)
Quick start
curl -X POST https://builtwith.mpp.paywithlocus.com/builtwith/trust \
-H "Content-Type: application/json" \
-d '{"LOOKUP": "example.com"}'Example
Request
{
"LOOKUP": "example.com"
}Endpoint
Quality
The OpenAPI spec provides a clear request schema and pricing, but the response schema is entirely absent — no example responses or field definitions. The probe only tested HEAD/GET (both 404), while the endpoint is POST-only, so liveness is plausible but unconfirmed. No crawled documentation was retrievable.
Warnings
- —Response schema is not documented; the shape of trust data returned is unknown.
- —Endpoint liveness not confirmed — probe used HEAD/GET but the endpoint requires POST. The 404s are expected for wrong methods, but a 402 on POST was not captured.
- —pathUSD decimals assumed to be 6 (standard for USD stablecoins); if different, the $0.035 price estimate would be incorrect.
- —No external documentation pages were successfully crawled; all returned 'not found' JSON.
Citations
- —The /builtwith/trust endpoint is a POST that accepts a LOOKUP domain parameter and costs 35,000 base units of pathUSD via Tempo settlement.https://builtwith.mpp.paywithlocus.com
- —BuiltWith covers technology profiling across 100M+ websites.https://builtwith.mpp.paywithlocus.com
- —Additional docs referenced at https://api.builtwith.com and https://beta.paywithlocus.com/mpp/builtwith.mdhttps://builtwith.mpp.paywithlocus.com