Who is acting?
A technical identifier does not always explain who operates the agent or what its purpose is.
Verify the context before exposing a sensitive action.How we evaluate contextDecide what an assistant can do and when it needs approval. Test the rules your platform supports in a guided pilot. Review the available evidence for the operation.
Free analysis: no account needed to start. Pilot: we agree on the scope with your team.
checkoutScope: Trusteed is not a payment processor and not merchant of record: the charge is made on the merchant's own payment account, with their credentials. Nor does it replace your own records or legal obligations. See full limits
An assistant may prepare an order above your limit or repeat a purchase by mistake. Before opening this channel, decide which actions need approval and what information you want to keep.
A technical identifier does not always explain who operates the agent or what its purpose is.
Verify the context before exposing a sensitive action.How we evaluate contextIdentifying the assistant helps you know who is acting. You also need rules to detect repeated orders or amounts above your limit.
Agree on limits and approval points for the pilot actions.See limits and approvalsPrice, stock, seller or terms may no longer match what was approved.
Check price and stock again in the flows that support it.See the scope of checkout controlTo review a purchase, you need to know what was requested, what was decided and which evidence is missing.
When a receipt is issued, consult the record and the missing evidence.See the sample TrustReceiptThe free audit reviews your public pages. To test purchases, Assurance identifies what is ready and what is missing. Control applies the agreed rules and Evidence lets you review the available records.
Before integrating, check which capabilities are available and which need further testing. The diagnosis helps you decide whether to start with Control or Evidence.
Set limits on the assistant's actions. In the pilot, we agree on the rules your platform supports and when a request is allowed, reviewed or blocked.
On supported channels, a signed TrustReceipt lets you verify the record's integrity. Its contents depend on the evidence captured during the operation.
Explore three situations: an everyday purchase, an order above the limit and an unverified agent. This simulation shows fixed decisions. It does not place orders or query your store.
{ "tool": "complete_checkout", "amount": 6400, "agent_status": "verified"}The request can continue after the buyer confirms. This decision does not mean the payment has completed.
Rafi, our AI avatar, explains how the arrival of shopping agents is changing the rules of online commerce, and what it means for your store.
The TrustReceipt signature lets you check who issued the record and whether it has changed. The receipt contains the available evidence for the operation, which may vary by channel and by the data captured.
The signature verifies the record's integrity. On its own, it does not prove a purchase took place or guarantee a successful dispute. The value of the evidence depends on the case and who receives it.
tr_01JY7E4M8X...A92FIndividual receipts are issued in production. Coverage depends on the channel: issuance was enabled and producing at the last check (2026-10-17), and the live counters are published at /api/v1/health. This reading does not show coverage, so do not assume every purchase has a receipt. Full lifecycle tracking remains planned.
Score for merchant: demo-store (demo store, synthetic data)
The Trust Score brings together this merchant's operational reliability signals. The Agent Score from the free audit evaluates public pages. These are different measures and neither guarantees the outcome of a purchase.
There is limited history available. Interpret this score with caution; it does not guarantee future purchases.
The public methodology is 4.1.0: the overall result comes from it, although the per-component breakdown may still come from an earlier engine, and each API response says which. Little history is reported as limited history, not as risk. The technical detail and API fields are on the methodology page.
How the Trust Score is measured ↗You do not need to migrate your store. The pilot integrates with your existing systems and covers the actions your platform supports.
Yes. An identified assistant may repeat an order by mistake or exceed a limit. Identity is checked alongside the rules for the operation.
It reviews your store's public pages and returns an Agent Score with the issues found. You can start without an account. If the full report requires an email address, this is shown alongside the result. The analysis does not activate purchase controls.
No. It lets you verify the signed record's integrity. What it proves depends on the evidence captured, and acceptance depends on the payment provider, the process and the jurisdiction.
Analyse your public pages for free. To test purchases with rules and evidence, request a pilot with your team.
MCP endpoint
POST https://trusteed.xyz/{storeSlug}/mcp/discoveryJSON-RPC 2.0: replace {storeSlug} with the slug published in merchant-index.json. Discovery needs no credential.
Discover the tools
tools/listRead the actual tool set on the selected endpoint; tools depend on each store.
Cart and checkout: /{storeSlug}/mcp/checkout. Real merchants need OAuth; demo-store uses a sandbox key and simulated payments.
If the bucket returns bucket_not_enabled_for_store, use the legacy /{storeSlug}/mcp alias. Check real-payment availability in the registry; a checkout endpoint does not prove settlement.