Skip to content
Trust Score v4.1 · public surface live

See how ready your store is for AI-assisted purchases.

The Trust Score is an operational reliability indicator. It helps AI assistants understand whether your store has current information, clear policies, and enough controls to serve a purchase.

This page describes how it is calculated. What that number decides — visibility in agent listings and, below a certain cut-off, automatic suspension of the store — is published with its exact thresholds and your GDPR Article 22 rights in Privacy.

It is a prioritisation signal with context: not a seal, not a customer review, not a guarantee of outcome.

Why it exists

In the human channel trust is built with a brand. In the agentic channel, with checkable data.

An agent decides in milliseconds, without seeing your site, reading your reviews or having room to interpret. It needs to know up front which actions it may attempt, which conditions will apply and what proof will remain afterwards. The Trust Score is that upfront reading: the same one for the merchant who publishes it and the agent who queries it.

01

Checking identity is not enough.

An authenticated agent can still act against the merchant's interest. Knowing who it is without checking its track record does not guarantee the operation ends well.

The score measures readiness, not identity.
02

Reviews are not machine readable.

Stars and opinions describe a past human experience, not the technical ability to answer a delegated action today.

A structured, versioned, queryable signal.
03

With no shared reference, both sides carry the risk.

The merchant assumes the agent will behave; the agent assumes the merchant will respond. Both find out in the same transaction.

One reference both read the same way.
How it is measured

Three aspects that help explain how ready your store is.

What could not be observed is not counted: it is marked not applicable and excluded from the calculation. The actual figure and the quality of each pillar travel in the signed response, with their date; that is why this page publishes no number, which would age the moment it is written.

PILLARS IN THE RESPONSE
Merchant reliabilityTrack record, continuity and real operationmerchant_reliability_base
Agentic readinessManifests, authentication, limits and policiesagentic_readiness
Agentic evidenceOnly when there is a real sample of operationsagentic_evidence
PER-SIGNAL QUALITY
measured
observed on the real system
verified
also checked against a third party
not_applicable
no sample: excluded from the calculation

The response is signed: the EdDSA signature and the key id travel in the headers (x-jws-signature, x-jws-kid), alongside the methodology version.

Open the demo store's signed response
METHODOLOGY 4.1.0Trust with context
  • Bayesian shrinkage: a small sample pulls towards the mean, not towards 100
  • Time decay: an old signal weighs less than a recent one
  • Wilson interval: the range is published, not just the point
  • Per-signal quality: measured, verified or not_applicable

The weight of each pillar and the quality of each signal travel inside the response. There is no hidden weighting.

From signal to score

Four steps between what your store exposes and what an agent reads.

01
Collectllms.txt, mcp.json, .well-known, policies and declared surfaces
available
02
CheckEvery signal is verified against the real system, not against the declaration
available
03
ContextualiseSample, age and confidence adjust the result
in pilot
04
Publish signedScore, range, provenance and version in a single response
available
The merchant's view

For a merchant it is not just a grade: it is what lets you judge who you open the channel to.

The score is calculated during the diagnosis and reads backwards: every point you miss names a concrete capability that is not operational yet.

01available
HOW IT IS USED

As a diagnosis before opening the channel.

You learn which control and evidence signals exist in your systems today and which ones you assumed existed. The score does not reward declared intentions.

  • Priority by impact, not a filed report
  • The difference between declared and checked
  • A measurable starting point for the pilot
How Assurance works
02in pilot
WHAT IT GIVES YOU

Visibility in the channel where nobody looks for your brand.

When an agent compares stores that solve the same need, it picks by complete and current signals. Being measured and signed is the condition for entering that comparison.

  • Eligibility and ordering in the agentic channel
  • Fewer agent rejections and retries
  • Fewer integration hours spent on trial and error
Assess my agentic channel
03in pilot
WHAT IT PROTECTS

A defensible position when something is questioned.

The score does not win a dispute, but it records which controls were active and with what provenance at the time of the operation.

  • Control status with date and version
  • Gaps declared as gaps, not hidden
  • Read alongside the receipt for the operation
What a verifiable receipt looks like
The agent's view

For an agent, picking the wrong store means failing the user who delegated the purchase.

Every tool call costs time, tokens and one chance to fail in front of the user. The Trust Score is queried during planning, before the first attempt is spent.

01

You prioritise instead of probing

Among several stores selling the same thing, you start with the one whose signals are most complete and recent, not with the first in the index.

Fewer retries after an unexpected rejection.
02

You know which condition applies

Thresholds, human review and supported surfaces are visible before attempting the action, not after the error.

Planning with the condition known.
03

You can justify the choice

The response arrives signed and versioned, so your agent's decision is explainable to the user who delegated it.

An auditable choice, not an opaque heuristic.
One signal, two readings

A number the merchant reads as a work plan and the agent as an order of priority.

There are not two scores or two methodologies. There is one signed response and two legitimate ways to use it, and that is what makes it a reference.

The merchant reads“These pillars are measured, these do not apply yet. This is the next one worth solving.”
The agent reads“This store has complete, recent signals. I start here and expect this condition at checkout.”
Inspect states and capabilities
Explicit limits

What the Trust Score is not.

It does not certify the merchant, does not guarantee a transaction goes well and does not replace the evidence of a specific operation. It is a prioritisation signal with visible provenance and sample. Presenting it as anything more would make it useless for both sides.

Review limits and evidence
availableGET /trust-score
A signal is always read with its context.
methodology_version
4.1.0
confidence_level
by sample and age
data_quality
one per pillar
in pilot

The pillars that depend on real operations switch on once there is enough sample in your pilot.

Frequently asked

What people ask before trusting a number.

Can I raise my score without changing anything real?

No. Every pillar is checked against the system, not against what a manifest declares. Declaring a capability that does not answer does not move the score; at best it leaves it marked not applicable.

What if my store is new and has no track record?

With a small sample, Bayesian shrinkage pulls the result towards the mean instead of rewarding a few favourable cases. The score rises as real operations accumulate, not all at once.

Does the score guarantee the transaction will go well?

No. It is a prioritisation signal — catalogue, policies, checkout, evidence — not a guarantee of outcome. The proof of a specific operation is its receipt, not the score.

How often is it recalculated?

Signals decay over time, so an old capture weighs less even if nothing changes. Every signed response states its date and methodology version so you can decide whether it still holds.

Can I compare my score with another store's?

Only by reading the quality of each pillar. Two stores with the same figure may have different pillars measured, and that is explicit in the response.

A number you can show

Calculate your store's Trust Score

The assessment is scoped to one operation, some systems and one metric. You leave with a figure, its provenance and the list of what is worth solving first.

Trust Score — the unit of measure between merchant and agent