---
title: "Trust-relevant facts OpenShopGraph itself measured about one merchant/shop (by id or domain): TLS certificate issuer and grade, hosting ISP and country, domain registration date, registrar, and accepted payment methods. Returns INDIVIDUAL signals, never an aggregate: every entry carries its own value, `source` (where OpenShopGraph observed it) and `checked_at` (when). There is deliberately no score, rating, percentage or star value — not even an internally computed one; you are given the raw evidence and judge for yourself. A field with no source or no check timestamp is omitted entirely rather than shipped with a null placeholder. If nothing was measured, the answer is status \"no_signals_collected\" with an empty list — that means NOTHING IS KNOWN, it is not a score of zero and not a negative verdict. Unknown domains, shops under internal review and measured-but-empty shops are intentionally indistinguishable here. `signal_coverage` describes data completeness, not merchant trustworthiness: `present`/`total` count how many of the (up to 7) signal fields OpenShopGraph was able to deliver for this shop, and `missing` lists the rest, each with a `reason` — `not_collected_yet` (OpenShopGraph has never run that check for this shop) or `pipeline_gap` (the check ran — source and timestamp exist — but produced no usable value, e.g. an IP/ASN lookup that resolves a hosting ISP but not a country). A low `present` count is NOT evidence of a low-quality or risky merchant: it usually just means one of OpenShopGraph's own probes came back empty. Do not treat `signal_coverage` as a rating, and do not rank or filter merchants by it as if it were one. Unlike every other tool on this page, this one requires a valid `x-api-token` header — a call without one fails before reaching this tool (401, no exceptions for anonymous/public callers)."
method: POST
path: "/tool/get_trust"
---

# Trust-relevant facts OpenShopGraph itself measured about one merchant/shop (by id or domain): TLS certificate issuer and grade, hosting ISP and country, domain registration date, registrar, and accepted payment methods. Returns INDIVIDUAL signals, never an aggregate: every entry carries its own value, \`source\` (where OpenShopGraph observed it) and \`checked_at\` (when). There is deliberately no score, rating, percentage or star value — not even an internally computed one; you are given the raw evidence and judge for yourself. A field with no source or no check timestamp is omitted entirely rather than shipped with a null placeholder. If nothing was measured, the answer is status "no_signals_collected" with an empty list — that means NOTHING IS KNOWN, it is not a score of zero and not a negative verdict. Unknown domains, shops under internal review and measured-but-empty shops are intentionally indistinguishable here. \`signal_coverage\` describes data completeness, not merchant trustworthiness: \`present\`/\`total\` count how many of the (up to 7) signal fields OpenShopGraph was able to deliver for this shop, and \`missing\` lists the rest, each with a \`reason\` — \`not_collected_yet\` (OpenShopGraph has never run that check for this shop) or \`pipeline_gap\` (the check ran — source and timestamp exist — but produced no usable value, e.g. an IP/ASN lookup that resolves a hosting ISP but not a country). A low \`present\` count is NOT evidence of a low-quality or risky merchant: it usually just means one of OpenShopGraph's own probes came back empty. Do not treat \`signal_coverage\` as a rating, and do not rank or filter merchants by it as if it were one. Unlike every other tool on this page, this one requires a valid \`x-api-token\` header — a call without one fails before reaching this tool (401, no exceptions for anonymous/public callers).

`POST /tool/get_trust`

## Request

- Base URL: `https://api.openshopgraph.com`
- URL: `https://api.openshopgraph.com/tool/get_trust`
- Auth: API key in header `x-api-token`

## Request body

- object
  - `shop_domain` string, required: Shop domain, e.g. "otto.de". An internal OpenShopGraph shop id is accepted here as well. The older field name `shop_id_or_domain` still works on every tool and means exactly the same thing.

## Response `200`

OK

## Other responses

- `400`: invalid input
- `404`: not found

---

[API](https://skmtc.dev/openshopgraph/apis/openshopgraph-mcp-server.md) · [All operations](https://skmtc.dev/openshopgraph/apis/openshopgraph-mcp-server/llms.txt) · [OpenAPI document](https://skmtc.dev/openshopgraph/apis/openshopgraph-mcp-server/revisions/5a5ef86dcc0a?raw)