Trust Score v4.1 combines three weighted dimensions with an optional external-assurance bonus and confidence-tier caps. Each response identifies the engine used; some responses fall back to legacy v2. A legacy v2 component breakdown does not explain an overall score produced by v4.1.
Methodology snapshot reviewed 2026-09-13. Check the live endpoint for current weights and engine selection.
Read engines.overall and engines.breakdown before interpreting a score. overall uses 0–1; trust_score_v41 uses 0–100 when available. With engines.mixed=true, the breakdown does not explain overall. insufficient_data is missing usable evidence, not a measured zero; the public route can return a degraded v2 fallback.
v4.1 available · v2 fallback possible · read engines
v4.1 weights depend on confidence and are renormalized over applicable dimensions. External Assurance adds up to 10 points after the base score, subject to its gates and the tier cap; it is not a fourth weighted dimension.
A store's confidence tier is set by its order history, not chosen by the merchant. The tier both caps the maximum score and sets how much each dimension counts.
—insufficient_dataNo applicable components (or a synthetic_blocked signal): the v4.1 engine emits no value. That does NOT mean the response comes without a score: what happens then is the declared fallback to the v2 engine, and the response says so in its `engines` field (`overall: "v2"`). Treat it as a DEGRADED result: v2 applies neither the tier caps nor the agentic-evidence checks of v4.1, so it is not comparable with a v4.1 score.65cold_starthumanOrders < 5 and agentOrders < 5. Weights: merchantReliabilityBase 0 · agenticReadiness 1 · agenticEvidence 0.85human_establishedhumanOrders ≥ 5 and agentOrders < 5. Weights: merchantReliabilityBase 0.7 · agenticReadiness 0.3 · agenticEvidence 0.92agent_verified_thinagentOrders between 5 and 19 (interpolation only within the tier). Weights: merchantReliabilityBase 0.45 · agenticReadiness 0.25 · agenticEvidence 0.3.100agent_verifiedagentOrders ≥ 20 and GMV ≥ 1,000,000 cents (€10k) in 90d and ≥ 20 unique buyers. Without the GMV floor or unique-buyer count → degrades to agent_verified_thin. Weights: merchantReliabilityBase 0.35 · agenticReadiness 0.25 · agenticEvidence 0.4.Every signal behind the score is tagged with one of these six levels, published alongside the number so a reader can tell measured fact from merchant claim.
verifiedmeasuredproxyself_declarednot_applicablesynthetic_blockedThese weights describe v2 only (0–1 scale), including its fallback path. They do not explain an overall score produced by v4.1. The methodology endpoint retains the fields for compatibility and identifies their scope under legacy_v2.
Legacy v2 formula: weighted_sum_clamped_0_1 · scheduled every 6 hours
These are the display-label thresholds published by the trust-score endpoint, not permissions to act — a score label, identity verification level and operational status are different fields. Consult the policy of the specific endpoint.
0.9EXCELLENTDisplay band only; grants or removes no permission — a separate operational_status field (active/deprioritized/hidden/suspended) governs search visibility and auto-suspension on its own threshold ladder.0.8GOODDisplay band only; grants or removes no permission — a separate operational_status field (active/deprioritized/hidden/suspended) governs search visibility and auto-suspension on its own threshold ladder.0.7ACCEPTABLEDisplay band only; grants or removes no permission — a separate operational_status field (active/deprioritized/hidden/suspended) governs search visibility and auto-suspension on its own threshold ladder.0.5CAUTIONDisplay band only; grants or removes no permission — a separate operational_status field (active/deprioritized/hidden/suspended) governs search visibility and auto-suspension on its own threshold ladder.0RESTRICTEDDisplay band only; grants or removes no permission — a separate operational_status field (active/deprioritized/hidden/suspended) governs search visibility and auto-suspension on its own threshold ladder.Merchants can formally appeal a score they believe is wrong.
POST /api/v1/trust/appealv4.1 labels signal quality and redistributes weight when evidence is not applicable. In the legacy v2 table, 10 of 12 components are labelled verified (weight 0.87); policy_coverage and review_sentiment are declared. These v2 labels do not prove that every input was independently verified.
The legacy v2 component job is scheduled every 6 hours. The public v4.1 overlay can be computed on request. Read the engine, calculated_at and freshness fields together; a mixed response can carry v2 timing alongside a v4.1 overall.
Read the signed public response from the merchant’s declared API host: /api/v1/stores/{slug}/trust-score. Check engines, scales and confidence; a signature authenticates the record, not the reliability of every underlying input.
Trust Score v4.1 combines three weighted dimensions with an optional external-assurance bonus and confidence-tier caps. Each response identifies the engine used; some responses fall back to legacy v2. A legacy v2 component breakdown does not explain an overall score produced by v4.1.