Support

Last updated ยท September 7, 2026

One address, and it is already the one on our privacy, terms and refund pages: hello@utilityhouse.xyz.

We do not publish a response time, because we have not measured one. Saying “within 24 hours” when nobody has checked is a promise, not a service.

What to include

Almost everything we need is in the result you already have.

Store origin
The public origin you ran the check against, for example https://shop.example.com.
What you ran
The free preflight, the MCP tool name, or the Release Gate.
The result
The whole JSON body if you have it — especially state, unknowns and any reasonCode.
observed_at
The timestamp in the result. It tells us which run you mean.
What you expected
One sentence. This is usually the most useful line in the message.

What never to send

We do not need any of these, and we would rather not receive them:

If a message arrives containing credentials, we will ask you to revoke them and we will not use them.

Common answers, before you write

What you sawWhat it means
state: "BLOCKED" with HTTP 200The check reached your store and could not read it. That is an abstention, not a verdict about your store. unknowns says why.
429 TARGET_RATE_LIMITEDThe daily budget for that store origin (3/day) or your address (10/day) is spent. Try tomorrow.
400 UNKNOWN_PROPERTYThe request body carried a field we do not accept. We reject rather than ignore it, so a typo never looks like an answer.
AUTH_REQUIRED from a Release Gate toolThose three tools need a bearer token and a verified ownership record. The public tools do not.
A price on the Release GateIt is a beta price and not available for purchase. Settlement is disabled.

Reporting a security issue

Use the security page, not this one.

Service state

Live state is at /status. Data handling is on the privacy page; service terms are on the terms page.